Evolution of the Kuali Rice Project Charter Governance

  • Slides: 26
Download presentation
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:

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)

What is Kuali Rice? Rice Version 1. 0 Core middleware components: • KEN Kuali

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

What is Kuali Rice? Middleware App Dev Tools

What is Kuali Rice? Middleware App Dev Tools

Evolution of Rice

Evolution of Rice

Progress in last year! • • • Project Board established Rice PM hired and

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

Rice Charter – Project Vision • Support the needs of the Kuali Application Projects

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

Rice Charter – Project Objectives • To create standard APIs to Rice components •

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

Rice Charter – Key Principles • • Plug and Play Reusability Interoperability Standards Based

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

Rice Charter – Project Organization • Partnerships – Investing Partners – Adopters – Interested

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

Rice Governance

Rice Governance

Rice Governance – Rice Board • • • 7 Investing Partners Representation by each

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

Rice Governance – TRC Technology Roadmap Committee • Chartered to – – Provide cross

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

Rice Governance – TRC Research Items on Roadmap • • • KSB replacement with

Rice Governance – 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

Rice Governance – ARC Application Roadmap Committee • Chartered to – Set goals and

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

Rice Roadmap Purpose: Provide the Kuali ecosystem with visibility into the future of the

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

Rice Roadmap - Process

Rice Roadmap - Process

Rice Roadmap – Release Cycles Roadmap Committees Defined… • Release Versioning Schemes (major, minor,

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)

Rice Roadmap – Release Version Scheme Major Versions: 2 -3 years Minor Versions: 6

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

Rice Roadmap – Enhancement Themes Roadmap Committees defined themes to classify enhancement requests… •

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.

Rice Roadmap: Release Timeline Pervasive Themes Key Version Themes Calendar Degree of Certainty Projected

Rice Roadmap: Release Timeline Pervasive Themes Key Version Themes Calendar Degree of Certainty Projected Milestones As of Nov 2009 Kuali Business Drivers Service Orientation Version 1. 0 Version 1. 1 Version 1. 2 Version 2. 0 Initial Launch Version Compatibility Ease of Implementation Modularity v 1. 0. x Patch Releases Industry Standards Project Standardization Leverage existing Open Source Solutions 2009 Q 4 2009 Rice 1. 01 Release 2010 Q 2 2010 Rice 1. 02 Release 2011 Q 4 2010 Rice 1. 1 Release Forward compatibility Kuali App Support Integration with Kuali Applications 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 Q 2 2011 Rice 1. 2 Release 2012 Rice 2. 0 Release Continued Support for Kuali Application Releases

Rice Roadmap: Release Timeline Pervasive Themes Key Version Themes Calendar Degree of Certainty Kuali

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

Rice Roadmap: Release Timeline Pervasive Themes Key Version Themes Calendar Degree of Certainty Kuali

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

Getting Involved There a number of ways to get involved… • Download the software

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

Getting Involved There a number of ways to get involved… • Contact a Rice

Getting Involved There 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

In Summary - The Benefits of Rice • Benefit from the collective knowledge base

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 campus faster • Optimize business processes with enterprise workflow • Open software by education, for education