vrijdag 9 december 2011

Use Cases

I created 10 use cases I think would be the most significant actions in the app. By actions I mean active use cases, like email a person. Possible "passive" use cases are included in those active ones, an example is to check the schedule: the schedule is listed when you execute the use case Navigate to Class.

Advice and comments are welcome!


USE CASES:

1. Log In

Primary Actor: The user.

Precondition: None.

Basic Flow:
1. Click on application icon.
2. Enter user ID and password, then press "enter".
3. The system comfirms the successful login.


2. Read An Announcement

Primary Actor: The user.

Precondition: User is logged in.

Basic Flow:
1. The user goes to the Feed View.
2. The system presents a list of the upcoming events and the recent
announcements.
3. The user selects one of the announcements.
4. The system displays the announcement.

Alternative Flow:
1. The user goes to the Home View.
2. The system presents the Home View with icons leading to different
parts of the application.
3. The user clicks on the Announcements icon.
4. The system displays a list of all the announcements, sorted to
show the most recent first.
5. The user selects one of the announcements.
6. The system displays the announcement.


3. View Course Announcements

Primary Actor: The user.

Precondition: User is logged in.

Basic Flow:
1. The user goes to the Home View.
2. The system presents the Home View with icons leading to different
parts of the application.
3. The user clicks on the Courses icon.
4. The system displays a list of the available courses.
5. The user selects a course.
6. The system presents different options for that course followed by
a list of the announcements for that course.


4. View Course Contacts

Primary Actor: The user.

Precondition: User is logged in.

Basic Flow:
1. The user goes to the Home View.
2. The system presents the Home View with icons leading to different
parts of the application.
3. The user clicks on the Courses icon.
4. The system displays a list of the available courses.
5. The user selects a course.
6. The system presents different options for that course followed by
a list of the announcements for that course.
7. The user selects the Contact option.
8. The system presents a list of people that teach this course.


5. View Course Schedule

Primary Actor: The user.

Precondition: User is logged in.

Basic Flow:
1. The user goes to the Home View.
2. The system presents the Home View with icons leading to different
parts of the application.
3. The user clicks on the Courses icon.
4. The system displays a list of the available courses.
5. The user selects a course.
6. The system presents different options for that course followed by
a list of the announcements for that course.
7. The user selects the Schedule option.
8. The system presents a list of all the class moments for that
course.


6. Email Person

Primary Actor: The user.

Precondition: User is logged in.

Basic Flow:
1. The user goes to the Home View.
2. The system presents the Home View with icons leading to different
parts of the application.
3. The user clicks on the Contact icon.
4. The system lists all the available contacts. *
5. The user types a part of the name of the target person.
6. The user selects the person.
7. The system shows the Person View of that person, including photo,
email address, office location, ...
8. The user clicks on the email address link.
9. The system will then, if present, open the native email app and
add the contact to the recepients.
10.The user writes his message and sends it.

(* available contacts include contacts from courses, departement heads,

possibly personnal study friends, ...)


7. Navigate to Person

Primary Actor: The user.

Precondition: User is logged in.

Basic Flow:
1. The user goes to the Home View.
2. The system presents the Home View with icons leading to different
parts of the application.
3. The user clicks on the Contact icon.
4. The system lists all the available contacts.
5. The user types a part of the name of the target person.
6. The user selects the person.
7. The system shows the Person View of that person, including photo,
email address, office location, ...
8. The user clicks on the office location link.
9. The system lists 2 options: "Show on map" and "Navigate".
10.The user selects the first option: "Show on map".
11.The system displays the Campus Map View, focused on the target
building.

Alternative Flow:
10.The user selects the second option: "Navigate".
11.The systems opens, if present, the native navigation app and gives
the target location geo coordinates as argument to it.


8. Navigate to Exam

Primary Actor: The user.

Precondition: User is logged in.

Basic Flow:
1. The user goes to the Home View.
2. The system presents the Home View with icons leading to different
parts of the application.
3. The user clicks on the Exams icon.
4. The system lists the exams of the upcoming exam period.
5. The user selects an exam.
6. The system shows the Exam View, including a link to the course,
the date and time of the exam, the location, ...
7. The user clicks on the location link.
8. The system lists 2 options: "Show on map" and "Navigate".
9 .The user selects the first option: "Show on map".
10.The system displays the Campus Map View, focused on the target
building.

Alternative Flow:
9 .The user selects the second option: "Navigate".
10.The systems opens, if present, the native navigation app and gives
the target location geo coordinates as argument to it.


9. Navigate to Class

Primary Actor: The user.

Precondition: User is logged in.

Basic Flow:
1. The user goes to the Feed View.
2. The system presents a list of the upcoming events and the recent
announcements. Every event has a date+time and a location link.
3. The user clicks on the location link of one of the class moments.
4. The system lists 2 options: "Show on map" and "Navigate".
5 .The user selects the first option: "Show on map".
6 .The system displays the Campus Map View, focused on the target
building.

Alternative Flow:
1. The user goes to the Home View.
2. The system presents the Home View with icons leading to different
parts of the application.
3. The user clicks on the Schedule icon.
4. The system displays a list of all the upcoming class moments.
Every class moment has a date+time and a location link.
5. The user clicks on the location link of one of the class moments.
6. The system lists 2 options: "Show on map" and "Navigate".
7 .The user selects the first option: "Show on map".
8 .The system displays the Campus Map View, focused on the target
building.

Alternative Flow:
7 .The user selects the second option: "Navigate".
8 .The systems opens, if present, the native navigation app and gives
the target location geo coordinates as argument to it.


10. Find Building

Primary Actor: The user.

Precondition: User is logged in.

Basic Flow:
1. The user goes to the Home View.
2. The system presents the Home View with icons leading to different
parts of the application.
3. The user clicks on the Campus Map icon.
4. The system displays the Campus Map View.
5. The user types the name of the building.
6. The system lists the results of a search for that name.
7. The user chooses one of the results.
8. The systems focuses the Campus Map View on the target building.

2 opmerkingen:

  1. I was wondering if these use cases are based on the results of your survey?

    BeantwoordenVerwijderen
  2. You provide an option to see your schedule as a list of events; maybe it is more useful to show the events on a timeline (like the schedule on the current Blackboard system)?

    BeantwoordenVerwijderen