Project ：Airways Information System
Overall description:
Your team is employed by an Airways company for the implementation and delivery of a computer system responsible for a large part of the operation of the company.
Customer specifications:
The system must be able to store the planes, flights and passengers of the company during the years of its operation. There are two types of planes P62 & P124 with rectangular arrangements of 6´2 & 12´4 seats, respectively. The sources and destinations of the currently available flights of the company (for simplicity, assume only direct flights) are allocated from a set of city airports which can be potentially extended. The different passengers can be allocated to specific flights and seats.
The system should be able to provide functionality to the different users listed below:
· A database administrator who can include new flights, prices, dates, airports and perhaps new planes for each of the two available types.
· A ticket agent who can flexibly search for a specific flight inquired by a customer. When the customer reserves or books a ticket, then the required details must be stored. Such information includes flight id, payment details, expiration date of reservation, route, allocated seat, viewing facilities of the seating plan, etc. Facilities to amend this information must be provided.
· A manager who can retrieve statistics about the company’s operation, such as the number of planes for each type, total passengers per flight, total revenue, etc.
题目要求
Final deliverables:
- Complete program source code (a set of *.c and *.h files).
- Design document, describing the different components of your developed system (a single MS‑Word or PDF file).
- A simple program manual, describing its basic functionality (a single MS‑Word or PDF file).
- Report of known bugs and functionality status (a single MS‑Word or PDF file).
- Breakdown of the roles and responsibilities of each group member during the duration of the project (a single MS‑Word or PDF file).
方案建议
The project descriptions are deliberately given in a form of simple customer specifications, which (as in the real world) are incomplete and often ambiguous, rather than a set of exact functional specifications. The group members should work methodically together (as the developers in a real world software project) to:
- Analyse and formalise the customer specifications (at this stage, the various design choices and the software features can be subject to the group’s creativity).
- Design and decompose the functional and programmatic aspects of the problem and allocate constituent tasks to each group member.
- Implement the product with frequent meetings to report progress and decisions to each other and re-evaluate the agreed courses of action.
- Implement test procedures, debug and correct the product.
- Finalise the deliverables.
The given specifications are only basic and most of the design choices should be decided in the group meetings. The systems described within the different projects have a variety of different features and the disambiguation of the customer specifications can be based to the student’s logic and real life experience. Assessment will be based on whether the product offers reasonable functionality and features (for the group size, allocated time and project difficulty), its design quality, flexibility, software bugs, and other stated deliverables. The group does not have to implement all the system features mentioned if it is not possible; it is better to have a few features fully working without run-time crashes, than all features with many bugs without working properly or causing disrupting ripple-effects to other subsystems. Prioritisation for the implementation of the different parts of the system is the group’s decision, however, for the purposes of demonstration and testing, those parts that manage and populate the filestores with data such as customers details, for instance, are necessary. In any case, any related decisions and compromises should be included in the report. The required testing procedures should simply take into account the input of each subsystem and what the output or operation of the software is supposed to do.