ARC and TRC Update to All Boards

Evolution of Rice

Successes this year

• Rice Investors & Charter• Grew the rice team from the ground up• ARC/TRC• Rice 1.0• KS released with KIM, ??, ??• Roadmap process & first roadmap

What is Kuali Rice?

App Dev Tools

Middleware

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 • Bi-weekly meetings• Strategic directions• Strategic relationships• Inter board communications• New funding model for sustaining project

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 and support

Technology Roadmap Committee

Rice Governance – TRC

• KSB replacement with another open source ESB• BPEL / BPM support • Common supported platforms (op 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 currently on roadmap

Rice Governance – TRC

• Member contributed participation time is limited– Hiring a Lead Technical Architect will help

• Time pressures of projects to make architectural decisions – Doing TRC reviews early in project development process will help

• Confusion over decision making processes– Having a roadmap process will now make change request processing better

• Level of automatic decision making by KAI and KTI groups– Need more time and experience to empower these steering groups to

make appropriate decisions without escalating to ARC / TRC• Prioritizing large scope of work

– May need to refine method of prioritizing to balance immediate and strategic needs

TRC challenges moving forward

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)

The Roadmap Committees have 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

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…

In summary…

• Rice is evolving to provide enhanced value to the projects

• Cross project communications is essential• Lead Technical Architect is a critical resource to help

drive the evolution of Rice• ARC / TRC starting to work but fine tuning membership

and decision making processes is necessary

Key challenges

• Sustainability– Insufficient resources: look at roadmap– Difficulty living up to the principles in our roadmap

(due to resources… ex. KSB)

• Complexity– Organizational (ARC/TRC/Board/Kuali Rice Counsel

(KRC)/subcommittees/etc.)

– Project demands (alignment of roadmaps, business needs, etc.)

• Level of project engagementEveryone 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 processCall this v0.5 beta

Questions?