Suppose you are asked to test the following Java method that converts given temperature in Fahrenheit, Kelvin or Delisle to Celsius.

1. List the minimum set of test inputs that will achieve 100% branch coverage (for each test input specify the branch(es) it covers).
2. List the minimum set of test inputs that will achieve 100% feasible path coverage (for each test input specify the path it covers).
3. Briefly discuss if the execution results of the test sets above reveal any bugs in the code.

Draw a UML sequence diagram using the class diagram above and the following use case. The specifications below describe the interaction among system objects when performing one of the system’s use cases. This use case explains a customer (company) booking a service.

Preconditions of this use case: The customer already logged-in and several objects already exist in the system. Some of these objects are: GUI (an object representing the graphical user interface of the system), company (instance of Company), manager (instance of GarageObjectManager), and garage (instance of Garage).

Note that despite the similarities, the system depicted above in Figure 1 is a different system than the one described in Question 1.

1. The customer selects the option to book service from the GUI.
2. GUI calls the company object and the company object calls the manager object to find garages with the requested service.
3. For all garages, the manager object gets provided services.
4. The manager object returns a list of garages offering the selected service and the company object passes the list to the GUI.
5. If the list is empty GUI displays no available garages.
6. Otherwise, GUI displays available garages to the customer.
7. The customer selects a garage.
8. GUI gets the available dates from the selected garage.
9. GUI gets the list of vehicles from the customer object.
10. GUI displays vehicles and available dates to the customer
11. The customer selects the date and vehicle.
12. GUI calls the company object to make booking.
13. The company object calls the manager object to create booking.
14. The manager object creates a booking with the given date, garage and vehicle.

[20 Marks]

HINTS:

• All input parameters are omitted from class methods to simplify the diagram. No need to add any parameters.
• A service can be offered by many garages.
• You can use List<ClassName> notation for your return messages where a lifeline returns of a list of objects.

Please use the names below for the actor name, guards and messages in your diagram.

Company, book service, display no available garages, display available garages, select garage, display vehicles and available dates, select date and vehicle

The requirements below partially describe a garage management system that is used for managing day to day activities of garages (of a company). The system keeps track of customers, vehicles, bookings, payments and employees. Draw a UML class diagram describing an object-oriented system using the list of requirements below.

1. The system must support two types of customers: individual and company.
2. The system must be able to store multiple contact details for each customer.
3. The system must allow customers to own multiple vehicles.
4. The system must support two types of employees: staff and mechanic.
5. Each garage has at least one employee.
6. The system must allow customers to book a service for a vehicle.
7. Each booking must be made for a single garage.
8. The system must not allow an employee to work in more than one garage.
9. The system must assign only one mechanic to each booking.
10. The system must create one bill for each booking.
11. A bill consists of at least one service and car parts.
12. The system must allow each garage to offer several services.
13. The system must be able to track payments.
14. Each payment is made to pay a bill.
15. The system must support these payment methods: card, cash and check.
16. Each payment must be made with one of the supported payment methods.
17. The system must track the staff who received the payment.

[30 Marks]

HINTS:

• No need to add any methods or attributes to your classes.
• When a customer is removed his/her contact details must also be removed.
• There will be vehicles in the system without any booking.
• There will be unpaid bills in the system, the system must represent them.
• The system must allow having bills without car parts.
• The same service can be offered in more than one garage
• A mechanic can be booked for more than one service using the system.

Please use the names below for the class names in your diagram.

Garage, Vehicle, Booking, Employee, Mechanic, Staff, Customer, Individual, Company, ContactDetail, Service, CarPart, Bill, Payment, PaymentMethod, Card, Cash, Check