Airline System - Repost - open to bidding

A small airline has fleet of passenger aircraft which is identified by a unique registration number consisting of 3 letters and 3 digits, i.e. XXX999. An aircraft has a maximum seating capacity and may be in one of two states: either assigned to a flight or available for assignment. Each flight has a unique identifier consisting of the letters BN followed three digits. A flight also has a unique identifier consisting of origin and destination. Employees of Airline are classed as either flight deck crew or cabin crew. The airline records the name of each employee and assigns to each one a unique employee number consisting of five digits. For each crew member the airline also records their total flying hours and the number of hours flown since their last rest period. When an aircraft is assigned to a flight it is also assigned a crew consisting of two flight deck crew and three cabin crew. When an aircraft completes a flight the number of flying hours of each member of the crew is updated. The crew is then no longer assigned to that craft. ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Installation package that will install the software (in ready-to-run condition) on the platform(s) specified in this bid request. 3) Complete ownership and distribution copyrights to all work purchased. Task The task is to design and implement a prototype system that enables the airline to keep track of its fleet of aircraft and aircrew. Your system should provide the following functionality. Your system should allow the company to: • Add or remove employee from its list of employees. • Add or remove aircraft from its fleet. • Add or remove flights • Allocate an aircraft to a flight. • Allocate aircrew to an aircraft. • Update the flying hours of crew member • Modify the status of crew member • Modify the status of an aircraft. • Given their employee number, provide a report on the employee; showing whether they are resting, available for assignment, or assigned to an aircraft; as well as the number of hours flown since taking a rest and their total flying hours. • Given its registration number, provide a report on an aircraft; showing whether or not it is assigned to a flight, if so and its currently assigned crew. Access to the facilities of your system should be via text based menus that appear on the terminal screen. All input being via the keyboard. Documentation Supply the following documentation. Design Class diagrams and class association diagrams, which represents the static structure of your system Sequence or collaboration diagrams showing the functionality provided by your system. The use of UML to describe the classes contained in the above scenario, along with their attributes, operations and relationships. The design should also include interaction or sequence diagrams to illustrate the functionality of the system. Source Code You should provide a complete set of source code listings, for all of the classes of the classes in your system. This system should be output directly from JGrasp and should not be word processed. Evidence of system functionality You should provide script files as original evidence of the functionality that your system provides. A script file containing demonstration and test results should be produced. Indicate in your test plan what data you have used to produce these results along with comments that relate the actual results to those expected. Demonstrate all of the functionality of the system. A narrative that helps to explain the design and implementation and which comments upon the results of any tests. Also state any assumptions made. ## Platform Windows NT,