### BERT, Group 50

### Use Case UC11: Manage Vehicles

### Revision History: current version v1

### Primary Actor: BERT Administrator

#### Stakeholders and interests:

- Administrator: Wants to be able to maintain the Vehicle Booking Subsystem through viewing, adding, modifying and deleting Vehicle resources from the system.

-Employee: Wants access up-to-date and correct information when accessing the Vehicle Booking Subsystem.

-Management: Wants up-to-date and correct information about its Vehicle resources to be stored on persistent storage.

Preconditions:

1. The Administrator has been successfully logged in to the BERT Management subsystem.
2. The Administrator's access priveleges have been verified.
3. The Vehicle booking information is available for interrogation.

Success Guarantee (Post conditions):

1. Vehicle information has been viewed, added, modified or deleted from the Vehicle Booking Subsystem.

Main Success Scenario (or Basic Flow):

1. System presents the Administrator with the options to view, add, modify or delete a Vehicle.
2. Administrator chooses to View a Vehicle and submits choice to system.
3. System receives Administrators chosen function and begins execution.
   1. If "Add a Vehicle" is chosen, extension 3a is executed.
   2. If "Modify a Vehicle" is chosen, extension 3b is executed.
   3. If "Delete a Vehicle" is chosen, extension 3c is executed.
4. System retrieves all Vehicle information.
5. System presents Administrator with a view of all Vehicles registered with the System.
6. Administrator exits Use Case.

Actor repeats steps 1-3 until indicates done.

Extensions (or Alternative Flows):

3a. Administrator wants to "Add a Vehicle".

1. System requests that the Administrator enters the Vehicle information.
2. Administrator enters the Vehicle information.
3. Administrator submits the information to the system.
4. System receives new Vehicle information.
5. System stores the new Vehicle information on persistent storage.
6. System presents the Administrator with a message confirming successful update.

Actor repeates steps 2-3 until indicates done.

3b. Administrator wants to "Modify a Vehicle".

1. System presents Administrator with a view of all Vehicles currently registered with the System..
2. Administrator selects which Vehicle is to be modified and submits request to system.
3. System presents Administrator with the facility to edit current information.
4. Adminstrator enters modifications.
5. Administrator submits a request for the Vehicle information to be updated.
6. System receives updated information.
7. System stores the updated Vehicle information on persistent storage.
8. System presents the Administrator with a message confirming successful update.

Actor repeats steps 2-5 until indicates done.

3c. Administrator wants to "Delete a Vehicle".

1. System presents Administrator with a view of all Vehicles currently registered with the System.
2. Administrator selects a Vehicle to be deleted.
3. Administrator submits request for the Vehicle to be deleted.
4. System receives request.
5. System removes the Vehicle information from persistent storage.
6. System presents the Administrator with a message confirming successful update.

Actor repeates steps 2-3 until indicates done.

Special Requirements:

-

Technology and Data Variations List:

n/a

#### Frequency of Occurrence:

Occurrence on an ad-hoc basis.

#### Open Issues:

-