13
Use Cases
Sagi Dayan edited this page 2015-04-25 19:37:21 +03:00
- Table of actors and their goals
| Actors Name | Goal |
|---|---|
| Lecturer | Manage Course and communicate with students |
| Student | Follow the Course schedule and Submit tasks |
- UML Diagram
- Main formal use cases
| Senario Name | UC1. Lecturer Dashboard |
|---|---|
| Main PLayer | Lecturer |
| Goal | See all snapshops of projects in the class and certain status's. |
| Scope and Level | Lecturer client,projects data. |
| Goal | See all snapshops of projects in the class and certain status's. |
| Interested and interests | Lecturer - to get an overview of the class. |
| Description | When a lecture enters the dashboard, he has a view of individual project's and milestones.And a course Time Line. |
| Trigger | Lecturer logged in to the system. |
| Prerequisite | The Lecturer will be successfully logged in to the system. |
| Conditions of Successful Finish | Full access to updated information and data |
| Conditions of Failure Finish | Information isn't presented correctly. |
| Significant Scenario Success | 1.Lecturer logs with his Github username and password. |
| 2.Information fetched from Github login succefully. | |
| 3.The data is presented correctly on the dashboard. | |
| Extensions (Errors) | Failure to gain access by incorrect inputs. |
| Alternative Scenarios |
| Senario Name | UC2. Github-OAuth-API-Login |
|---|---|
| Main Player | |
| Goal | |
| Scope and Level | |
| Goal | |
| Interested and interests | |
| Description | |
| Trigger | |
| Prerequisite | |
| Conditions of Successful Finish | |
| Conditions of Failure Finish | |
| Significant Scenario Success | |
| Extensions (Errors) | |
| Alternative Scenarios |