4SSA2 Version: 1.

0
Maintain Fuel Use Case Specification Issue Date: 14/May/2009
52317136.doc

1. Maintain Fuel
1.1 Brief Description
The use case starts after the customer has selected a vehicle and the system has retrieved the
vehicle fuel history(get database) on screen. The customer chooses to add, edit and delete a fuel
record.

1.2 Flow of Events

1.2.1 Basic Flow

1.2.1.1 When the customer selects the option of Add Fuel Record:

1.2.1.1.1 The system displays a blank fuel form for the customer to enter the fuel information like
date, last odometer, current odometer, gallons/litres dealer, octane…….comments etc.
See screen prototype for attributes details.

1.2.1.1.2 When the customer clicks the OK button, the system will create a new fuel log object
and load the entered data into the fuel log object, the system will then conduct the
following verification:

1.2.1.1.2.1 The system verifies the last odometer against the current odometer.

1.2.1.1.2.2 After the above verification, the user click ok button and the system will save the
new fuel record into the database.

1.2.1.2 When the customer selects the option to Edit Fuel Record:

1.2.1.2.1 The system will display the current fuel record details on screen. The customer modifies
the selected fuel information like date, last odometer, current odometer, gallons/litres
dealer, octane…….comments etc. See screen prototype for attributes details.

1.2.1.2.2 When the customer clicks the OK button, the system will modify the entered data into
the fuel object, the system will then conduct the following verification:

1.2.1.2.2.1 The system verifies the last odometer against the current odometer.

1.2.1.2.2.2 After the above verification, the user click ok button and the system will save the
current fuel record into the database.

1.2.1.3 The customer selects the option to Delete Fuel Record(s):

1.2.1.3.1 After the customer has selected one or more fuel record(s) then the user may choose to
delete the fuel record(s). The system will delete the corresponding fuel records from the
database.

Confidential Page 1
4SSA2 Version: 1.0
Maintain Fuel Use Case Specification Issue Date: 14/May/2009
52317136.doc

1.2.1.4 The system goes through the vehicle fuel records and recalculates the total fuel costs and
average fuel consumption (i.e. mpg). The system will display these fuel summaries at the bottom of the
screen.

1.2.2 Alternative Flows

1.2.2.1 Quit from the system

The user chooses to exit the system prematurely before add, edit or delete fuel transaction is
completed.

1.2.2.2 Vehicle Database Not Available

If in the Basic Flow, the database is not available, the system will display an error message
stating that the database is not available. The use case ends.

1.2.2.3 Odometer verification failed

If in the Basic Flow, the system verifies the last odometer against the current odometer. If the
last odometer is bigger than the current odometer, the system will display an error message. The
customer is expected to re-enter the data.

1.3 Special Requirements

None.

1.4 Pre-Conditions
The customer must have logged in the system and has selected a vehicle before this use case
begins. The authentication and security issues are not considered for the purpose of this
assignment.

1.5 Post-Conditions
If the use case was successful, the fuel information is saved to the system. Otherwise the state of
the system is unchanged.

1.6 Extension Points

None

Confidential Page 2