1 / 26

Evolution of the Kuali Rice Project Charter, Governance and Roadmap

Evolution of the Kuali Rice Project Charter, Governance and Roadmap. 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

Download Presentation

Evolution of the Kuali Rice Project Charter, Governance and Roadmap

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Evolution of the Kuali Rice ProjectCharter, 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? Rice Version 1.0 Core middleware components: • KEN Kuali Enterprise Notification • KSB Kuali Service Bus • KEW Kuali Enterprise Workflow • KIM Kuali Identity Management Rapid Application Development Framework: • KNS Kuali Nervous System

  4. What is Kuali Rice? Middleware App Dev Tools

  5. Evolution of Rice

  6. Progress in last year! • Project Board established • Rice PM hired and development team established • Charter developed and adopted • ARC and TRC established • Rice version 1.0 released • Improved documentation • KIM Improvements • Initial roadmap established • Rice version 1.0.1 released • Supports KFS 3.0

  7. 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

  8. 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

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

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

  11. Rice Governance

  12. Rice Governance – Rice Board • 7 Investing Partners • Representation by each Application project • Bi-weekly meetings • Strategic directions • Strategic relationships • Inter board communications

  13. Rice Governance – TRC Technology Roadmap Committee • 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 Compatibility

  14. Rice Governance – TRC TRC Research Items on Roadmap • KSB replacement with another open source ESB • BPEL / BPM support • Common supported platforms (OS, 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

  15. Rice Governance – ARC Application Roadmap Committee • Chartered to • Set goals and prioritize the Rice roadmap • Provide a leadership forum for cross project initiatives • Membership representative of all Application projects, and Rice investors • Active Projects • Roadmap Working Group • Developing the initial public Rice roadmap and process • Kuali Application Integration (KAI) • Tactical support and issue resolution for how Kuali Applications integrate with and leverage Rice • Prioritizes and decides on functional issues that impact users

  16. 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

  17. Rice Roadmap - Process

  18. Rice Roadmap – Release Cycles Roadmap Committees Defined… • 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)

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

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

  21. Pervasive Themes Kuali Business Drivers Service Orientation Integration with Kuali Applications Version 1.1 Version Compatibility Industry Standards Version 1.2 Ease of Implementation Project Standardization Version 1.0 Initial Launch v1.0.x Patch Releases Version 2.0 Modularity Leverage existing Open Source Solutions Key Version Themes Calendar 2009 2010 2011 2012 Degree of Certainty Projected Milestones As of Nov 2009 Q4 2009 Rice 1.01 Release Q2 2010 Rice 1.02 Release Q4 2010 Rice 1.1 Release Q2 2011 Rice 1.2 Release 2012 Rice 2.0 Release Forward compatibility KFS 3.0 KS 1.0 KC 1.x KFS 3.x KS 1.x KC 2.0 KFS 4.0 KS 1.x KC 2.x Continued Support for Kuali Application Releases Kuali App Support Rice Roadmap: Release Timeline

  22. Pervasive Themes Kuali Business Drivers Service Orientation Integration with Kuali Applications Version 1.1 Version Compatibility Industry Standards Version 1.2 Ease of Implementation Project Standardization Version 1.0 Initial Launch v1.0.x Patch Releases Version 2.0 Modularity Leverage Existing Open Source Solutions Key Version Themes Calendar 2009 2010 2011 2012 Degree of Certainty Projected Milestones As of Nov 2009 Q4 2009 Rice 1.01 Release Q2 2010 Rice 1.02 Release Q4 2010 Rice 1.1 Release Q2 2011 Rice 1.2 Release 2012 Rice 2.0 Release Forward compatibility KFS 3.0 KS 1.0 KC 1.x KFS 3.x KS 1.x KC 2.0 KFS 4.0 KS 1.x KC 2.x Continued Support for Kuali Application Releases Kuali App Support Rice Roadmap: Release Timeline Desired Features Please see current roadmaps and status reports for updates Version 1.0 .x • Kuali Identity Management • Convert KEW screens to use KNS • Reduce Code Duplication • Project Structure Improvements • Database Object Name Standardization • Improved Documentation • Context Sensitive Help • Doc Search Enhancements • Rice Portal Version 1.1 • Complete API Module • Framework Compatibility • Spring 2.5 Framework • Java Persistence API - Replace OJB with JPA • PDF Plug In • FERPA, FIPPA Compliance Upgrades • XML Import/Export Expanded functionality • KIM Management screens • Research KIM Modularity Version 1.2 • Modularize the Kuali Nervous System (KNS) • WYSIWIG Workflow Editor • Workflow Escalation • Action List Improvements • Document Search Improvements • Standardize Configuration Parameter Names • Standardize Service Names • Document Type Delegation Features Version 2.0 • Automated Database Generation • Modularity (SOA, OSGI, ProjectBuild) • Update Operations for KIM • Localization Features • DROOLS Business Rules • Kuali Entity Management • Kuali Organization Management • Formal Published Service Contracts • Administrative Tools

  23. Pervasive Themes Kuali Business Drivers Service Orientation Integration with Kuali Applications Version 1.1 Version Compatibility Industry Standards Version 1.2 Ease of Implementation Project Standardization Version 1.0 Initial Launch v1.0.x Patch Releases Version 2.0 Modularity Leverage Existing Open Source Solutions Key Version Themes Calendar 2009 2010 2011 2012 Degree of Certainty Projected Milestones As of Nov 2009 Q4 2009 Rice 1.01 Release Q2 2010 Rice 1.02 Release Q4 2010 Rice 1.1 Release Q2 2011 Rice 1.2 Release 2012 Rice 2.0 Release Forward compatibility KFS 3.0 KS 1.0 KC 1.x KFS 3.x KS 1.x KC 2.0 KFS 4.0 KS 1.x KC 2.x Continued Support for Kuali Application Releases Kuali App Support Rice Roadmap: Release Timeline Desired Features Please see current roadmaps and status reports for updates Version 1.0 .x • Kuali Identity Management • Convert KEW screens to use KNS • Reduce Code Duplication • Project Structure Improvements • Database Object Name Standardization • Improved Documentation • Context Sensitive Help • Doc Search Enhancements • Rice Portal Version 1.1 • Complete API Module • Framework Compatibility • Spring 2.5 Framework • Java Persistence API - Replace OJB with JPA • PDF Plug In • FERPA, FIPPA Compliance Upgrades • XML Import/Export Expanded functionality • KIM Management screens • Research KIM Modularity Version 1.2 • Modularize the Kuali Nervous System (KNS) • WYSIWIG Workflow Editor • Workflow Escalation • Action List Improvements • Document Search Improvements • Standardize Configuration Parameter Names • Standardize Service Names • Document Type Delegation Features Version 2.0 • Automated Database Generation • Modularity (SOA, OSGI, ProjectBuild) • Update Operations for KIM • Localization Features • DROOLS Business Rules • Kuali Entity Management • Kuali Organization Management • Formal Published Service Contracts • Administrative Tools

  24. Getting Involved There are a number of ways to get involved… • Download the software and adopt it • Contribute back useful add-ons, plug ins, sample applications • Get started with Kuali Enterprise Workflow • Share experiences and support via email lists

  25. Getting Involved There are a number of ways to get involved… • 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

  26. In Summary - The Benefits of Rice • Benefit from the collective knowledge base to develop key-enterprise architecture • Standardize enterprise applications and promote re-use • Deliver enterprise software development on campusfaster • Optimize business processes with enterprise workflow • Open software by education, for education

More Related