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

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


The Vision

Can We Make Kuali Student a ”Next Generation Student System?”


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


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


• 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


• 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


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


Collaboration Tools

• Face-to-Face Workshops

• Wiki, Googledocs

• Skype + Breeze

• IM and Googletalk

• HD video conferencing bridge

• Phone and email


Application Architecture Phase


Service Modeling and Contract Design

ApplicationArchitecture Goals

1. document High Level Functionality

2. id Service Candidates3. Domain Partitioning4. define Release 1 Scope

Primary Goals &Agile SOAD Methodology

Kuali StudentSOAD Methodology

Domain Discovery

Service Candidate Identification

Service Modeling andContract Design


1. DocumentHigh-levelBusiness

Requirements

Application Architecture

3.3 gather Institutional Specific Requirements

(institutional responsibility)

User Signoff

3.8 partition ServicesInto Applications

and Domains

3.9 validate againstConcierge Design

Principles

3.6 map InstitutionalRequirements toKuali Features

3.4 collect and documentUse Cases

3.5 Identify DataAbstractionTest Cases

3.5 Identify Rules Test

Cases

3.5 IdentifyOrchestration

Test Cases

3.2 create Business

Process Model

3.1 create Conceptual

Object Model

Signoff

3.7 identifyService

Candidates


Design Workshops

Document High-Level Requirements - Steps

BAsSMEs

Institutional Interviews


High-Level Requirements Teams & Deliverables

Jul

Aug

Sep Oct Nov

FunctionalStatements

ObjectModel

Swim Lanediagram


Application Architecture

3.3 gather Institutional Specific Requirements

(institutional responsibility)

User Signoff

3.8 partition ServicesInto Applications

and Domains

3.9 validate againstConcierge Design

Principles

3.6 map InstitutionalRequirements toKuali Features

3.4 collect and documentUse Cases

3.5 Identify DataAbstractionTest Cases

3.5 Identify Rules Test

Cases

3.5 IdentifyOrchestration

Test Cases

3.2 create Business

Process Model

3.1 create Conceptual

Object Model

Signoff

3.7 identifyService

Candidates

2. Service Candidate Identification

3. Domain Partitioning


Teams, Steps and Deliverables

Jul

Aug

Sep Oct Nov

Service X-Refs

diagram

DomainCapabilities

ServiceCandidates

Dec

…


4. Define Release 1 Scope


Service Modeling andContract Design


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



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


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


Next Steps

starting November 2008


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


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.


So What?


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


Questions?


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/)

• Kuali Studenthttps://test.kuali.org/confluence/display/KULSTU/Home

Documents

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