You are developing software for different independent Bike Rental Outlets. Your team has already completed a use case diagram together with potential clients.

The following mock-up illustrates the interface of the rental outlet:

Only some outlets offer to sell bikes, all other don’t need the use cases of the package “bike sale”. That's why EstimateMarketValue is implemented as am extension use-case.

Use Case Diagram for Bike Rental Outlet

1. USER fills the fields “type of bike”, “desired no. of bikes” to filter the bikes
2. SYSTEM shows a list of available bikes
3. USER selects one bike from the list
4. SYSTEM shows bike’s details, photo and where it can be picked up

ACTORS: USER

1. INCLUDE: SelectABike
2. USER presses “Reserve”
3. SYSTEM creates a reservation

ACTORS: USER

1. USER selects “My reservations” page
2. SYSTEM shows a list of reservations
3. USER selects one reservation from the list
4. SYSTEM shows reservation’s details
5. USER presses “Cancel”
6. SYSTEM deletes the reservation

ACTORS: USER

1. COUNTER STAFF selects “New Rental”
2. SYSTEM shows the “Enter details of rental” page
3. COUNTER STAFF introduces the details of the new rental or selects the details from a previously made reservation
4. COUNTER STAFF presses “Rent”
5. SYSTEM creates the rental record, marks the bikes as rented and it marks the reservation as completed, if necessary

ACTORS: COUNTER STAFF

1. COUNTER STAFF selects the “Rental” page
2. COUNTER STAFF completes the rental no.
3. SYSTEM shows the rental details page
4. COUNTER STAFF selects “Complete rental” button
5. SYSTEM marks the rental as complete and marks the bikes as being free

ACTORS: COUNTER STAFF

1. MECHANIC logs into the system.
2. SYSTEM displays a Bike Inventory form showing all bikes which are currently not rented
3. MECHANIC selects a bike
4. SYSTEM marks the bike as under maintenance

ACTORS: MECHANIC

1. MECHANIC logs into the SYSTEM
2. SYSTEM displays a Bike Inventory form showing all bikes which are currently not rented
3. MECHANIC selects the maintained bike
4. SYSTEM shows record of expenses for maintenance and repairs
5. THE MECHANIC enters all the required information.
6. SYSTEM updates bike record and marks it as available
7. EP: FINISHED_MAINTENANCE
8. MECHANIC presses “End Maintenance”.

ACTORS: MECHANIC

1. COUNTER staff logs into the SYSTEM.
2. COUNTER STAFF selects the desired bike in the “Bike inventory form” (used for selling purposes now).
3. COUNTER STAFF has a look on the last maintenance for that bike.
4. COUNTER STAFF chooses to sell the bike.
5. SYSTEM shows the “Enter details of selling” page
6. COUNTER STAFF enters information regarding the client and possible additional information.
7. COUNTER STAFF presses “Confirm Sell Bike”
8. SYSTEM automatically completes the selling details and updates the database table regarding the further sell availability of that specific bike type.

ACTORS: COUNTER STAFF

IF the shop sells bikes
AFTER FINISHED_MAINTENANCE

1. MECHANIC inserts in the provided box the market value after maintenance
2. SYSTEM updates and saves the information accordingly.

ACTORS: MECHANIC