Upload
mara-blaker
View
219
Download
1
Tags:
Embed Size (px)
Citation preview
Evolution of the Kuali Rice ProjectCharter, 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• 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?
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
Rice Version 1.0
What is Kuali Rice?
App Dev Tools
Middleware
Evolution of Rice
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– 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• 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• Service Oriented• Open Source• Leveraging existing OS assets (avoid NIH)
Rice Charter – Project Organization
• Partnerships– Investing Partners– Adopters– Interested Parties
• Project Manager• Lead Technical Architect• Contributions from other Kuali Projects
Rice Governance
Kuali Rice Board
Application Roadmap Committee
Kuali Foundation Board
Kuali Financial Reps
Kuali Student Reps
Kuali Coeus Reps
Kuali Rice Reps
Future Project Reps
Technology Roadmap Committee
Kuali Financial Reps
Kuali Student Reps
Kuali Coeus Reps
Kuali Rice Reps
Future Project Reps
Kuali Rice Project Manager
Kuali Application IntegrationWorking Group
Kuali Technology IntegrationWorking Group
Kuali Rice Developers
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
• 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
Technology Roadmap Committee
Rice Governance – TRC
• 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
TRC Research Items on Roadmap
Rice Governance – ARC
• 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
Application Roadmap Committee
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 – 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…
Rice Roadmap – Release Version Scheme
Major Versions: 2-3 yearsMinor Versions: 6-9 monthsPatch Versions: as needed
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…
Rice Roadmap: Release Timeline
Key VersionThemes
ProjectedMilestones
As ofNov 2009
Q4 2009Rice 1.01Release
Q2 2011Rice 1.2Release
Kuali Business Drivers Service Orientation Integration with Kuali ApplicationsKuali Business Drivers Service Orientation Integration with Kuali ApplicationsPervasive Themes
Calendar 2009 2010 2011 2012
Version 1.1
Version Compatibility
Industry Standards
Version 1.2
Ease of Implementation
Project Standardization
Kuali AppSupport
Version 1.0
Initial Launch
v1.0.x Patch Releases
2012Rice 2.0Release
Continued Support forKuali Application Releases
KFS 3.xKS 1.xKC 2.0
KFS 3.0KS 1.0KC 1.x
KFS 4.0KS 1.xKC 2.x
Forward compatibility
Q2 2010Rice 1.02Release
Version 2.0
Modularity
Leverage existing Open Source Solutions
Q4 2010Rice 1.1Release
Degree of Certainty
Key VersionThemes
ProjectedMilestones
As ofNov 2009
Q4 2009Rice 1.01Release
Q2 2011Rice 1.2Release
Kuali Business Drivers Service Orientation Integration with Kuali ApplicationsKuali Business Drivers Service Orientation Integration with Kuali ApplicationsPervasive Themes
Calendar 2009 2010 2011 2012
Version 1.1
Version Compatibility
Industry Standards
Version 1.2
Ease of Implementation
Project Standardization
Kuali AppSupport
Version 1.0
Initial Launch
v1.0.x Patch Releases
2012Rice 2.0Release
Continued Support forKuali Application Releases
KFS 3.xKS 1.xKC 2.0
KFS 3.0KS 1.0KC 1.x
KFS 4.0KS 1.xKC 2.x
Forward compatibility
Q2 2010Rice 1.02Release
Version 2.0
Modularity
Leverage Existing Open Source Solutions
Q4 2010Rice 1.1Release
Degree of Certainty
Rice Roadmap: Release Timeline
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
Desired Features
Please see current
roadmaps and status reports for
updates
Key VersionThemes
ProjectedMilestones
As ofNov 2009
Q4 2009Rice 1.01Release
Q2 2011Rice 1.2Release
Kuali Business Drivers Service Orientation Integration with Kuali ApplicationsKuali Business Drivers Service Orientation Integration with Kuali ApplicationsPervasive Themes
Calendar 2009 2010 2011 2012
Version 1.1
Version Compatibility
Industry Standards
Version 1.2
Ease of Implementation
Project Standardization
Kuali AppSupport
Version 1.0
Initial Launch
v1.0.x Patch Releases
2012Rice 2.0Release
Continued Support forKuali Application Releases
KFS 3.xKS 1.xKC 2.0
KFS 3.0KS 1.0KC 1.x
KFS 4.0KS 1.xKC 2.x
Forward compatibility
Q2 2010Rice 1.02Release
Version 2.0
Modularity
Leverage Existing Open Source Solutions
Q4 2010Rice 1.1Release
Degree of Certainty
Rice Roadmap: Release Timeline
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
Desired Features
Please see current
roadmaps and status reports for
updates
Getting 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
There are a number of ways to get involved…
Getting 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
There are a number of ways to get involved…
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