Update Use Cases with content
Jonas Jødestøl Haugland
parent
cd96f9f9ec
commit
eb7b85b32f
141
Use-Cases.md
141
Use-Cases.md
@ -1 +1,140 @@
|
|||||||
Use Cases will be added once finished
|
### Use Case 1 – Create admin
|
||||||
|
|
||||||
|
| Action | Create admin |
|
||||||
|
|------------------------|----------------------------------------------------------|
|
||||||
|
| Actor | Manager |
|
||||||
|
| Pre-conditions | Logged in as manager |
|
||||||
|
| Post-conditions | A new admin is created |
|
||||||
|
| Basic path | 1. Manager clicks menu button, enters “View Admins” page |
|
||||||
|
| | 2. Manager enters “View Admins” page |
|
||||||
|
| | 3. Manager clicks “Create new admin” |
|
||||||
|
| | 4. Manager fills inn necessary information |
|
||||||
|
| | 5. Manager clicks “submit” button |
|
||||||
|
| Exception | 4.1 Manager doesn’t fill in admin name |
|
||||||
|
| | 4.2 Manager doesn’t fill in initial password |
|
||||||
|
| | 5.1 Manager doesn’t click the “submit” button |
|
||||||
|
| Additional information | The following must be entered to create an admin: |
|
||||||
|
| | - Admin name |
|
||||||
|
| | - Initial password |
|
||||||
|
|
||||||
|
### Use case 2 – Create tournament
|
||||||
|
|
||||||
|
| Action | Create tournament |
|
||||||
|
|------------------------|--------------------------------------------------------|
|
||||||
|
| Actor | Admin |
|
||||||
|
| Pre-conditions | Logged in as admin or manager |
|
||||||
|
| Post-conditions | A new tournament is created |
|
||||||
|
| Basic path | 1. Admin clicks “Create New Tournament” |
|
||||||
|
| | 2. Admin fills inn necessary information |
|
||||||
|
| | 3. Admin clicks “submit” button |
|
||||||
|
| Exception | 2.1 Admin doesn’t fill in “Tournament name” |
|
||||||
|
| | 2.2 Admin doesn’t fill in “Tournament description” |
|
||||||
|
| | 2.3 Admin doesn’t fill in start and end time |
|
||||||
|
| | 3.1 Admin doesn’t click the “submit” button |
|
||||||
|
| Additional information | The following must be entered to create a tournament: |
|
||||||
|
| | - Tournament name |
|
||||||
|
| | - Tournament description |
|
||||||
|
| | - Tournament start and end time |
|
||||||
|
|
||||||
|
### Use-case 3 – Create team
|
||||||
|
|
||||||
|
| Action | Create team |
|
||||||
|
|------------------------|-------------------------------------------------------|
|
||||||
|
| Actor | Admin |
|
||||||
|
| Pre-conditions | Logged in as an administrator |
|
||||||
|
| Post-conditions | A new team has been created |
|
||||||
|
| Basic path | 1. Admin clicks menu button, enters “View teams” page |
|
||||||
|
| | 2. Admin enters “Manage teams” page |
|
||||||
|
| | 3. Admin clicks “Create new team” |
|
||||||
|
| | 4. Admin fills inn necessary information |
|
||||||
|
| | 5. Admin clicks “submit” button |
|
||||||
|
| Exception | 4.1 Admin doesn’t fill in “Team name” |
|
||||||
|
| | 4.2 Admin doesn’t fill in any team members |
|
||||||
|
| | 5.1 Admin doesn’t click the “submit” button |
|
||||||
|
| Additional information | The following must be entered to create a team: |
|
||||||
|
| | - Team name |
|
||||||
|
| | - Team members |
|
||||||
|
|
||||||
|
### Use-case 4 – Delete admin
|
||||||
|
|
||||||
|
| Action | Delete admin |
|
||||||
|
|------------------------|-----------------------------------------------------------|
|
||||||
|
| Actor | Manager |
|
||||||
|
| Pre-conditions | Logged inn as manager |
|
||||||
|
| Post-conditions | A new admin is created |
|
||||||
|
| Basic path | 1. Manager clicks menu button, enters “View Admins” page |
|
||||||
|
| | 2. Manager enters “View Admins” page |
|
||||||
|
| | 3. Manager clicks “Remove Admin” |
|
||||||
|
| | 4. Manager selects the intended admin(s) to remove |
|
||||||
|
| | 5. Manager clicks “submit” button |
|
||||||
|
| Exception | 4.1 Manager can’t remove an admin which is also a manager |
|
||||||
|
| | 4.2 Admin no longer exists |
|
||||||
|
| | 5.1 Manager doesn’t click the “submit” button |
|
||||||
|
| Additional information | The following must be true to delete an admin |
|
||||||
|
| | - Selected admin must still exist in the database |
|
||||||
|
|
||||||
|
### Use-case 5 – Manage tournament
|
||||||
|
|
||||||
|
| Action | Manage tournament |
|
||||||
|
|------------------------|----------------------------------------------------------------------|
|
||||||
|
| Actor | Admin |
|
||||||
|
| Pre-conditions | Logged in as an administrator |
|
||||||
|
| Post-conditions | Selected tournament has been edited and saved |
|
||||||
|
| Basic path | 1. Admin clicks “Manage Tournament” |
|
||||||
|
| | 2. Admin fills inn desired information |
|
||||||
|
| | 3. Admin clicks “submit” button |
|
||||||
|
| Exception | 3.1 Admin doesn’t click the “submit” button |
|
||||||
|
| Additional information | To save the edited information at least one field must be filled out |
|
||||||
|
|
||||||
|
### Use-case 6 – Complete tournament
|
||||||
|
|
||||||
|
| Action | Complete tournament |
|
||||||
|
|------------------------|------------------------------------------------------------------------------------------------|
|
||||||
|
| Actor | Admin |
|
||||||
|
| Pre-conditions | A tournament must exist and have played matches |
|
||||||
|
| Post-conditions | The tournament is completed |
|
||||||
|
| Basic path | 1. Admin clicks “Tournament Overview” |
|
||||||
|
| | 2. Admin clicks “Complete tournament” |
|
||||||
|
| Exception | 2.1 Tournament has already been completed automatically |
|
||||||
|
| Additional information | Tournaments will be completed automatically when there is selected a winner for the last match |
|
||||||
|
|
||||||
|
### Use-case 7 – Delete tournament
|
||||||
|
|
||||||
|
| Action | Delete tournament |
|
||||||
|
|------------------------|-------------------------------------|
|
||||||
|
| Actor | Admin |
|
||||||
|
| Pre-conditions | Logged in as an administrator |
|
||||||
|
| Post-conditions | The selected tournament is deleted |
|
||||||
|
| Basic path | 1. Admin clicks “Manage Tournament” |
|
||||||
|
| | 2. Admin clicks “Delete tournament” |
|
||||||
|
| Exception | There are no active tournaments |
|
||||||
|
| Additional information | |
|
||||||
|
|
||||||
|
### Use-case 8 – Manage team
|
||||||
|
|
||||||
|
| Action | Manage team |
|
||||||
|
|------------------------|----------------------------------------------------------------------|
|
||||||
|
| Actor | Admin |
|
||||||
|
| Pre-conditions | Logged in as an administrator |
|
||||||
|
| Post-conditions | Selected team has been edited and saved |
|
||||||
|
| Basic path | 1. Admin clicks menu button, enters “View teams” page |
|
||||||
|
| | 2. Admin enters “Manage team” page |
|
||||||
|
| | 4. Admin fills inn desired information |
|
||||||
|
| | 5. Admin clicks “submit” button |
|
||||||
|
| Exception | 4.1 There are no teams created |
|
||||||
|
| | 5.1 Admin doesn’t click the “submit” button |
|
||||||
|
| Additional information | To save the edited information at least one field must be filled out |
|
||||||
|
|
||||||
|
### Use-case 9 – Delete team
|
||||||
|
|
||||||
|
| Action | Delete team |
|
||||||
|
|------------------------|-------------------------------------------------------|
|
||||||
|
| Actor | Admin |
|
||||||
|
| Pre-conditions | Logged in as an administrator |
|
||||||
|
| Post-conditions | Selected team has been deleted |
|
||||||
|
| Basic path | 1. Admin clicks menu button, enters “View teams” page |
|
||||||
|
| | 2. Admin clicks “Manage team” |
|
||||||
|
| | 3. Admin clicks “Delete team” |
|
||||||
|
| Exception | 2.1 There are no teams created |
|
||||||
|
| Additional information | |
|
||||||
|
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user