link to WICHE

WCET logo

Home

Membership
Events
Projects
Resources
Consulting
Index
Contact Us

   __________

PO Box 9752
Boulder, CO
80301
303.541.0231



  Beyond the Administrative Core: Creating Web-Based Student Services for Online Learners
link to Home link to Partners link to Resources link to Guidelines link to Webcasts link to Consulting

  ""

About the Project

link to Overview

link to Principles link to Deliverables Timeline link to Annual Reports
link to Collaboration link to Presentations and Publications link to Advisory Board link to Supporters link to 2002 Partners Meeting

Timeline

Year One
Year Two
Year Three

Year One – Assessment and Planning

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 Universal Modeling Language (UML) and scenario building to describe new services.

Year Two – Design and Development

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.

Year Three – Implementation and Evaluation

January 1 - December 31, 2002

  • Campus partners continue development of modules. 
  • Campus partners test pilot modules for ADA compliance in spring.
  • Campus partners implement modules for summer 2002.
  • Campus partners evaluate success of implementation, revise, and expand as appropriate. 
  • SCT makes integrator product available to its clients. 
  • At final partners meeting in November 2002, partners share experiences and lessons learned. 
  • Partners develop guidelines for developing services to assist other campuses. 
  • Consultant completes case studies of partner institutions.

to the top

Updated 12/10/2002

   Home | About us | Membership | Events | Projects | Resources | Consulting | WICHE