© 2004, The Trustees of Indiana University Kuali Project Architecture JA-SIG December 7, 2004 James Thomas Manager, Systems Integration Indiana University

© 2004, The Trustees of Indiana University Session Agenda Kuali Project Overview (brief) Service Oriented Architecture Kuali Development Methodology Standard Tools and Frameworks Key Infrastructure: Portal & Workflow

© 2004, The Trustees of Indiana University Kuali Project Overview

© 2004, The Trustees of Indiana University Overview Kuali – kitchen wok; humble utensil Community Source Project See for detailswww.kualiproject.org

© 2004, The Trustees of Indiana University Overview Develop a comprehensive suite of financial software to serve the needs of higher education. Modules include: Chart of AccountsPurchasing General LedgerAccounts Payable General AccountingCash Receipting/Disbursement Accounts ReceivableTravel Req/Reimbursement Capital Asset MgmntE-Commerce Pre/Post-Award AdminBudget Construction Auxiliary AccountingWorkflow (infrastructure)

© 2004, The Trustees of Indiana University Overview Project Status Work has already begun “Official” kickoff in January 2005 Two-year development plan

© 2004, The Trustees of Indiana University Kuali Project Architecture

© 2004, The Trustees of Indiana University Architecture Key Objectives Design highly functional and flexible software Technology choices based on industry standard, open source, and “proven” solutions Deliver applications via loosely-coupled components and services with clearly defined APIs Leverage core “IT assets” Emphasize code re-use/reduce redundancy

© 2004, The Trustees of Indiana University Architecture Service Oriented Architecture (SOA) Services are loosely coupled. Services have well-defined interfaces and are reusable. Focus on business processes

© 2004, The Trustees of Indiana University

Architecture Benefits of SOA Improved ROI – some reusable components will outlive applications Easier to maintain code base Code Mobility

© 2004, The Trustees of Indiana University Architecture Benefits of SOA (continued) Can support multiple clients - browser or “rich client” Services can be assembled to build new applications faster Independent layers make development by different groups easier using standard APIs

© 2004, The Trustees of Indiana University Kuali Development Methodology

© 2004, The Trustees of Indiana University Methodology Problems with previous methodologies Process driven Difficult to keep up with changes Time consuming Inefficient Sometimes less than satisfactory results Inflexible – requirements do change

© 2004, The Trustees of Indiana University Methodology What’s wrong with this picture? Where is our focus? Our goal is to develop software that works for our customers

© 2004, The Trustees of Indiana University Methodology Development Methodology for delivering working software Flexible (b/c the only certainty is change) Efficient Results-Oriented People-Centered Feedback Driven Sustainable

© 2004, The Trustees of Indiana University Methodology Strategy Plan for shorter development cycles Embrace change Developers and functional experts should work together continuously Open communication Quality software builds trust and faith Keep it simple/avoid over-engineering

© 2004, The Trustees of Indiana University Methodology One Possibility: Test-Driven Development (TDD) TDD is a lightweight methodology emphasizing fast, incremental development and writing tests before writing code Start with small pieces of functionality and then build the app little-by-little (red/green/refactor)

© 2004, The Trustees of Indiana University Methodology Benefits of TDD Code that works! Immediate feedback on design decisions Flexibility Users provide input “as you go” Confident programmers Fully testable code base Clean and maintainable code

© 2004, The Trustees of Indiana University Methodology Exploring other concepts from Agile Processes Extreme Programming (XP) Learning and adapting as we go Like the results thus far

© 2004, The Trustees of Indiana University Kuali Standard Tools and Frameworks

© 2004, The Trustees of Indiana University Tools/Frameworks Standards Java 2 Enterprise Edition (J2EE) XML/XSLT Tools/Frameworks Struts/JSTL Spring Object Relational Bridge (OJB) jUnit and jMeter Log4J

© 2004, The Trustees of Indiana University Platforms Web Server: Linux, Apache Application Server: Linux, Tomcat 5 DBMS: Oracle * *avoiding triggers, stored procedures, proprietary data types, etc. in order to achieve database independence

© 2004, The Trustees of Indiana University Key Kuali Infrastructure Portal & Workflow

© 2004, The Trustees of Indiana University Enterprise Portal Kuali services will be designed to be delivered via a standard enterprise portal framework Access to “Action List” service for managing electronic transactions (eDocs) via enterprise workflow

© 2004, The Trustees of Indiana University Power of Workflow A general-purpose infrastructure for conducting mediated transactions with electronic documents (eDocs) Quick, easy, and accurate routing Automate University business rules Complete Audit Trail

© 2004, The Trustees of Indiana University OneStart Workflow EXAMPLE: OneStart Workflow is currently routing over 1,800 eDocs/day and 55,000/mo Human Resources eDocs previously requiring 1 to 2 weeks to process have been approved in < 1 hour 38 different types of eDocs from 3 diff apps

© 2004, The Trustees of Indiana University Workflow Lessons Causes re-evaluation of current business processes. Are they efficient? No more “Bottleneck Bills”. We see Workflow… …everywhere!

© 2004, The Trustees of Indiana University Conclusions

© 2004, The Trustees of Indiana University Conclusions Kuali Partners are committed to: Community Source Software Service Oriented Architecture Iterative and Flexible Methodology Open Standards Enterprise Application Integration

© 2004, The Trustees of Indiana University Conclusion We are genuinely excited about the challenges and the possibilities!!!

© 2004, The Trustees of Indiana University Want technical details? Attend this session TODAY (12/7/04): “Pragmatic Application Building: Step-By- Step” Build IT Track 2:00 to 3:00PM Presenter:Jay Sissom Indiana University

© 2004, The Trustees of Indiana University Questions? James Thomas Manager, Systems Integration University Information Systems Indiana University