About the Project

January 1 - December 31, 2000

At the partners meeting in February 2000, partners agree to scope and guiding principles for the project.
Each partner forms a campus vision team to provide oversight for the project.
Consultants meet with each campus vision team to build awareness about electronic student services and to facilitate discussion about the possible student service(s) to be developed in the LAAP project.
Project leaders gather input from students, campus leaders, and other stakeholders on priorities and satisfaction with current services.
Campus and corporate partners identify student service module(s) to be developed in LAAP project by each partner. Kansas State University selects academic advising; Kapi'olani Community College selects tutoring; Regis University selects orientation to academic advising; SCT focuses on adding academic advising functionality to its system and development of its brokering product.
Each partner identifies own "development team" of subject matter experts in the service area and supporting technical staff.
Partners begin training in Unifiedl Modeling Language (UML) and scenario building to describe new services.

January 1 - December 31, 2001

At the second partners meeting in January 2001, partners discuss progress and make plans for year two.
Subject matter expert members of the development teams develop flow diagrams and scenarios to describe conceptual design for new services they envision.
Development teams review conceptual designs with vision teams and wider campus constituencies for consensus.
Partners' technical staffs evaluate the conceptual design for possible technical solutions and provide options with costs to project leadership.
Campus partners review costs with campus leadership and select option.
Partners identify expertise needed from consultants in development phase.
Subject matter experts begin development of the content (e.g., tutoring exercises, messages to student) to be used in the automated services.
Campus partners share scenarios and flow diagrams in the collaboratory.
Campus partners begin module development; SCT tests integrator product with selected client partners.
Webcast series begins to disseminate information on providing student services to distance learners.

January 1 - December 31, 2002

Campus partners continued development of modules.
Campus partners tested pilot modules for ADA compliance in spring.
Campus partners implemented modules for summer 2002.
Campus partners evaluated success of implementation, revise, and expand as appropriate.
At final partners meeting in November 2002, partners shared experiences and lessons learned.
Partners developed guidelines for developing services to assist other campuses.
Consultant completed case studies of partner institutions.