Project team leads for the Kuali Student Project gave a presentation at Kuali Days 2011 in Indianapolis to update the Kuali community on the Kuali Student Project.

1. Kuali Student Project
Update

2. Introductions
Dan McDevitt
KS Program Director
Indiana University
Carol Bershad
KS Product Manager
University of Washington
Rajiv Kaushik
KS Development Manager
University of Toronto

3. Agenda
 What is Kuali Student?
 Introduction to Kuali Student
 Overview of Core Functionality
 Who is Kuali Student?
 Founder and Partner Update
 When is Kuali Student being delivered?
 Three-Year Roadmap
 Product Updates
 How is Kuali Student being delivered?
 Delivery Overview
 Questions

4. What is Kuali Student?
Dan McDevitt | Indiana University

5. What is Kuali Student?
Kuali Student is a NEXT GENERATION STUDENT SYSTEM
which is ……
…….being incrementally produced through a dedicated community of
international higher education partners
…..meeting requirements of the community (not just the
requirements of a single institution)
……flexible to changing business processes
…… delivering a rich user experience
…… modular and scalable
.... HAPPENING!

6. What is Kuali Student?

7. Who is Kuali Student?
Dan McDevitt | Indiana University

8. Kuali Student Community
Founders Partners
Naval Post Graduate School Boston College
University of California, Berkeley Indiana University
University of North-West
Maryland, College Park University, South Africa
University of Southern California
University of Toronto
University of Washington
Founders = $~1 M/per year for 5 years….

9. When is Kuali Student Delivering?
Carol Bershad | University of Washington

10. KS Product Roadmap

11. KS Curriculum Management
What is this What features What is its
module? does it have? status?
Curriculum DELIVERED
• Courses and
Management
Program
provides the ability to Version 1.1
propose, create, modi • Robust proposal March 2011
fy and retire learning process
experiences that are Version 1.2
• Administrative
part of an institution's November 2011
CRUD screens
sanctioned
curriculum. • Analysis of Now in the “hands”
dependencies of the Community
across the
curriculum

12. KS Curriculum Management
 Implementations Institution Current Status
Boston College Planning and proof of concept
North-West University In Progress
UC Berkeley In Progress
University of Maryland In Progress
University of Washington In Progress (data migration)
 Ongoing support and enhancements
QUESTIONS DEFECTS ENHANCEMENTS
Defects submitted and Enhancements are
Questions addressed to
tracked in JIRA managed via the KS
Project and Community
https://jira.kuali.org/bro Contribution Model
ks.info@kuali.org
wse/KSLAB
ks.collab@kuali.org

13. KS Enrollment
What is this What features What is its
module? does it have? status?
KS Enrollment IN DEVELOPMENT
• Course
manages the
Registration
enrollment lifecycle … by the KS Project
of students once • Course Team
admitted to the Assessment
institution
• Program
Enrollment
• Program
Assessment
… and many more
(stay tuned)!

14. Institution Facing Student Facing
KS Curriculum 2.People and
Set up Users Manage Info and
2.People and
Management Permissions
Preferences
Permissions
9.Academic
Explore
Programs
Planning
KS
6.Program
Offer Offer
3.Course Accounts
Programs
Offering Courses
Offering
10.Academic
Academic Register for
4.Course 7.Program
Enroll in UW My
Record
Record Registration
Courses Enrollment
Programs Plan
KS Scheduling
5.Course
Grade
Assessment
Courses
9.Academic
Plan
Setup the Programs
Planning
1. Setup
Environment
Assess Progress in
8.Program KS Program
Assessment
Programs Audit
KS Enrollment: Framework

15. KS Enrollment : Roadmap
Institution Facing Student Facing
1. Set Up
2. People and Permissions
3. Course Offering
4. Course Registration
5. Course Assessment
ENR Feature Set
Basic1.0
6. Program Offering ENR 2.0 and Beyond
Full Feature Set
7. Program Enrollment
8. Program Assessment
9. Academic Planning
ENR 1.0
10. Academic Record ENR 2.0 and beyond
15

16. KS Enrollment Roadmap:
Functional Dependencies
Functional Area Dependent Module Strategy
Course
Offering
KS Curriculum Management DELIVERED
Program
Offering
3rd Party Integration R25
KS Scheduling (CollegeNET)
Course
Registration
Program Contribution
KS Accounts Sigma System, Inc
Enrollment
Program 3rd Party Integration
KS Program Audit u.Achieve® (redLantern)
Assessment
Academic
Planning Contribution
UW MyPlan University of Washington
16

17. UW MyPlan
What is What features What is its
UW MyPlan? does it have? status?
UW MyPlan is an • View enrollment IN DEVELOPMENT
academic planning history
tool that makes it … as a Contribution
easier for students • Explore curricular
offerings
to navigate the UW’s
curricular offerings • Perform
and achieve their program audit
academic goals. • Project academic
plan
• Share with advisor

18. KS Accounts
What is this What features What is its
module? does it have? status?
The Accounts • Assess tuition IN DEVELOPMENT
module supports and fees
the pricing, sale and • Access to … as a Contribution
purchase of both financial
internal and external planning tools
products (e.g. • Invoice
courses and customer
programs) and • Settle bill
services (e.g. • Maintain
athletics and library customer
fees) account
• Process refunds

19. KS Accounts
 The first vendor-contributed project designed as a core KS module
 Sigma Systems based in Denver, CO
 Forty years of experience in US higher education
 ProSAM, flagship financial aid package
 Sponsoring institutions are University of Maryland and University of
Southern California
 Planned KSA submodules:
 KSA – Receivables Management
 KSA – Fee Management
 KSA – Third Party
 KSA – Collections Management
 Submodules identified but not included:
 KSA – Scholarship Management
 KSA – Aid Management

20. KS Product Roadmap

21. How We Are Doing It

22. Development Philosophy
Embrace Iterative development
 A Module has 2 or more Releases
 Each Release is broken down into short Milestones
 Every Milestone delivers code which goes through QA
 Milestone code is available to KS community

23. Architecture

24. Kuali Student Architecture
Application
Jquery
Presentation Spring MVC
Rapid Application Development Framework (KRAD)
Service Contract Person Organization
SOAP (KIM) (KOM)
Service
Layer/ SOA Rules (KRMS)
Service Implementation
Workflow (KEW)
JAXWS/CXF
Notification (KEN)
Kuali Service Bus (KSB)
Data Access Object (DAO)
Persistence
JPA/Hibernate, OJB
Database
Database
DB Independent
Kuali Student
Kuali Rice
24

25. Architecture Implications
Truly a next generation Student System
 Infrastructure: Relies on a modern infrastructure
developed in the Cloud
 Separation of UI and Services enables institutions to
 Develop their own UIs
 Integrate with current systems on campus

26. Architecture Implications
Truly a next generation Student System
 Services are designed to accommodate future changes
to business processes.
 Front end can change every few years but Service Contracts
are more stable over time
 Loose coupling between modules helps institutions
 Roll out modules over time
 Minimize impact of changes from one module to another

27. Expert Review of Architecture
 Recent expert review of architecture validates that
platform
 Has a solid foundation
 Will be adoptable as production enterprise software
 Will run with appropriate availability/scalability
 Has no "red flag" issues
 Has come areas of concern/improvement

28. Development Strategy

29. Phase I – Core Slice
Breadth
PHASE 1 – Foundation (“thin slice”)
Depth
Course offerings, students, registration, grading, academic record, others
Manage Manage Grading, R Fees, Trans
Learning Course Degree
Course People and ecord, Tran fer Credit
Plan Registration Audit
Offerings Time script

30. Phase II- Enrollment 1 Parallel Development
Breadth
Team A Team D Team B
Depth
PHASE 2 – Expand Depth with Parallel Dev Teams
Team A Team B Team C
Manage Manage Grading, R Fees,
Learning Course Degree
Course People and ecord, Tran Transfer
Plan Registration Audit
Offerings Time script Credit

31. Teams West Coast 2
West Coast 1
9
9
East Coast 1
9
ANALYSIS 9
MGMT
UX
South Africa
QA
26
SVCS
DEV 9
East Coast 2
Team Structure to Support Strategy 31

32. Parallel Development Teams
 Parallel Development Teams focus
 Application Development
 Broad swath across features
 Minimal UI progressing to richer UX
 Deliver code in three 2-week sprints as part of each Milestone
32

33. Core Team
 Core Team focus
 Overall application design, ensuring one cohesive application
 Service Contracts, including implementation (80/20), allowing
parallel teams to focus on application development
 Technical Strategy
 Performance
 Scaling
 Database
33

34. Wrap up

35. Challenges / Opportunities
 Balancing the reality triangle Resources Scope
Time
 Software support vs. Software development
(Evolving Ecosystem)
 Core system being build from ground up vs. based
off existing system

36. Get Involved
Round Table on Choosing to Join Kuali Student
Wednesday, 2:30-3:30pm
Room 101/102
Kuali Student Project Round Table
Wednesday, 4:00-5:00pm
White River B

37. Questions?