how to write the classes and its states and behaviours?
I will take care of the CODING myself, just want someone to help understanding how many classes I need to create in the UML. Also, how many states and behaviours in each class. If someone can help explain that, will appreciate it
A company rents out planes to private pilots. Bookings are made when a client reserves a plane for a specified date. Planes are picked up and dropped off at specified airports. This is usually done on the telephone. Planes can be booked for one (1) day only and are booked for the whole day.
The company would like to computerize their system. The company clerk will be entering information to a computer while speaking to a client on the telephone. The clerk will need to retrieve information (e.g. plane details, airport details, or client details if the clerk is dealing with an existing client) and create new bookings using the system. The clerk must be able to add, delete and update information on planes and airports. The clerk must also be able to add new clients as well as record new bookings and checking the availability of planes for specific dates.
You must come up with appropriate state (3 to 4 state values are acceptable) information for all classes involved. All collections must be shown as arrays.
Carry out an initial object-oriented design for the above specification, in which you should identify and show in a UML diagram:
• Classes that you think will be required.
• Their attributes and behaviours
• Any aggregation relationships
• Any other relationships between your classes
The UML Diagram should show all the information of the classes up to and including the coordinator class.
Start with Accounts, Planes, Airports, Bookings. Then you figure out the attributes, behaviors, and relationships
Okay so let me show you what I have got so far I'm confused with the attributes, and behaviours.
What are you confused about when it comes to attributes and behaviours?
Okay so here I'm having difficulty with what should I have in the clerk class?
I think all you need are CRUD operations on Airport, Plane, Client, and Booking which includes a function to check the plane availability for specific dates which is basically a special Read operation on Plane.
Based on the text you provided, I do not think you need a Clerk class and I wonder why you even added it in the first place.
Ah I see. Sorry I'm just a beginner, learning all this the first time
Обсуждают сегодня