Back to contents

Use cases

Use Case Scenarios

• USE CASE I) Add/Edit/Delete Resource
  • Main Success Scenario
    1. User requests to add a resource (room, instructor, or course)
    2. CMS prompts for appropriate information.
    3. User enters the information.
    4. User confirms the entry.
    5. CMS creates the resource and adds it to the database.
  • Extentions
    • 0a: User loads previously saved information about resources.
    • 1b: Resource is a room.
    • 1c: Resource is an instructor.
    • 1d: Resource is a course.
    • 1e: User selects an existing resource to edit.
      • 2e: CMS retrieves the resource and presents it to user to edit.
    • 3ea: User requests to delete the selected resource.
      • 4ea: CMS deletes the resource from the database. (Stop here.)
• USE CASE II) Add/Edit/Delete Course Offering
  • Main Success Scenario
    1. User requests to add a course offering.
    2. CMS presents a list each of courses, rooms, instructors, and time slots.
    3. User selects one of each, from lists incrementally filtered based on availability of resources.
    4. CMS adds course offering to database.
  • Extensions
    • 1a: User selects an existing course offering to edit.
      • 2a: CMS presents current state of course offering, using lists as in main success scenario.
      • 4a: CMS updates course offering in database.
    • 3aa: User requests to delete the selected resource.
      • 4aa: CMS deletes the resource from the database.
• USE CASE III) Display Schedule
  • Main Success Scenario
    1. User requests the schedule displayed in a tabular format.
    2. CMS displays schedule to user, possibly filtered with respect to rooms, courses, or instructors.
• USE CASE IV) Save Environment
  • Main Success Scenario
    1. User asks CMS to save environment (rooms, instructors, and courses).
    2. CMS saves the environment.
• USE CASE V) Save Course Schedule
  • Main Success Scenario
    1. User asks CMS to save course offerings.
    2. CMS saves course offerings.

Note: the rationale for maintaining the environment and course offerings in separate files is to make it easy to develop a schedule for each quarter while keeping the same database of rooms, instructors, and courses, which is expected to change little compared to the course offerings.

Use Case Diagram

Last updated: Sun May 18, 2003