View Presentation

393 views

Published on

  • Be the first to comment

  • Be the first to like this

View Presentation

  1. 1. Kuali Project Architecture JA-SIG December 7, 2004 James Thomas Manager, Systems Integration Indiana University
  2. 2. Session Agenda <ul><li>Kuali Project Overview (brief) </li></ul><ul><li>Service Oriented Architecture </li></ul><ul><li>Kuali Development Methodology </li></ul><ul><li>Standard Tools and Frameworks </li></ul><ul><li>Key Infrastructure: Portal & Workflow </li></ul>
  3. 3. Kuali Project Overview
  4. 4. Overview <ul><li>Kuali – kitchen wok; humble utensil </li></ul><ul><li>Community Source Project </li></ul>See www.kualiproject.org for details
  5. 5. Overview <ul><li>Develop a comprehensive suite of financial software to serve the needs of higher education . Modules include: </li></ul><ul><li>Chart of Accounts Purchasing </li></ul><ul><li>General Ledger Accounts Payable </li></ul><ul><li>General Accounting Cash Receipting/Disbursement </li></ul><ul><li>Accounts Receivable Travel Req/Reimbursement </li></ul><ul><li>Capital Asset Mgmnt E-Commerce </li></ul><ul><li>Pre/Post-Award Admin Budget Construction </li></ul><ul><li>Auxiliary Accounting Workflow (infrastructure) </li></ul>
  6. 6. Overview <ul><li>Project Status </li></ul><ul><li>Work has already begun </li></ul><ul><li>“Official” kickoff in January 2005 </li></ul><ul><li>Two-year development plan </li></ul>
  7. 7. Kuali Project Architecture
  8. 8. Architecture <ul><li>Key Objectives </li></ul><ul><li>Design highly functional and flexible software </li></ul><ul><li>Technology choices based on industry standard, open source, and “proven” solutions </li></ul><ul><li>Deliver applications via loosely-coupled components and services with clearly defined APIs </li></ul><ul><li>Leverage core “IT assets” </li></ul><ul><li>Emphasize code re-use/reduce redundancy </li></ul>
  9. 9. Architecture <ul><li>Service Oriented Architecture (SOA) </li></ul><ul><li>Services are loosely coupled . </li></ul><ul><li>Services have well-defined interfaces and are reusable . </li></ul><ul><li>Focus on business processes </li></ul>
  10. 11. Architecture <ul><li>Benefits of SOA </li></ul><ul><li>Improved ROI – some reusable components will outlive applications </li></ul><ul><li>Easier to maintain code base </li></ul><ul><li>Code Mobility </li></ul>
  11. 12. Architecture <ul><li>Benefits of SOA (continued) </li></ul><ul><li>Can support multiple clients - browser or </li></ul><ul><li> “ rich client” </li></ul><ul><li>Services can be assembled to build new applications faster </li></ul><ul><li>Independent layers make development by different groups easier using standard APIs </li></ul>
  12. 13. Kuali Development Methodology
  13. 14. Methodology <ul><li>Problems with previous methodologies </li></ul><ul><li>Process driven </li></ul><ul><li>Difficult to keep up with changes </li></ul><ul><li>Time consuming </li></ul><ul><li>Inefficient </li></ul><ul><li>Sometimes less than satisfactory results </li></ul><ul><li>Inflexible – requirements do change </li></ul>
  14. 15. Methodology <ul><li>What’s wrong with this picture? </li></ul><ul><li>Where is our focus? </li></ul><ul><li>Our goal is to develop software that works for our customers </li></ul>
  15. 16. Methodology <ul><li>Development Methodology for delivering working software </li></ul><ul><li>Flexible (b/c the only certainty is change ) </li></ul><ul><li>Efficient </li></ul><ul><li>Results-Oriented </li></ul><ul><li>People-Centered </li></ul><ul><li>Feedback Driven </li></ul><ul><li>Sustainable </li></ul>
  16. 17. Methodology <ul><li>Strategy </li></ul><ul><li>Plan for shorter development cycles </li></ul><ul><li>Embrace change </li></ul><ul><li>Developers and functional experts should work together continuously </li></ul><ul><li>Open communication </li></ul><ul><li>Quality software builds trust and faith </li></ul><ul><li>Keep it simple/avoid over-engineering </li></ul>
  17. 18. Methodology <ul><li>One Possibility: Test-Driven Development (TDD) </li></ul><ul><li>TDD is a lightweight methodology emphasizing fast, incremental development and writing tests before writing code </li></ul><ul><li>Start with small pieces of functionality and then build the app little-by-little (red/green/refactor) </li></ul>
  18. 19. Methodology <ul><li>Benefits of TDD </li></ul><ul><li>Code that works! </li></ul><ul><li>Immediate feedback on design decisions </li></ul><ul><li>Flexibility </li></ul><ul><li>Users provide input “as you go” </li></ul><ul><li>Confident programmers </li></ul><ul><li>Fully testable code base </li></ul><ul><li>Clean and maintainable code </li></ul>
  19. 20. Methodology <ul><li>Exploring other concepts from </li></ul><ul><li>Agile Processes </li></ul><ul><li>Extreme Programming (XP) </li></ul><ul><li>Learning and adapting as we go </li></ul><ul><li>Like the results thus far </li></ul>
  20. 21. Kuali Standard Tools and Frameworks
  21. 22. Tools/Frameworks <ul><li>Standards </li></ul><ul><li>Java 2 Enterprise Edition (J2EE) </li></ul><ul><li>XML/XSLT </li></ul><ul><li>Tools/Frameworks </li></ul><ul><li>Struts/JSTL </li></ul><ul><li>Spring </li></ul><ul><li>Object Relational Bridge (OJB) </li></ul><ul><li>jUnit and jMeter </li></ul><ul><li>Log4J </li></ul>
  22. 23. Platforms <ul><li>Web Server: Linux, Apache </li></ul><ul><li>Application Server: Linux, Tomcat 5 </li></ul><ul><li>DBMS: Oracle </li></ul>* *avoiding triggers, stored procedures, proprietary data types, etc. in order to achieve database independence
  23. 24. Key Kuali Infrastructure Portal & Workflow
  24. 25. Enterprise Portal <ul><li>Kuali services will be designed to be delivered via a standard enterprise portal framework </li></ul><ul><li>Access to “Action List” service for managing electronic transactions (eDocs) via enterprise workflow </li></ul>
  25. 26. Power of Workflow <ul><li>A general-purpose infrastructure for conducting mediated transactions with electronic documents (eDocs) </li></ul><ul><li>Quick, easy, and accurate routing </li></ul><ul><li>Automate University business rules </li></ul><ul><li>Complete Audit Trail </li></ul>
  26. 27. OneStart Workflow <ul><li>EXAMPLE: </li></ul><ul><li>OneStart Workflow is currently routing over 1,800 eDocs/day and 55,000/mo </li></ul><ul><li>Human Resources eDocs previously requiring 1 to 2 weeks to process have been approved in < 1 hour </li></ul><ul><li>38 different types of eDocs from 3 diff apps </li></ul>
  27. 28. Workflow Lessons <ul><li>Causes re-evaluation of current business processes. Are they efficient? </li></ul><ul><li>No more “Bottleneck Bills”.  </li></ul><ul><li>We see Workflow… </li></ul><ul><li>… everywhere! </li></ul>
  28. 29. Conclusions
  29. 30. Conclusions <ul><li>Kuali Partners are committed to: </li></ul><ul><li>Community Source Software </li></ul><ul><li>Service Oriented Architecture </li></ul><ul><li>Iterative and Flexible Methodology </li></ul><ul><li>Open Standards </li></ul><ul><li>Enterprise Application Integration </li></ul>
  30. 31. Conclusion <ul><li>We are genuinely excited about the challenges and the possibilities!!! </li></ul>
  31. 32. Want technical details? <ul><li>Attend this session TODAY (12/7/04): </li></ul><ul><li>“ Pragmatic Application Building: Step-By-Step” </li></ul><ul><li>Build IT Track </li></ul><ul><li>2:00 to 3:00PM </li></ul><ul><li>Presenter: Jay Sissom </li></ul><ul><li>Indiana University </li></ul>
  32. 33. Questions? <ul><li>James Thomas </li></ul><ul><li>Manager, Systems Integration </li></ul><ul><li>University Information Systems </li></ul><ul><li>Indiana University </li></ul><ul><li>[email_address] </li></ul>

×