1. Kuali Days :: Chicago May 13-14 Overview of Kuali Student Application Architecture Rick Burnette (FSU) Gord Uyeda (UBC) Kuali Days :: Chicago May 13-14, 2008

2. Kuali Days :: Chicago May 13-14 The Vision Can We Make Kuali Student a ”Next Generation Student System?”

3. Kuali Days :: Chicago May 13-14 Vision Statement support end users by anticipating their needs support a wide range of learners and learning activities. support a wide range of business processes flexibility to make it easier to change business processes to meet institution needs reduce time staff spend on routine tasks allow for Extensibility for the future changes and growth

4. Kuali Days :: Chicago May 13-14 Presentation Objectives Provide a summary of the Functional side of the Kuali Student –How we are structured –What the teams did –What the teams are currently working on –What’s next –How to get more info

5. Kuali Days :: Chicago May 13-14 Person Identity Learning Unit Management Enrollment Program Audit and Academic Evaluation –supports evaluation, status towards Learning Objectives –supports ongoing evaluation of academic progress Person Identity Learning Unit Management Enrollment –manages Learner to LU relationships –manages Provider to LU relationships –manages Learning Results Person Identity Learning Unit Management Enrollment Program Audit and Academic Evaluation Student Financials –Product pricing –assessment of additional Fees –determine Invoice and Payment plans –Payment processing Person Identity –manage Person info –support Authorization, Authentication –manage Groups, Organizations –manage Contact info Person Identity Learning Unit Management –manage catalog of Learning Experiences –manage creation, approval new LUs –manage evaluation, review of existing LUs Tier 1 Business Domains

6. Kuali Days :: Chicago May 13-14 Admissions Scheduling Financial Aid –manage Awards, Financial Aid Resources –maintain student Characteristics and Needs –assign Awards to students Admissions Scheduling –manage LU “offerings” –schedule Resources –manage Calendars Admissions –capture Application info –manage Evidence –automate process workflow –evaluate Learner’s qualifications Tier 2 Business Domains

7. Kuali Days :: Chicago May 13-14 other Business Domains Recruitment Event Management Housing Athletics Alumni Development Family Financial Planning Elections Student Life Out of Scope –Learning Management System –Student Portfolio –Financial (FMIS) system –Campus Calendar –Facilities Management –Library –Parking

8. Kuali Days :: Chicago May 13-14 Collaboration Tools Face-to-Face Workshops Wiki, Googledocs Skype + Breeze IM and Googletalk HD video conferencing bridge Phone and email

9. Kuali Days :: Chicago May 13-14 Application Architecture Phase

10. Kuali Days :: Chicago May 13-14 Service Modeling and Contract Design Application Architecture Goals 1.document High Level Functionality 2.id Service Candidates 3.Domain Partitioning 4.define Release 1 Scope Primary Goals & Agile SOAD Methodology Kuali Student SOAD Methodology Domain Discovery Service Candidate Identification Service Modeling and Contract Design

11. Kuali Days :: Chicago May 13-14 1. Document High-level Business Requirements Application Architecture 3.3 gather Institutional Specific Requirements (institutional responsibility) User Signoff 3.8 partition Services Into Applications and Domains 3.9 validate against Concierge Design Principles 3.6 map Institutional Requirements to Kuali Features 3.4 collect and document Use Cases 3.5 Identify Data Abstraction Test Cases 3.5 Identify Rules Test Cases 3.5 Identify Orchestration Test Cases 3.2 create Business Process Model 3.1 create Conceptual Object Model Signoff 3.7 identify Service Candidates

12. Kuali Days :: Chicago May 13-14 Design Workshops Document High-Level Requirements - Steps BAs SMEs Institutional Interviews

13. Kuali Days :: Chicago May 13-14 High-Level Requirements Teams & Deliverables Jul Aug Sep Oct Nov Functional Statements Object Model Swim Lane diagram

14. Kuali Days :: Chicago May 13-14 Application Architecture 3.3 gather Institutional Specific Requirements (institutional responsibility) User Signoff 3.8 partition Services Into Applications and Domains 3.9 validate against Concierge Design Principles 3.6 map Institutional Requirements to Kuali Features 3.4 collect and document Use Cases 3.5 Identify Data Abstraction Test Cases 3.5 Identify Rules Test Cases 3.5 Identify Orchestration Test Cases 3.2 create Business Process Model 3.1 create Conceptual Object Model Signoff 3.7 identify Service Candidates 2.Service Candidate Identification 3.Domain Partitioning

15. Kuali Days :: Chicago May 13-14 Teams, Steps and Deliverables Jul Aug Sep Oct Nov Service X-Refs diagram Domain Capabilities Service Candidates Dec …

16. Kuali Days :: Chicago May 13-14 4. Define Release 1 Scope

17. Kuali Days :: Chicago May 13-14 Service Modeling and Contract Design

18. Kuali Days :: Chicago May 13-14 4.1 collect and extend Use Cases 4.2 develop and extend Test Cases Signoff 4.6 validate Service Definitions Iteration 2 4.5 define Service and Contracts Iteration 2 Iterative Refinement 4.4 validate Service Definitions Iteration 1 Iterative Refinement 4.3 define Service and Contracts Iteration 1 4.7 User Interface Design (Style Templates and UI Models) Service Modeling & Contract Design outputsinputs Service Candidates Object Model Use Case Object Model Service Capabilities UI Style Template Design Specs … as required, time permitting Service X-Refs diagram Swim Lane diagram Service X-Refs diagram Swim Lane diagram Functional Statements Service Description & Contract Design

19. Kuali Days :: Chicago May 13-14 Service Design Teams Use Case Team –User Scenario Subject Matter Experts –Service/Case Analysts Data Team –Data Structures and Service Message Structures Services Team –Service Factoring + Service Stack Composition –Service Operations + Service Contracts

20. Kuali Days :: Chicago May 13-14

21. Service Design Scope The current focus of the services teams is on: Learning Unit Management Person Identity –Person and Organization Management Services Common Services –Rules –Workflow –Communication

22. Kuali Days :: Chicago May 13-14 Service Design Deliverables By November, the services teams will: Produce Service Definitions, Contracts and Message Structures for the defined services. Produce a mature set of user scenarios, test use cases and reference implementation cases Provide validation of released service iterations and modify services until finalized

23. Kuali Days :: Chicago May 13-14 Next Steps starting November 2008

24. Kuali Days :: Chicago May 13-14 6.1.1 UI Design with Users (screen mock-ups) Iterative Refinement 6.1.2 Software Design (User Facing Components) 6.1.3 Software Design (Business Controller) 6.1.4 Code/test Web Application Components 6.1.5 Code/test Business Controller Components 6.2.3 develop Services 6.2.4 implement Orchestrated Services 6.2.1 Software Design (Service) 6.2.2 Service Orchestration Design (Ref Implementation) User Facing Components Service Implementations Software DesignSoftware Development Software Design & Development outputsinputs Iterative Refinement 6.3 prepare Documentation package UI Style Template Design Specs Use Case Re-Usable Interface Components Sequence diagrams/ Service Interactions Class Diagrams Deployable UI Components Deployable services db Configuration guide Installation guide System overview Service Contract Design Coding Standards Service Orchestration design Service X-Ref diagram

25. Kuali Days :: Chicago May 13-14 Release 1 Development Beginning in November, the services teams and will support both Release 1 development and Release 2 Service Modeling and Contract Design Functional Team members (Use Case, Data and UX) will work with the technical teams on the development of the Release 1 application implementation

26. Kuali Days :: Chicago May 13-14 Release 2 Service Design The bulk of the services teams will begin working on Service Modeling and Contract Design for Release 2. This work will likely be focused on designing services around the Enrollment Module.

27. Kuali Days :: Chicago May 13-14 So What?

28. Kuali Days :: Chicago May 13-14 What we Learned? Collaboration Experience –Distance challenges –Inter-institutional interactions –Team dynamics Flexibility of the Learning Unit Construct The User Experience/Concierge Focus We produced a new SOAD Model

29. Kuali Days :: Chicago May 13-14 Why is KS Different? SOAD Methodology –SOA + Community Source = Self Determination / Supported Autonomy –Extensibility –Configuration Framework Separation of Data, Rules, Workflows Learning Unit Construct User Experience versus User Interface Concierge Internationalization – Language and Model Support

30. Kuali Days :: Chicago May 13-14 Questions?

31. Kuali Days :: Chicago May 13-14 Need More Information? Kuali Days Functional Presentations –Evolving a New Agile Service Oriented Analysis and Design (SOAD) Methodology (Tues 2:15 ) –KS Person Identity & Learning Unit Management Service Design (Tues 3:45) –Electronic Concierge (Tues 5:00) –Learning Unit Management II and other Topics (Wed 11:00) –KS User Interface (Wed 2:15) Kuali Foundation (http://kuali.org/)http://kuali.org/ Kuali Student https://test.kuali.org/confluence/display/KULSTU/Home