Consider a fuel station automation software is required. The automation system will keep track

of fuel tanks, personnel, pumps, customers, sales and will prepare appropriate reports. The

following data are necessary to be kept by the system.

TANKS : TankNumber, Fuel Type, Capacity, Current Level

PERSONNEL : ID$,$ Name, Blood Type

CUSTOMER : ID$,$ Name, Address

PUMPS : Pump Number, Serial Number, Connected Tank

SALES : ID$,$ Sales Date and Time, Amount, Personnel ID$,$ Customer ID$,$ Pump Number

The following system functions are also requested:

$-$ CRUD $($Create$-$Read$-$Delete$-$Update$)$ opeations for all type of information

$-$ After each sale, a $$sales receipt$$ must be printed

$-$ Each sale is initiated by the identification of the personnel by a special hardware $($smart card,

touch button etc.$)$

$-$ Registered customers should present their identity by means of a special hardware before the

refill

$-$ System should allow fuel sales for unregistered customers

$-$ Manager of the station requires a daily sales report in the end of shifts

$-$ Only the manager can set the new prices in the pump machine $($by means of the automation

system$)$

a$)[15$ points$]$ Draw UML Use Case Diagrams.

b$)[20$ points$]$ Draw UML Class Diagrams $($attributes$,$ methods, and relationships$).$

c$)[15$ points$]$ Draw UML Sequence Diagram for $$sale$$