Kuali Student UX
Kuali Student Overview Richard Spencer. Executive Director IT, University of British Columbia AACRAO, Chicago IL, April 15, 2009
Kuali Student is... a community source development project a partnership of more than 10 institutions focused on the needs of users a better solution for institutions 222 standards-based, SOA, open source making progress, with real deliverables
....this not“enthusiastic a sales pitch!believers”! but weisare 2
Agenda • • • • • • •
Why Kuali Student now? The Kuali vision Functional design Technical architecture 333 Project scope Timelines and progress Community source, partnerships 3
Why Kuali Student now?
Student system history • BC – paper based processes – information silos in separate departments – the customer had to help us run the institution
• SRS – on-line records, flat files, 555 reports
• SIS – support for core processes in core departments – we began to help the customer – often more work & time for other users 5
5
Why Kuali Student? Many student systems need to be replaced New technology should let us do more Vendor solutions are not the answer for some Development of systems in-house is challenging Partnerships and open source system development 666 works • Community source let’s us build systems that: • • • • •
– do more for institutions – do more for users 6
The Kuali Vision
Functional • Focus on needs of all users – anticipate their needs and simplify tasks • Support a wide range of learners and learning activities activities. • Support a wide range888 of academic and business processes. • Make it easier to change rules and processes • Store data outside the system, improve access 8
Technical • Develop an architecture based on Serviceorientation, implemented using Web Services. source, standard components • Use open source • Publish service contract 999 specifications • Develop and use services that can be shared with other campus systems. • Define and publish standards for development 9
Sustainability • Founders will implement the core services • Adoption and implementation elsewhere • A community of interest to sustain maintenance and development. • Defined product development and support 101010 processes to help implementation and support • Participation by vendors and service providers • Continue to evolve the technology and architecture 10
10
Functional design
Functional Design Concepts • High level entities – learning units, person identity, time
• Concierge – use what we know to help people achieve their goals
• Rules R l engines, i workk fl flow – rules and logic are not121212 in the code
• Modular, configurable system
– your processes, not someone else’s “best practices”
• Managed access to information – people can see what they should be able to see 12
Learning Units • A learning unit can represent: – a course; a single lecture in a course; a 15 minute student presentation in a course – a degree program – a coop work placement placement, an overseas work experience – any non-credit, continuing studies, or other activity
• We can also have:
131313
– learning results – learning plans – learning resources 13
Person Kuali Student’s use of identity management: • • • • • • • •
people are entities easy to create an online identity authentication is standard across systems y authorization based on roles and rules 141414 role creation by people or applications authority is easily delegated when appropriate good tools for role and group management Identity management is an institutional service 14
Person-centric identity model
151515
15
Concierge • use what we know about: – the person, the rules, the experience of others
• suggest valid choices – don’t make the user wade through choices that don’t apply
• apply and explain the relevant rules – don don’tt expect the user to read and understand the regulations
• anticipate peoples needs
161616 – these courses meet your requirements and match your interests
• integrate processes to make things easier – do you want to apply your tuition credit to your child’s registration?
• implement using rules and workflow support the for endthings user! we know how to do! no training 16 16
Concierge We should use: Personal Information
Institutional Information Requirements
Record
Options
171717
Experiences of others
Rules Possibilities
Status Goals
to support users
Pitfalls 17 17
Concierge in action ability to register triggered by accepting offer of admission
Concierge “sees” student accept offer Concierge “knows” rules and process
Concierge sits looking and listening for changes in a person’s state, institution rules, peoples experiences, etc.
Concierge checks student info, 181818 program, required courses, elective opportunities, and guides student to solution process ends when student has a complete program that meets her needs
18 18
Uses Information Rules engine Workflow
Rules
191919
19
...other design concepts • Modular – modules can be used with existing systems
• Configurable – rules l and d workflow kfl are externall to the h code d 202020 • Managed access to information
– data is outside the core system – all access is through a data abstraction layer
20
Technical architecture
Technical objectives: • Service Oriented Architecture – SOA, web services, standards based – Separate governance process for service contracts
• Component abstraction – Abstraction of: • presentation layer • business processes • data layer
222222
• Use open source technology – Use an open source software stack – Java as the language of choice 22
Application Architecture User
Portal Concierge
Business us ess Services Infrastructure Services Technology Stack
Concierrge
Applications
Curriculum management
Admission
Registration
Learning Unit service
Evaluation service
Enrolment service
Rules service
Identity service
Services framework
Rules engine
232323 Workflow service Data
23
Technical architecture
242424
24
Project scope
Functional Scope Tier 1 Functionality
Tier 2 Functionality
Curriculum Development Customer contact Configuration application Enrolment Degree Audit and Academic 262626 Evaluation – Student Financials – Concierge – limited – Application connectors – – – – –
26
– – – –
Admissions Scheduling Awards and Financial Aid Concierge
26
Out of Scope Complementary Modules – – – – – – – –
Third Party Systems
Recruitment Event Management Housing Athletics Alumni 272727 Family Financial Planning Elections Student Life
27
– Learning Management System – Student Portfolio – Financial (FMIS) system – Campus Calendar – Facilities Management – Library – Parking
Timelines and progress
Timeline
292929
29
Phased Modular Approach Application Architecture Technical Architecture
Architectural Activities Development Infrastructure
One Time only
Develop Infrastructure Services User Requirements R1 Services Modeling & Contract Design R1
303030
Application Design R1
Release Activities
Software Development R1
Repeat for each Release
Implementation Support R1
Release 2
30
Where we are today Middleware services Identity: Authorization Service Identity: Group Service Identity: Role Service Identity: y Authentication Service Identity: Organization Service 313131 Person Service Workflow Search interface Dictionary interface Business Rules 31
Availability Now Now Now Now June June Now Now June Now
Community source, partnerships
Founder & Partners Founders • • • • • • • •
University of British Columbia University of California, Berkeley University of Maryland, College Park Florida State University San Joaquin Delta College University of Southern California University of Washington Carnegie Mellon University 333333
Partners • • •
Massachusetts Institute of Technology Naval Postgraduate Institute Cambridge University
33
Other Supporters Supported by:
• AACRAO • NITLE Advancing liberal education in the digital age
343434
The Andrew W. Mellon Foundation
34
Why Community Source? • Benefits – Shared resources = lower total development cost – Institutions share ideas and solutions – Community ensures sustainability – Commercial affiliates can provide support 353535 • Outcomes - Kuali Student will – Make all code available on a public website – Publish procedures and standards for use by others – Build a community to sustain, and add functionality 35
Paths to adoption • Stay connected and informed – KS newsletter – email Jennifer Foutty ([email protected]) – KS website – student.kuali.org – Kuali Days events – Fall 2009
• Join the Kuali Foundation – Help build the community 363636
• Try modules as they are released – Down load and try open source code – Implement and configure – (work with a vendor?) – Share implementation experiences and enhancements 36
If it’s free, why contribute? • Software is a fraction of the total cost … – implementation, user support – configuration, customization, maintenance … all cost dearly and require resources • Becoming an active member … 373737 – of a Kuali Project, or the Kuali Foundation …is the least expensive way to grow these resources Participation buys influence, helps implementation 37
Information
www.student.kuali.orgg 383838
Email: [email protected]
38
Kuali Student is... a community source development project a partnership of more than 10 institutions focused on the needs of users a better solution for institutions 222 standards-based, SOA, open source making progress, with real deliverables
....this not“enthusiastic a sales pitch!believers”! but weisare 2
Agenda • • • • • • •
Why Kuali Student now? The Kuali vision Functional design Technical architecture 333 Project scope Timelines and progress Community source, partnerships 3
Why Kuali Student now?
Student system history • BC – paper based processes – information silos in separate departments – the customer had to help us run the institution
• SRS – on-line records, flat files, 555 reports
• SIS – support for core processes in core departments – we began to help the customer – often more work & time for other users 5
5
Why Kuali Student? Many student systems need to be replaced New technology should let us do more Vendor solutions are not the answer for some Development of systems in-house is challenging Partnerships and open source system development 666 works • Community source let’s us build systems that: • • • • •
– do more for institutions – do more for users 6
The Kuali Vision
Functional • Focus on needs of all users – anticipate their needs and simplify tasks • Support a wide range of learners and learning activities activities. • Support a wide range888 of academic and business processes. • Make it easier to change rules and processes • Store data outside the system, improve access 8
Technical • Develop an architecture based on Serviceorientation, implemented using Web Services. source, standard components • Use open source • Publish service contract 999 specifications • Develop and use services that can be shared with other campus systems. • Define and publish standards for development 9
Sustainability • Founders will implement the core services • Adoption and implementation elsewhere • A community of interest to sustain maintenance and development. • Defined product development and support 101010 processes to help implementation and support • Participation by vendors and service providers • Continue to evolve the technology and architecture 10
10
Functional design
Functional Design Concepts • High level entities – learning units, person identity, time
• Concierge – use what we know to help people achieve their goals
• Rules R l engines, i workk fl flow – rules and logic are not121212 in the code
• Modular, configurable system
– your processes, not someone else’s “best practices”
• Managed access to information – people can see what they should be able to see 12
Learning Units • A learning unit can represent: – a course; a single lecture in a course; a 15 minute student presentation in a course – a degree program – a coop work placement placement, an overseas work experience – any non-credit, continuing studies, or other activity
• We can also have:
131313
– learning results – learning plans – learning resources 13
Person Kuali Student’s use of identity management: • • • • • • • •
people are entities easy to create an online identity authentication is standard across systems y authorization based on roles and rules 141414 role creation by people or applications authority is easily delegated when appropriate good tools for role and group management Identity management is an institutional service 14
Person-centric identity model
151515
15
Concierge • use what we know about: – the person, the rules, the experience of others
• suggest valid choices – don’t make the user wade through choices that don’t apply
• apply and explain the relevant rules – don don’tt expect the user to read and understand the regulations
• anticipate peoples needs
161616 – these courses meet your requirements and match your interests
• integrate processes to make things easier – do you want to apply your tuition credit to your child’s registration?
• implement using rules and workflow support the for endthings user! we know how to do! no training 16 16
Concierge We should use: Personal Information
Institutional Information Requirements
Record
Options
171717
Experiences of others
Rules Possibilities
Status Goals
to support users
Pitfalls 17 17
Concierge in action ability to register triggered by accepting offer of admission
Concierge “sees” student accept offer Concierge “knows” rules and process
Concierge sits looking and listening for changes in a person’s state, institution rules, peoples experiences, etc.
Concierge checks student info, 181818 program, required courses, elective opportunities, and guides student to solution process ends when student has a complete program that meets her needs
18 18
Uses Information Rules engine Workflow
Rules
191919
19
...other design concepts • Modular – modules can be used with existing systems
• Configurable – rules l and d workflow kfl are externall to the h code d 202020 • Managed access to information
– data is outside the core system – all access is through a data abstraction layer
20
Technical architecture
Technical objectives: • Service Oriented Architecture – SOA, web services, standards based – Separate governance process for service contracts
• Component abstraction – Abstraction of: • presentation layer • business processes • data layer
222222
• Use open source technology – Use an open source software stack – Java as the language of choice 22
Application Architecture User
Portal Concierge
Business us ess Services Infrastructure Services Technology Stack
Concierrge
Applications
Curriculum management
Admission
Registration
Learning Unit service
Evaluation service
Enrolment service
Rules service
Identity service
Services framework
Rules engine
232323 Workflow service Data
23
Technical architecture
242424
24
Project scope
Functional Scope Tier 1 Functionality
Tier 2 Functionality
Curriculum Development Customer contact Configuration application Enrolment Degree Audit and Academic 262626 Evaluation – Student Financials – Concierge – limited – Application connectors – – – – –
26
– – – –
Admissions Scheduling Awards and Financial Aid Concierge
26
Out of Scope Complementary Modules – – – – – – – –
Third Party Systems
Recruitment Event Management Housing Athletics Alumni 272727 Family Financial Planning Elections Student Life
27
– Learning Management System – Student Portfolio – Financial (FMIS) system – Campus Calendar – Facilities Management – Library – Parking
Timelines and progress
Timeline
292929
29
Phased Modular Approach Application Architecture Technical Architecture
Architectural Activities Development Infrastructure
One Time only
Develop Infrastructure Services User Requirements R1 Services Modeling & Contract Design R1
303030
Application Design R1
Release Activities
Software Development R1
Repeat for each Release
Implementation Support R1
Release 2
30
Where we are today Middleware services Identity: Authorization Service Identity: Group Service Identity: Role Service Identity: y Authentication Service Identity: Organization Service 313131 Person Service Workflow Search interface Dictionary interface Business Rules 31
Availability Now Now Now Now June June Now Now June Now
Community source, partnerships
Founder & Partners Founders • • • • • • • •
University of British Columbia University of California, Berkeley University of Maryland, College Park Florida State University San Joaquin Delta College University of Southern California University of Washington Carnegie Mellon University 333333
Partners • • •
Massachusetts Institute of Technology Naval Postgraduate Institute Cambridge University
33
Other Supporters Supported by:
• AACRAO • NITLE Advancing liberal education in the digital age
343434
The Andrew W. Mellon Foundation
34
Why Community Source? • Benefits – Shared resources = lower total development cost – Institutions share ideas and solutions – Community ensures sustainability – Commercial affiliates can provide support 353535 • Outcomes - Kuali Student will – Make all code available on a public website – Publish procedures and standards for use by others – Build a community to sustain, and add functionality 35
Paths to adoption • Stay connected and informed – KS newsletter – email Jennifer Foutty ([email protected]) – KS website – student.kuali.org – Kuali Days events – Fall 2009
• Join the Kuali Foundation – Help build the community 363636
• Try modules as they are released – Down load and try open source code – Implement and configure – (work with a vendor?) – Share implementation experiences and enhancements 36
If it’s free, why contribute? • Software is a fraction of the total cost … – implementation, user support – configuration, customization, maintenance … all cost dearly and require resources • Becoming an active member … 373737 – of a Kuali Project, or the Kuali Foundation …is the least expensive way to grow these resources Participation buys influence, helps implementation 37
Information
www.student.kuali.orgg 383838
Email: [email protected]
38
