Airline Booking System Phase 2: Design Document
Introduction - XYZZY Software is contracted to develop a reservation system for a very small and exclusive airline. The system is to be developed using Java Technologies (NetBeans, Java DB) and a phased implementation strategy will be adopted. This document represents the current state of the design for the Phase 2 system.
Requirements - Because of the simplicity of the functional requirements, the corresponding use cases are not duplicated here.
The purpose of the system is to assist staff in the management of reservations. In this regard, note that the airline is unusual in that it only operates two flights per day - one from Canberra to Melbourne and the other from Melbourne to Canberra. Because of the quality of the in-flight dining, business is thriving and in order to retain its exclusivity, the owners have no immediate intention of adding more flights or destinations. The reservation system is to be implemented as a Java desktop application that employs a simple Swing GUI and Java DB database. Interaction between the database and the application is to be via JDBC. The NetBeans IDE is to be used for development.
The functional requirements for the Phase 1 system were as follows:
1. Start the application and connect to the database
2. Close the database connection and stop the application
3. Display all reservations
4. Display all reservations for which the number of passengers is within a specified range
5. Display the total number of passengers who have booked for a particular flight
6. Add a reservation to the database if sufficient seating is available and the application was to conform to the MVP (Model View Presenter).
In Phase 2, the following additional functional requirements are added:
7. Clear all fields in the GUI
8. For commands that return reservation records (ie requirements 3 and 4) the records are to be browsable via previous and next buttons, as detailed in Section 5.
Furthermore, the display of browsable records is to be realised using the MVC (Model View Controller) pattern. Any output associated with requirements 5 and 6 will be initiated by the controller (using the MVP pattern) and not by the model. Refer to the class diagram of Figure 6 for clarification. Note that "presenter" functionality is provided by the ReservationsController class. Your application must conform to Figure 6, although you are free to add additional private members and methods.
The database design and sample data are provided in Section 4. Note that dates are represented (both in the database and in the application) as text strings. Data validation is not required at this stage. However, basic preconditions must be satisfied for each requirement and if these are not satisfied, an appropriate message is to be displayed. These preconditions are specified in Section 8.
Attachment:- Assignment File.rar