Hi all, I have an assignment due for programing (again) and I have done very little work on UML Diagrams, My first 2 tasks are:
1) A UML use-case diagram for the system, including all important actors
who will use the system. You should also include a short commentary
on this diagram, describing the process that you used to develop the
diagram. [17%]
2) A UML class diagram, including appropriate methods and attributes
for each class in the system. Again, a commentary on your design
process should be handed in too. [16%]
The problem I have is this:
Would this Use case diagram for the problem be correct?
“A customer rents a vehicle”. This is related to both the customer, who wishes to rent, and the employee who must arrange the rental. The employee will perform a “check on the customers rental history” to see if he or she is will be loaned a vehicle, this action extends the “Rent vehicle” use case.
Once it has been decided that the customer will rent a vehicle, the action of renting the vehicle includes two actions,” invoicing the customer” for the cost of the rental (getting payment) and making sure they have what the “stock” the customer wants.
The customer also needs to “return the vehicle”, the employee again deals with this, the process of returning the vehicle included “checking how long the vehicle was out” and “issuing any extra costs” resulting in extended rentals, this will also be added to the “customers records”.
The employee will update all of the “customers records”, with details such as current rentals, reliability, return times etc. Finally the shop (or boss) will deal with hiring, and firing of staff, meaning they relate to the employee, they will also have a copy of the customer records, and be responsible for preparing the customer invoices.
1) A UML use-case diagram for the system, including all important actors
who will use the system. You should also include a short commentary
on this diagram, describing the process that you used to develop the
diagram. [17%]
2) A UML class diagram, including appropriate methods and attributes
for each class in the system. Again, a commentary on your design
process should be handed in too. [16%]
The problem I have is this:
Code:
Fitzroy Bailey, the owner of Rockall Vehicle Rental Agency, wishes to set up
a stock-control system to manage hiring, invoicing, and customer records.
Bailey should be able to determine how many vehicles are on hire at a given
moment, and what the rental income to date is. The shop hires bicycles by
the half-day, cars by the week (with an additional charge if a car is used
for more than an average of 1,000 miles/week), and helicopters by the hour.
When a customer hires a vehicle, an employee must record their name and
address, and ensure that the hiring information is recorded, including the
length of time for which the vehicle has been hired. Everyone who hires a
vehicle must pay for it at the time of hiring.
Would this Use case diagram for the problem be correct?
“A customer rents a vehicle”. This is related to both the customer, who wishes to rent, and the employee who must arrange the rental. The employee will perform a “check on the customers rental history” to see if he or she is will be loaned a vehicle, this action extends the “Rent vehicle” use case.
Once it has been decided that the customer will rent a vehicle, the action of renting the vehicle includes two actions,” invoicing the customer” for the cost of the rental (getting payment) and making sure they have what the “stock” the customer wants.
The customer also needs to “return the vehicle”, the employee again deals with this, the process of returning the vehicle included “checking how long the vehicle was out” and “issuing any extra costs” resulting in extended rentals, this will also be added to the “customers records”.
The employee will update all of the “customers records”, with details such as current rentals, reliability, return times etc. Finally the shop (or boss) will deal with hiring, and firing of staff, meaning they relate to the employee, they will also have a copy of the customer records, and be responsible for preparing the customer invoices.
Last edited: