In the level 2 diagram, Booking module has been exploded and the processing is shown in more detail. The customers may make contact either through the internet or over the phone. In case of the internet they go through the available data and could possibly send an email asking for data to the marketing who in turn could pass it on to the telephone handling process. Else the customer himself might directly call up and land at the call center to get his queries answered. The marketing people handling the telephone calls are supported by data from the airline company and from the overseas staff by providing them with the villa details. Once the process is through, the marketing makes a provisional booking and passes the information to the accounts. On receipt of the payment from the customer, accounts confirms the booking.
2.2 To access any client detail, we will accessing the same using any of these numbers: 1. Client id 2. Booking number. Since most of the times we will require to use the client name and id, we will take that as an example to understand accessing of the client list table. From the client id, we can realize the exact booking operation fully. Client id relates to the client table since it is the primary key. The foreign keys there lets you know who handled the client ( staff id ), booking number relates to the bookings table telling you the date and time of the booking, his / her payment status, etc., Similarly, the entire line to other tables like the villas, the flights are all closed and we will be able to pick up all information corresponding to one client for that specific season. Ideally, if the same system spans over years, then we need to have a composite key including year along with the client id as the primary key for the client entity.
3.0 List of Requirements
The requirements are listed as business requirements, sub classified as functional and non-functional requirements.
Non Functional Requirements