1. 310313 REQUIREMENTS CAPTURE 1 ASU Course Registration System User Interface Specifification UI Elements Register for courses Use Case

2. 310313 REQUIREMENTS CAPTURE 2 ASU: REGISTER FOR COURSES UI ELEMENTS To register for a course, a student actor needs to supply the following information: –semester –year –course code –offering id –priority (i.e., primary or alternate choice) To find these UI elements, we consider the Register for courses use case and determine what information passes between the user and the system when performing the use case.

3. 310313 REQUIREMENTS CAPTURE 3 ASU Course Registration System User Interface Specification UI Layout Register for courses Use Case

4. 310313 REQUIREMENTS CAPTURE 4 ASU UI SPECIFICATION: UI LAYOUT — OPTION I Register for Courses CancelRegisterDone Year: 2007 t Semester: Spring t Alternate?: Yes No Course offering: t Course code: t Course title:

5. 310313 REQUIREMENTS CAPTURE 5 ASU UI SPECIFICATION: UI LAYOUT — OPTION I Consider the first option for the UI layout. The semester and year default to the current semester and year, which is the most likely case and so the student will not have to change these values in most cases, but can use the drop-down lists if necessary. For each course, the student needs to select the course code and course offering from the drop-down lists (the course title is retrieved by the system and displayed to the student) and indicate whether it is a primary or alternate course selection using the radio buttons (with the default being a primary course selection). The student keeps selecting courses and clicking the “Register” button until the last course has been selected, after which the “Done” button is clicked. The good aspect of this design is that it minimizes “keystrokes”; since only selection is required, the user cannot enter incorrect data. Problem: In how many primary and alternate courses has the student registered?. The interface does not show this information; the student needs to remember it!

6. 310313 REQUIREMENTS CAPTURE 6 SPECIFICATION: UI LAYOUT — OPTION II Register for Courses CancelDone Year: 2007 t Semester: Spring t Course code:Course title:Course offering: t t t t t t t t Alternate choices: Course code:Course title:Course offering: t t t t

7. 310313 REQUIREMENTS CAPTURE 7 ASU UI SPECIFICATION: UI LAYOUT — OPTION II Consider the second option for the UI layout. Selection of semester, year, course and course offering is similar to the previous interface. However, in this interface, it is clear that there are four primary and two alternate selections possible. Furthermore, the system can easily display the courses in which the student is already registered in the interface. Which design has better usability? Note that these designs were done using only PowerPoint. No implementation was needed!

8. 310313 REQUIREMENTS CAPTURE 8 ASU Course Registration System User Interface Specification Dialog Description Scenario of Creating a Student’s Schedule

9. 310313 REQUIREMENTS CAPTURE 9 ASU UI SPECIFICATION: DIALOG DESCRIPTION 1. The system displays the Register for Courses form with the current semester and year as the default. 2. If necessary, the user selects a semester and year. 3. For each primary course the user wishes to select 3.1. The user selects a primary course code. 3.2. The system displays the course title. 3.3. The user selects a course offering. 4. For each alternate course the user wishes to select 4.1. The user selects an alternate course code. 4.2. The system displays the course title. 4.3. The user selects a course offering. 5. The user clicks the Done button. 6. The system displays the status of the course registration (succeeded/failed). Much of this information can be found in the flow of events for a use case.