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

2. Evolution of Rice

3. 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 released
Supports KFS 3.0

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

5. What is Kuali Rice?
Middleware
App Dev Tools

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 – Key Principles
Plug and Play
Reusability
Interoperability
Standards Based
Service Oriented
Open Source
Leveraging existing OS assets (avoid NIH)

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 – 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
Representation by each Application project
Bi-weekly meetings
Strategic directions
Strategic relationships
Inter board communications

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

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

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

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 Version Scheme
Major Versions: 2-3 years
Minor Versions: 6-9 months
Patch Versions: as needed

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

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

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

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

22. Key challenges Sustainability Complexity
Insufficient resources: look at roadmap
Difficulty living up to the principles in our roadmap (due to resources… ex. KSB)
Complexity
Organizational (Kuali Rice Board, ARC / TRC, subcommittees, etc.)
Project demands (alignment of roadmaps, business needs, etc.)
Level of project engagement Everyone is really busy and engagement in ARC/TRC is a valiant volunteer effort, but it’s challenging and probably not sustainable
Maturity of the roadmap process Good first start, but call this v0.5 beta

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