Use cases

From MWCSWiki

Contents 1 Halloween 2 Mid-November 3 December 4 March (for targeting a March 9 beta testing period) 5 early April (for final product) 6 Post-sunset

Halloween

(Nothing is persistent)

1. Show (the one) schedule
2. Move class
   1. Add class to schedule
      1. Add a specific class from the classes box (this eventually will need to have super smarts, so that it can tell which requirements have been satisfied as a result of adding that class. But for Halloween, we'll do that last, if at all.)
      2. Add a requirement from the requirements box
   2. Move class between semesters

Mid-November

(Everything is persistent) (My prediction: Jesse moves into domain, Roger concentrates on persistence)

1. Move Class (note: this includes updating the requirements box when things are added to schedule)
   1. Add class to schedule
   2. Remove class from schedule

December

1. Log In
2. Log Out
3. Save Schedule
4. Add Year
5. Change Major
6. Select Student

March (for targeting a March 9 beta testing period)

1. Definitely for March 2
   1. "Search for courses" dialog (in place of "all courses" list)
   2. Prereqs
   3. Change # of Credits for a var-credit course
   4. Choose major
   5. Deal with WI & SI courses (backend complete; frontend support in progress)
      1. Have some way of visually annotating a course on the display with WI/SI
      2. Counter that shows # of WIs and # of SIs
   6. A way for students to register and select their advisor (and make it so advisors can access their advisees' schedules)
2. Definitely for March 9
   1. Add more data (Gen Eds, CPSC, CIS, MATH, PSYC, SPAN, FREN majors) (test that this appears)
   2. Some way to include transfer/AP credit on the schedule
   3. Compute total number of credits
   4. Advisor interface (choose from advisees to see/modify their schedule) (in progress)
3. Hopefully for March 9
   1. An integrated comment/feedback system (??)
   2. Some way to specify that a requirement has been met through other means (e.g., testing out of Spanish)
   3. Need to enter the list of all "standard" WI/SI courses from Web pages
   4. Integrate with LDAP to get userids/passwords

early April (for final product)

1. Set Availability
2. Compute # of credits per semester, and flag overloads/underloads
3. Add/Edit Note
4. Dept. chair interface (to set expected course availability)
5. Compute GPA

Post-sunset

1. Multiple schedules per student

With the exception of Select Student (Advisor) and Set Availability (Department rep), the actor in each use case is a Student/Advisor.