Design a system for a company that sells new recreational vehicle (RV)s. The operations include:
1) The manager creates a new vehicle record in the system.
2) A salesperson creates an invoice in the system when a purchase has been agreed upon. The invoice summarizes the purchase, including full customer information, information on the trade-in vehicle (if any), the trade-in allowance, and information on the purchased vehicle. If the customer requests dealer-installed options, they are listed on the invoice as well. The invoice also summarizes the final negotiated price, plus any applicable taxes and license fees.
3) A manager can update the invoice.
4) The system manages customer information.
5) The system also manages the information of salesperson.
Use case narrative for “Create Invoice” use case
Use Case Name:
Create Invoice
Actor:
Salesperson
Description:
This use case describes the event of a salesperson creating a new invoice in the system.
Precondition(s):
The salesperson has already logged in.
The vehicle record has been created in the system.
The customer record exists in the system
Typical Course of Events:
Actor Action
System Response
Step 1: The salesperson selects the option to create a new invoice
Step 3: The salesperson enters the serial number of the vehicle
Step 6: The salesperson confirms the vehicle.
Step 8: The salesperson enters the customer ID.
Step 11: The salesperson enters invoice information
Step 2: The system responds by presenting a screen where the vehicle record may be searched.
Step 4: System searches for the vehicle
Step 5: System displays the vehicle information
Step 7: System asks for the customer ID
Step 9: System searches for the customer
Step 10: System displays the invoice form
Step 12: System saves the invoice
Alternate Courses:
(Omitted)
Post-Condition:
The invoice has been entered. Inventory has been updated.
Question 3. Develop a class diagram for the above system. Your class diagram should contain all entity, boundary and control classes. (30 points)
Question 4.Develop a sequence diagram for “create invoice” use case based on the use case narrative provided. (20 points)
Question 5. Develop a state machine diagram for an object of “invoice” class based on the system description and the following information(20 points).
