1. Evolution of the Kuali Rice Project Charter, Governance and Roadmap

2. What is Kuali Rice? Kuali: a humble kitchen wok (Malaysian origins) Rice: a food staple – Sits on the bottom of a dish – Not a very tasty meal by itself – Better with some cuisine on top KFS (Kuali Financial System) - Beef KC (Kuali Coeus, Research Administration) - Chicken KS (Kuali Student) - Seafood Rice is the foundation to hearty meals (aka enterprise administrative software products for education)

3. What is Kuali Rice? KNSKuali Nervous System KENKuali Enterprise Notification KSBKuali Service Bus KEWKuali Enterprise Workflow KIM Kuali Identity Management Rice Version 1.0 Components

4. What is Kuali Rice? App Dev Tools Middleware

5. Evolution of Rice

6. Rice Charter – Project Vision Support the needs of the Kuali Application Projects – Foundational middleware components and services – Enhanced software development framework Leverage the middleware and development frameworks for building custom applications Achieve sustainability through community source development and adoption Iterate Rice towards an increasingly Service Oriented Architecture

7. Rice Charter – Project Objectives To create standard APIs to Rice components To design components which are modular To provide a reference implementation based on industry standards To ensure intellectual property and open source license compliance is maintained To promote adoption by a wide variety of institutions, primarily in higher education To build a large community of interest with strong sustainability

8. Rice Charter – Key Principles Plug and Play Reusability Interoperability Standards Based Service Oriented Open Source Leveraging existing OS assets (avoid NIH)

9. Rice Charter – Project Organization Partnerships – Investing Partners – Adopters – Interested Parties Project Manager Lead Technical Architect Contributions from other Kuali Projects

10. Rice Governance

11. Rice Governance – Rice Board 7 Investing Partners Bi-weekly meetings Strategic directions Strategic relationships Inter board communications

12. Rice Governance – TRC Chartered to – Provide cross project communications, resolve conflicts, build community – Encourage convergence of technologies and methods – Evaluate, recommend and endorse development tools and technologies – Conduct architectural reviews and feasibility research studies Active Work Teams and Projects – Kuali Technical Integration (KTI) Steering Group – Version compatibility – OJB replacement with JPA – Rice KNS improvement strategies – Java 5 to 6 Transition Plan – Browser Compatibiity Technology Roadmap Committee

13. Rice Governance – TRC KSB replacement with another open source ESB BPEL / BPM support Common supported platforms (oper systems, databases, etc.) RESTful service oriented architecture support Component / package modularity architectures (e.g. OSGI) Rich UI Framework support Accessibility and Internationalization support Service Contract Change Management Application Connectors to other ERP systems Common Data Warehouses and Data Marts TRC Research Items on Roadmap

14. Rice Governance – ARC Chartered to – Set goals and prioritize the Rice roadmap – Provide a leadership forum for cross project initiatives Active Projects – Roadmap Working Group – Kuali Application Integration (KAI) Kuali Application Integration group provides tactical support and issue resolution for how Kuali applications integrate and leverage Rice. Application Roadmap Committee

15. Rice Roadmap Purpose: Provide the Kuali ecosystem with visibility into the future of the Rice software, and a means to effect that future. The roadmap covers: – Background and Vision – Themes – Release Plans – The Roadmap Process – Release Cycle Strategies

16. Rice Roadmap - Process

17. Rice Roadmap – Release Cycles Release Versioning Schemes (major, minor, patch, version lifespan) Release Lifespan strategies Expectations on synchronizing Rice Releases to other Kuali Project releases End-of-Life for major versions strategy Pre-release version strategies (Dev builds, milestones, release candidates) Roadmap Committees Defined…

18. Rice Roadmap – Release Version Scheme Major Versions: 2-3 years Minor Versions: 6-9 months Patch Versions: as needed

19. Rice Roadmap – Enhancement Themes Development Ease of Use Ease of Implementation Kuali Project Business Drivers Modularity Industry Standards Project Standardization Version Compatibility Service Orientation Etc. Roadmap Committees defined themes to classify enhancement requests…

20. Rice Roadmap – Release Timeline

21. Rice Roadmap – Release 1.1 Details Version Compatibility (backward compatibility, framework compatibility) API service interface improvements Spring 2.5 Framework Upgrade Expanded support for XML import and export Replace OJB with Java Persistence API (JPA) Improve support for FERPA and FIPPA compliance Adopt PDF Adobe Acrobat Plug In developed by Cornell Research KIM modularization options Planned Enhancements Include…

22. Getting Involved Download the software and adopt it Contribute back useful add-ons, plug ins, sample applications Share experiences and support via email lists Contact a Rice Board member to discuss strategic relationships Enlist the help of Kuali Commercial Affiliates for training and support Become an Investing Partner and help shape the future direction There are a number of ways to get involved…

23. Why Rice? Software for education, but applicable for others Shared resources spread the cost of development Open code results in better community support and lower costs Community development approach ensures better overall software Application development and middleware solutions that increase productivity In summary, the benefits of Rice are…