1. Kuali Student R2Update :: 2/28/11
UC Berkeley KS Community Council
Kuali Student R2Update :: 2/28/11

2. Topics to Cover Core Slice Deliverables R2 Tech Workshop Highlights
R2 Roadmap

3. R2 Tech Workshop Highlights
Provided level setting across all of the developers that will work on Core Slice
Defined critical POC and development work prior to Iteration 0
KRAD
Rules
Services and Application Layers
Defined Iterations 0 – 4
General functions
Dependencies
Timeline

4. R2 Core Slice Deliverables :: Development
Provide an early demonstration of working code that crosses all major aspects of enrollment
Prove the conceptual design vis-à-vis the skeleton for Enrollment
Provide solid basis for development
UIF (KRAD)
Rules (KRMS)
Identity, authorization, person (KIM)
New search (KNS)
New application layering
Context
Authorization
Calculation/validation
Assembly (Class II)
Persistence

5. R2 Core Slice Deliverables :: Design
Provide a comprehensive definition of Enrollment based on institutional work developed over the past 18 months
Develop Analysis artifacts
Representative User Stories
Synthesized Business Requirements
Synthesized Data Requirements
Develop Class I and Class II Services
Contracts
Technical artifacts (as described in Service POC below)
Develop UIM including
Interaction patterns & widgets, including mobile devices
Deep dive (wireframes) for Learning Plan and Schedule Builder
For each of the above, define and publish the strategy for governance as parallel development begins

6. Iteration 0 - 4

7. March Focus: Development
Services POC (aka Application Layering) is designed to prove the following improvements in service design and implementation
API first design
SVN restructuring
Passing of context in service
Perform authorization in service implementation
Perform custom authentication
Validate/CRUD data in multiple languages
Improve entities to/from DTOs translations

8. March Focus: Development (cont.)
Rules POC will be the first demonstration of execution of KS statements
Rules POC Roles and Responsibilities While there is still some uncertainty around who will be doing the implementation (Rice or KS or both), the design work will be coordinated
Execution Structure There are 2 possibilities and they depend heavily on how we design the KRMS repository to execution system ::
Translate Statements to KRMS rule structure This will either be done at runtime or at create/modify of statements
Translate Statements to Execution structure The KRMS team is considering a rule execution language or execution object structure for executing rules instead of reading directly from the KRMS repository

9. March Focus: Development (cont.)
KRAD will be the UI tool for delivering KS application screens
Rich UI Support
Lightboxes
Messages
Progressive Disclosure
Client Side Validation
Table Tools A
Themes
AJAX Enabled Fields
More UI Flexibility Using KNS many screens can be generated through configuration, e.g., a business object lookup, inquiry and CRUD can be generated from an XML file

10. March Focus: Design
Continue to work on Core Slice Deliverables and their Governance
Develop Design Specification for Core Slice
What are the non-functional deliverables of each sprint?
What are the functional deliverables of each sprint?
What artifacts are required to support the above?
Non-functional requirements
Functional requirements
Data requirements
Screen flow

11. Project Planning/R2 Roadmap
The leadership team will be working on the overall roadmap for R2 as it will unfold after Core Slice development is complete. The plan will be delivered by Dan McDevitt at the Kuali Community Workshop in April, including ::
Third Party Integration
Degree Audit
Scheduling
Define chunks of functionality
Define effort estimates for completing each chunk
Define assumptions
Number of parallel teams
Make up of each parallel team

12. R2 Roadmap (cont.) Formalize/standardize how Parallel Teams will work
Structure
Roles
Processes
Design Specifications
Define timeline for R2
Check points for merging
Define KS Core team to support
R2 parallel teams
R1 implementations
Strategic partnerships
On-boarding of new partners