Kuali Student: A Next Generation Student System


Published on

  • Be the first to comment

  • Be the first to like this

Kuali Student: A Next Generation Student System

  1. 1. … the next generation student system is coming! Kuali Days V November 14, 2007
  2. 2. Agenda <ul><li>Why now? </li></ul><ul><li>The vision </li></ul><ul><li>Functional design and scope </li></ul><ul><li>Technical architecture </li></ul><ul><li>Development approach </li></ul><ul><li>Community source </li></ul><ul><li>Where we are and where we’re going </li></ul>
  3. 3. Why Now? <ul><li>Many student systems don’t meet current needs </li></ul><ul><li>Vendor solutions may not be the answer </li></ul><ul><li>Development of in-house systems is challenging </li></ul><ul><ul><li>Increasingly complex technology requires specialist resources </li></ul></ul><ul><ul><li>Competing for scarce IT resources in a constrained market </li></ul></ul><ul><ul><li>User requirements and expectations increasing rapidly </li></ul></ul><ul><ul><li>Budgets and funding are constrained </li></ul></ul><ul><li>Collaboration and open source systems development works </li></ul><ul><li>We can build systems that do more for users </li></ul>
  4. 4. Vision: Functional Objectives <ul><li>Support end users by anticipating their needs and simplifying (or eliminating) administrative tasks. </li></ul><ul><li>Support a wide range of learners and learning activities. </li></ul><ul><li>Support a wide range of business processes , including those that cross department and system boundaries. </li></ul><ul><li>Make it easier to change business processes to meet institution needs and allow process improvement, using rules and workflow, configurable systems, and flexible data models. </li></ul><ul><li>Reduce time staff spend on routine tasks , so they can do more to directly support students and faculty. </li></ul>
  5. 5. Vision: Sustainability <ul><li>Ensure the core services of Kuali Student are successfully implemented by the Founding Institutions . </li></ul><ul><li>Promote the adoption and implementation of Kuali Student by a wide variety of educational institutions – in North America and internationally. </li></ul><ul><li>Build a community of interest that will sustain future maintenance, enhancement and development. </li></ul><ul><li>Define product development and support processes that will help the community implement the software and provide operational support. </li></ul><ul><li>Facilitate participation by vendors and service providers </li></ul><ul><li>Evolve the technology and architecture of Kuali Student to keep up with new standards, tool releases and trends. </li></ul>
  6. 6. Vision: Technical Objectives <ul><li>Develop a next generation architecture based on Service-orientation , implemented using Web Services . </li></ul><ul><li>Publish service contract specifications . This will allow a large community work on the system. </li></ul><ul><li>Produce a software product based on a set of services . </li></ul><ul><li>Define and publish standards for development that can be used by others to develop services that are outside the scope of the core product. </li></ul>
  7. 7. Functional design: Elements <ul><li>High level entities </li></ul><ul><ul><li>person; time; learning units </li></ul></ul><ul><li>Concierge </li></ul><ul><li>Rules engines </li></ul><ul><li>Work flow </li></ul><ul><li>Modular, configurable system </li></ul><ul><li>Managed access to information </li></ul><ul><li>Internationalization </li></ul>
  8. 8. Learning units <ul><li>Course; single lecture in a course; 15 minute student presentation in a course </li></ul><ul><li>Participation in community service </li></ul><ul><li>Any activity that the student wants to include on a formal or co-curricular transcript </li></ul><ul><li>A “learning unit number” is like a SKU... </li></ul><ul><li>We can also have: </li></ul><ul><ul><li>learning results </li></ul></ul><ul><ul><li>learning plans </li></ul></ul><ul><ul><li>learning resources </li></ul></ul>
  9. 9. Concierge Institutional Information Requirements Personal Information Goals Information about the experiences of others Possibilities We should use: to support users
  10. 10. Concierge Concierge sits looking and listening for changes persons state, institution rules, peoples experiences, etc. Concierge “sees” student complete registration requirement to pay fees triggered by completing registration Concierge checks student info, rules & financial aid opportunities and guides student through process process ends when fees are paid Rules engine Workflow Uses Information
  11. 11. Functional Scope <ul><li>Tier 1 Functionality </li></ul><ul><ul><li>Curriculum Development </li></ul></ul><ul><ul><li>Customer contact </li></ul></ul><ul><ul><li>Configuration application </li></ul></ul><ul><ul><li>Enrolment </li></ul></ul><ul><ul><li>Degree Audit and Academic Evaluation </li></ul></ul><ul><ul><li>Student Financials </li></ul></ul><ul><ul><li>Concierge – limited </li></ul></ul><ul><ul><li>Application connectors </li></ul></ul><ul><li>Tier 2 Functionality </li></ul><ul><ul><li>Admissions </li></ul></ul><ul><ul><li>Scheduling </li></ul></ul><ul><ul><li>Awards and Financial Aid </li></ul></ul><ul><ul><li>Concierge </li></ul></ul>
  12. 12. Out of Scope Functionality <ul><li>Tier 3 – Out of scope for Founders </li></ul><ul><ul><li>Recruitment </li></ul></ul><ul><ul><li>Event Management </li></ul></ul><ul><ul><li>Housing </li></ul></ul><ul><ul><li>Athletics </li></ul></ul><ul><ul><li>Alumni </li></ul></ul><ul><ul><li>Family Financial Planning </li></ul></ul><ul><ul><li>Elections </li></ul></ul><ul><ul><li>Student Life </li></ul></ul><ul><li>Out of Scope </li></ul><ul><ul><li>Learning Management System </li></ul></ul><ul><ul><li>Student Portfolio </li></ul></ul><ul><ul><li>Financial (FMIS) system </li></ul></ul><ul><ul><li>Campus Calendar </li></ul></ul><ul><ul><li>Facilities Management </li></ul></ul><ul><ul><li>Library </li></ul></ul><ul><ul><li>Parking </li></ul></ul>
  13. 13. Functional Scope and Timeline
  14. 14. Technical architecture: Guiding principles <ul><li>Service Oriented Architecture </li></ul><ul><ul><ul><li>SOA methodology </li></ul></ul></ul><ul><ul><ul><li>Web services </li></ul></ul></ul><ul><ul><ul><li>Standards based (WS and industry standards) </li></ul></ul></ul><ul><ul><ul><li>Separate governance process for service contracts </li></ul></ul></ul><ul><ul><li>Component Abstraction </li></ul></ul><ul><ul><ul><li>Abstraction of business processes and business rules </li></ul></ul></ul><ul><ul><ul><li>Abstraction of presentation layer via a portal </li></ul></ul></ul><ul><ul><ul><li>Abstraction of the data layer </li></ul></ul></ul><ul><ul><li>Leverage Open Source Technology </li></ul></ul><ul><ul><ul><li>Use an open source software stack </li></ul></ul></ul><ul><ul><ul><li>Infrastructure built from open source products </li></ul></ul></ul><ul><ul><ul><li>Java as the language of choice </li></ul></ul></ul>
  15. 15. Technical Architecture
  16. 16. Developers Workbench
  17. 17. Configuration Application
  18. 18. Development Approach <ul><li>Development project structure </li></ul><ul><ul><li>5 + year project starting July 2007 </li></ul></ul><ul><ul><li>Well defined phases of approximately 4-6 months each </li></ul></ul><ul><ul><li>Clear definition of deliverables at each stage </li></ul></ul><ul><ul><li>Each phase delivers a tangible asset </li></ul></ul><ul><ul><li>QA reviews and checkpoints at the end of each phase </li></ul></ul><ul><ul><li>Sign off of phase deliverables as complete </li></ul></ul><ul><ul><li>Review plans for the next phase at the end of each phase </li></ul></ul><ul><li>Separate implementation projects at each institution </li></ul><ul><ul><li>Kuali Student does NOT include implementation </li></ul></ul><ul><ul><li>Product is “configured” for institution by a separate team </li></ul></ul><ul><ul><ul><li>dictionary; search; rules; BPEL; authorization </li></ul></ul></ul><ul><li>Agility, phases, time boxing, reusability and iterations </li></ul>
  19. 19. Technical Stream Functional Stream Jul 2007 Sep 2008 Oct 2008 Apr 2009 Jun 2009 July 2009 <ul><li>Application Architecture </li></ul><ul><li>- Process models </li></ul><ul><li>ER models </li></ul><ul><li>High Level Service Models </li></ul><ul><li>Domain Definitions </li></ul><ul><li>Technical Architecture </li></ul><ul><li>Technology proofs </li></ul><ul><li>SOA standards </li></ul>Service Modeling R1 (Infrastructure & Curriculum Development) <ul><li>Development Infrastructure </li></ul><ul><li>Developers workbench </li></ul><ul><li>Procedures </li></ul><ul><li>Standards </li></ul>Contract Design R1 (Infrastructure & Curriculum Development) Service Modeling R2 (Domain 2) Software Design & Development R1 (Infrastructure & Domain 1) Adjust plans and repeat for Releases 2/3/4 Program Management & Communications Contract Design R2 (Domain 2) Release 1 & Implement Test Re-plan / Re-Architect / Implement & Transition to Support <ul><li>Develop Configuration </li></ul><ul><li>Application </li></ul><ul><li>Configuration Infrastructure </li></ul><ul><li>Proof of concept Pilot </li></ul>Phased Modular Approach
  20. 20. Why Community Source? <ul><li>Benefits </li></ul><ul><ul><li>Shared resources means more efficient development </li></ul></ul><ul><ul><li>Institutions share ideas and create innovative solutions, leveraging their user experiences </li></ul></ul><ul><ul><li>Contributing institutions have direct input into functions and features </li></ul></ul><ul><ul><li>Sustainability – a community that contributes to enhancements can ensure sustained development </li></ul></ul><ul><ul><li>Support – commercial partners for implementation and support are encouraged </li></ul></ul><ul><li>Kuali Student will </li></ul><ul><ul><li>Build a community of interest </li></ul></ul><ul><ul><li>Establish procedures and standards for development </li></ul></ul><ul><ul><li>Encourage commercial affiliates </li></ul></ul><ul><ul><li>Share implementation experiences </li></ul></ul>
  21. 21. Founder & Partners <ul><li>Partners </li></ul><ul><li>Massachusetts Institute of Technology </li></ul><ul><li>Carnegie Mellon University </li></ul><ul><li>Founders </li></ul><ul><li>University of British Columbia </li></ul><ul><li>University of California, Berkeley </li></ul><ul><li>University of Maryland, College Park </li></ul><ul><li>Florida State University </li></ul><ul><li>San Joaquin Delta College </li></ul>
  22. 22. Other Partners <ul><li>Supported by: </li></ul><ul><li>AACRAO </li></ul><ul><li>NITLE </li></ul>The Andrew W. Mellon Foundation
  23. 23. An Opportunity to Contribute <ul><li>Align with the vision </li></ul><ul><li>Membership in the Kuali Foundation </li></ul><ul><li>Contribute funds toward the development of Kuali Student </li></ul><ul><li>Express an interest in implementing one or more modules </li></ul><ul><li>Abide by the provisions of the Educational Community License </li></ul><ul><li>Act as an advocate for the Program </li></ul>
  24. 24. Benefits of Contributing <ul><li>Able to provide specific input on product directions, needs and expectations </li></ul><ul><li>Access to project documentation and artifacts as they are developed </li></ul><ul><li>May participate in Beta testing and may have early access to software for testing and implementation </li></ul><ul><li>May contribute to bug fixes and enhancements to ensure the quality of the end product </li></ul><ul><li>May contribute implementation experiences and materials back to the community body of knowledge </li></ul><ul><li>May provide input to the development of support processes and product release strategies. </li></ul>
  25. 25. Other Opportunities <ul><li>Founders </li></ul><ul><li>Partners </li></ul><ul><li>Contributors </li></ul><ul><li>Adopters </li></ul><ul><ul><li>commitment to adopt some modules </li></ul></ul><ul><li>Supporters </li></ul><ul><ul><li>display the bumper sticker </li></ul></ul>
  26. 26. <ul><li>Technology </li></ul><ul><li>Business Analysis (SOA) </li></ul><ul><li>Lack of Appropriate Skills </li></ul><ul><li>Failure of the Partnership </li></ul><ul><li>Size, Scope, and Complexity </li></ul><ul><li>SOA Approach </li></ul><ul><li>Standards Compliance </li></ul><ul><li>SME Staff Availability </li></ul><ul><li>Budget / Cost Estimates </li></ul><ul><li>Funding </li></ul><ul><li>Departure of Key Members (Board, Steering, other) </li></ul><ul><li>Working with a distributed team </li></ul><ul><li>Change management challenges </li></ul>Risks
  27. 27. <ul><li>Legal agreements between Founders </li></ul><ul><li>Partnership with Kuali Foundation </li></ul><ul><li>Project charter approved </li></ul><ul><li>$2.5 M Mellon grant awarded </li></ul><ul><li>Project launch workshop July 30, 2007 </li></ul><ul><li>Application Architecture – in progress </li></ul><ul><li>Contributors program being finalized </li></ul>Where are we today?
  28. 28. Where are we going <ul><li>Kuali Student will: </li></ul><ul><ul><li>Support users by anticipating their needs and saving them time. </li></ul></ul><ul><ul><li>Support a wide range of learners and learning activities in a wide range of institutions by using a flexible, configurable, data model. </li></ul></ul><ul><ul><li>Support a wide range of business processes , in different institutions, using a configuration application. </li></ul></ul><ul><ul><li>Make it easy to change processes , using rules and workflow. </li></ul></ul><ul><ul><li>Use a Service Oriented Architecture , implemented using Web Services. </li></ul></ul><ul><ul><li>Achieve sustainability through community source development and wide spread adoption. </li></ul></ul>
  29. 29. Information www.kuali.org/communities/ks/