The net-based travel agent ‘TA’ needs a new system for handling reservations. TA makes ordinary flight reservations, ordinary train reservations, plus reservations for package tours (by airplane only). No further kinds of reservations are considered here. What is required is a system wherein reservations can be recorded according to their data (e.g. source, destination, relevant dates and points of time, prices,…). It must be possible to handle reservations in various rather obvious ways, e.g. to create or update their data, cancel them, print them, delete them and so on. Moreover, it should be possible to derive an itinerary for the travel in question (from the corresponding reservation).
The reservation process is taken to start with an enquiry (a search undertaken in TA’s system) by a customer. In the case of a regular (non-charter) reservation, we could imagine that the customer typically states the destination of his/her travel, plus a point of departure. Moreover, the desired dates of departure and return will be required.
The system of TA then proceeds to collect information about the various possibilities. We shall assume that the collection of information from various train lines, flight operators etc. is based on an already existing system, which is a separate entity and not to be confused with the reservation system (a system interacting with other actors’ systems such as dsb, SAS, etc. etc.). One or more tentative reservations, and corresponding prices, can be suggested to the customer. The customer can then make a choice among these proposals and a final full reservation is created and stored in a register, from where it can also be deleted when the travel is completed or cancelled.
Develop a UML-model of the domain, using Modelio to produce an appropriate class diagram. The minimum demand is a class diagram representing the reservation system, including operations allowing for obvious interactions such as enquiries, creation, updates and cancellations of reservations. Your model should also take the production of itineraries (based on reservations) into consideration. Together with the class diagram, you must submit a short report containing reflections on the domain and how you have chosen to interpret and model it. This includes describing basic assumptions that you have made (see 'Formal requirements' below).
Some possible extensions to your system would be taking payment into more detailed consideration (when, in the form of installments or once-and-for-all, security deposits, etc.). Well-known “additionals” such as accommodation (which is perhaps not so additional when looking at Package tours) and other well-known features of searching for and booking travels can also be added to refine your model. You may also reflect on the very activity of UML-classification/-modeling – for instance the advantages and limitations of this structured approach to classification.
However these possible extensions are not demanded, but meant as suggestions for voluntary refinement of you submission.
Your submission must include:
DescriptionIn this final assignment, the students will demonstrate their ability to apply two ma
Path finding involves finding a path from A to B. Typically we want the path to have certain properties,such as being the shortest or to avoid going t
Develop a program to emulate a purchase transaction at a retail store. Thisprogram will have two classes, a LineItem class and a Transaction class. Th
1 Project 1 Introduction - the SeaPort Project series For this set of projects for the course, we wish to simulate some of the aspects of a number of
1 Project 2 Introduction - the SeaPort Project series For this set of projects for the course, we wish to simulate some of the aspects of a number of