(a) Draw a Collaboration diagram for the Written Use Case description of a typical Vehicle Repair and Maintenance Shop, as provided below:

Use Case Title: Auto Maintenance & Repair

Primary Actor: Customer

Level: Kite (high, general)

Stakeholders: Customer, Parts Vendor

Preconditions: Customer owns a vehicle with a problem

Minimal Guarantee: Vehicle condition will be evaluated

Success Guarantee: Vehicle will be repaired appropriately

Main success scenario:

o Customer enters shop, requests help with vehicular problem, provides personal and vehicle info

o Attendant obtains request (with the customers & vehicle information)

o Diagnose actual problem

o Determine if vehicle requires maintenance or repair

o If maintenance is required, service accordingly

o If repair is required, determine if repair involves fixing or replacing vehicle parts (determine if part needed)

o If able to fix the part, perform repair

o If a new part is required, obtain part from vendor, then repair

o Update vehicle history (Update Vehicle Maintenance log)

o Prepare (calculate) bill for the customer

o Present bill for payment

o Receive payment (cash or credit) from customer & return keys.

Extensions:

3a) Unable to diagnose problem take vehicle to another shop

8a) Part not available offer customer a courtesy vehicle

12a) Customer unable to pay retain keys of vehicle until customer returns with payment.

Hint: o Use only the Main Success scenario to draw the diagram.

o The Customer Actor interacts with the system through a ShopInterface boundary object.

o Consider Parts Vendor as an actor outside the system.

o Also, consider one Control object (e.g.:ShopControl), and two entity objects (:VehicleMaintenanceLog, containing data for all maintenance and repairs performed on the Vehicle, and :Vehicle, containing all vehicle specific data).

o Consider all calculations to be performed by the :ShopControl class on itself.

o Note that car repair involves servicing, as well as replacing parts.

(b) Convert the Collaboration Diagram you have prepared in the previous task (a) into a Class Diagram.

Hint: o Consider that all messages presented on the Sequence diagram become responsibilities of the receiver object class (i.e. they become methods of that class).

o Also, consider that each Vehicle instance of the Vehicle class has a unique identifier Vehicle Reg No, and attributes like Chasis No, Make, Model, Colour, Details and Current Owner Details.

o The unique identifier in the Vehicle Maintenance Log class is Vehicle Log Entry No, and attributes are Date, Vehicle Reg No, and Log Entry Details.