Reservation/usecases
From Dokeos
Use Cases
Use cases describe the process of an event
Contents |
Admin
Itemmanager
Add an item
Primary actor:
Admin
Preconditions:
- The admin is logged in
Post conditions:
- The item is added
Process:
1. The admin fills in the form
2. The system validates
3. The system notifies the admin that everything went successfully
Alternative ways:
2.1 The admin didn’t fill in all required fields
2.1.a The system notifies the admin that the form is empty
Edit an item
Primary actor:
Admin
Preconditions:
- The admin is logged in
Post conditions:
-The item is edited
Process:
1. The admin selects the item he wants to change
2. The system looks up the item and returns the values
3. The admin makes some changes to the values of the item
4. The system validates the changes
5. The system notifies the admin that everything went successfully
Alternative ways:
2.1 The requested item doesn’t exist
2.1.a The system notifies the admin of the problem
4.1 The admin doesn’t fill in the form correctly.
4.1.a The system notifies the admin that he made a mistake
Delete an item
Primary actor:
Admin
Preconditions:
- The admin is logged in
Post conditions:
- The item is deleted
Process:
1. The admin selects the item he wants to delete
2. The system validates and removes the item
3. The system notifies the admin that the item is removed
Alternative ways:
2.1 The item that the admin tries to remove has still active reservations
2.1.a The system asks for confirmation
2.2.a The admin confirms
2.2.b The admin denies
Reservation manager
Make a new reservation
Primary actor:
Admin
Preconditions:
- The admin is logged in
Post conditions:
-A new reservation is made
Process:
1. The admin selects a category
2. The system returns all corresponding items
3. The admin selects the item that he wants to make a new reservation for and fills in the date & time as well as some extra information
4. The system validates and adds the reservation.
Alternative ways:
1.1 The selected category doesn’t exist
1.1.a The system notifies the admin
1.1.b The admin chooses a new category
3.1.a The end date is before the start date
3.1.b The system notifies the admin
3.1.c The admin chooses a new date & time
3.2.a The start date or end date is already used
3.2.b The system notifies the admin that a part or the full period is already in use
3.2.c The admin selects a new period
Edit a reservation
Primary actor:
Admin
Preconditions:
- The admin is logged in
Post conditions:
- A reservation is edited
Process:
1. The admin selects the reservation he wants to edit
2. The system retrieves the reservation
3. The admin changes the properties of the reservation
4. The system validates and adds the reservation.
Alternative ways:
2.1 The reservation doesn’t exist
2.1.a The system notifies the admin that the reservation doesn’t exist
2.1.b The admin selects another one
3.1.a The end date is before the start date
3.1.b The system notifies the admin
3.1.c The admin chooses a new date & time
3.2.a The start date or end date is already used
3.2.b The system notifies the admin that a part or the full period is already in use
3.2.c The admin selects a new period
Delete a reservation
Primary actor:
Admin
Preconditions:
- The admin is logged in
Post conditions:
- A new reservation is edited
Process:
1. The admin selects the reservation he wants to delete
2. The system validates and removes the reservation.
Alternative ways:
2.1 The reservation doesn’t exist
2.1.a The system notifies the admin that the reservation doesn’t exist
2.1.b The admin selects the right one
2.2 There are already subscribers to the reservation.
2.2.a The system notifies the admin and asks if he wants to continue
2.2.b The admin confirms
2.3.b The admin declines
Category manager
Add a category
Primary actor:
Admin
Preconditions:
- The admin is logged in
Post conditions:
- A new category is added
Process:
1. The Admin fills in the necessary fields
2. The system validates and stores the category
3. The system notifies the user
Alternative ways:
2.1. The inputted fields are empty
2.1.a The system notifies the Admin
2.1.b The admin fills in the necessary fields
2.2 The inputted fields are not filled in correctly.
2.2.a The system notifies the admin that some fields are not filled in correctly
2.2.b The admin fills in new values.
2.3 The submitted category already exists
2.3.a The system notifies the user that the category already exists
Edit a category
Primary actor:
Admin
Preconditions:
- The admin is logged in
Post conditions:
- A category is edited
Process:
1. The admin selects a category
2. The system validates and retrieve the necessary data
3. The admin makes some changes
4. The system validates and saves the changes
Alternative ways:
2.1 Selected category doesn’t exist
2.1.a The system notifies the admin that the category does not exist
2.1.b The admin selects another category
4.1 The edited fields are not filled in correctly.
4.1.a The system notifies the admin that some fields are not filled in correctly
4.1.b The admin fills in new values.
4.2 The edited category already exists
4.2.a The system notifies the user that the category already exists
Delete a category
Primary actor:
Admin
Preconditions:
- The admin is logged in
Post conditions:
- A category is deleted
Process:
1. The admin selects a category
2. The system validates and deletes the selected category
Alternative ways:
2.1 Selected category doesn’t exist
2.1.a The system notifies the admin that the category does not exist
2.1.b The admin selects another category
User
Make a subscription
Primary actor:
User
Preconditions:
- The user is logged in
Post conditions:
- A subscription is made
Process:
1. The users selects a category, item and a reservation
2. The user fills in the necessary fields
3. The system validates and the user is subscribed.
4. The system notifies the user that his subscription is made
Alternative ways:
3.1 The end date is before the start date
3.1.b The system notifies the admin
3.1.c The user chooses a new date & time
3.2 The start date or end date is already used
3.2.b The system notifies the admin that a part or the full period is already in use
3.2.c The user selects a new period
Delete a subscription
Primary actor:
User
Preconditions:
- The user is logged in - The user is in ‘my reservation’
Post conditions:
- A subscription is deleted
Process:
1. The users selects a subscription
2. The system deletes the subscription
3. The system notifies the user
Alternative ways:
2.1 The subscription does not exist
2.2 The system notifies the user
2.3 The user selects another subscription
