Flight management system Project in C# Sharp

Flight management system Project in C# Sharp

Functional Requirements
This section is the bulk of the document and precisely states the functions of the system
– what it should do and what it should not. This section is split into subsections
modeled after the real world activities like reserving tickets, rescheduling tickets etc.
Freedom from ambiguity and navigability were kept in mind while documentation. A
consistent terminology has been followed throughout and the terms are explained in
the appendix. The subsections follow a logical sequence that reflects the real world. For
example, a customer cannot reschedule a ticket unless he has bought one earlier and
cannot buy one unless he has checked its availability.
User Accounts

The passenger, who will henceforth be called the ‘user’, will be presented with 3
choices by the reservation system, as the first step in the interaction between
them. A user can choose one of these and his choice would be governed by
whether he is a guest or a registered user and whether he wants to check the
availability of tickets or also block/buy them.
Registration and creation of user profile
The system shall require a user to register, in order to carry out any transactions
with it except for checking the availability of tickets. It will ask the user for the
following information at the least – a user id, a password, first name, last name,
address, phone number, email address, sex, age, preferred credit card number.
The system will automatically create a ‘sky miles’ field and initialize it to zero in
the user’s profile.
Checking Availability
After logging in a user (either a registered user or a guest), the system shall
request him to enter the following details – origin city and destination city. “City’
is a generic term and refers to a city or town as the case may be. The origin and
destination cities would be entered as text.
Update Profile
The system shall enable the user to update his profile at any time. Changes
can be made in fields including but not limited to address, phone number and
preferred credit card number.
View Ticket Status
The system shall allow a user to view all information about his trip. After logging
him on, it asks for his blocking number or his confirmation number. It accesses
DB-reservation and retrieves the details of the trip and presents them to the user
in a convenient format, including any last minute changes to the flight timings
etc. Such changes will be highlighted.
Query Flight Details
The system shall allow any user (registered or non registered) to access the details
about the arrival and departure times of a flight by requesting the user to input
the flight number and date. The system accesses DB-schedule and presents the
time of arrival and departure.
Telephone access
The system shall be accessible through a touch-tone telephone. The telephonic
interface shall, at the least, provide the customer with the facility to check
availability of tickets and query flight details