Individual Project

Report Generation Process

Flight Report

Client Report

Daily

Report Process

Daily Client Report Process

Client

Report

MODULARIZATION

Below are the different modules used in the project. It contains different features a particular module support. All these modules are independently developed and are integrated later. Administrator roles are developed after all the forms are developed so that back end word can be seen easily various modules used are:

There are five modules in the systems

1. Admin_login

2. Ticket

3. Tools

4. Report

1. Admin_login

This module contains two sub modules.

Admin_login

Description: This submodule is used to logging in the project. Without Admin_login we can’t use the use the facilities of the software. The existing can using this system by entering username and password. Each user has unique Admin_login id and password provided. They can only identify with these values on Admin_login module.

Inputs: Administrator id and password and other inputs are according to the task performed.

Outputs: The form is validated and options for performing various tasks are displayed.

Validations: No required field should be left empty.

Attribute: Administrator id , Password

Exit

This option is used for exit from the system.

2. TICKET

This module contains three submodules.

2.1 Booking

Description: This submodule is used for the Booking of Flight. It contains the Ticket no., Flight Name, Flight Number, fare and all the personal detail of the client.

Input: Flight name, Required seats, Fare and Personal information of the Flight Reserver e.g. Name, Age, Address

Output: Shows options for inserting the Flight Description, Client Personal Information.

Validation: No Ticket Number, Flight Name, Required Seat, Fare and Name, Address of Client Field should left empty.

Attributes: Ticket number, Flight Name, Flight Number, Fare, Name of Client, Address.

3.2 Fligh_Cancellation

Description: This submodule is used for the Fligh_Cancellation of the booked Flight tickets. It contains the Ticket no, Flight name, journey date and the personal detail of the client.

Input: Ticket number, Journey Date, Flight Name, Clients Personal Information and Options for performing various task is displayed.

Output: Display options required for Fligh_Cancellation of a booked Ticket e.g- Ticket Number, Flight Name, Name of Clients, Address of Client.

Validations: No Ticket Number, Journey Date, Flight Name, Name of Client fields should left empty.

Attributes: Ticket Number, Flight Name, Flight Number, Fare, Name of Client, Address.

3. TOOLS

This module contains one submodule.

4.1 Add/Remove Flight

Description: This Submodule is used for Adding, New Flight, Deleting the existing Flight, modify the Details about the existing Flight etc.

Input: Flight Number, Flight Name, Destination and other Inputs are according to the task performed.

Output: This form shows options for Adding, Modifying or Delete the Flight from the list.

Validation: No Field Flight Number and Flight Name should left empty.

4. REPORT

This module contains four submodules.

4.1 Flight Status

Description: If any client wants to book a Flight, he can view the details of Flight that the Flight is available at that particular date or not. After viewing the status of Flight clients can make easy decisions about the Flight Booking.

4.2 Client Report

Description: This submodule is used for showing the Clients list that has booked their seats in the Flight.

Output: Shows the list of the clients who has booked the Flight.

Validations: Shows only the list of booked clients list.

4.3 Report

Description: This submodule is used for showing the clients list whose tickets are cancelled.

Output: Shows the list of the clients who has cancelled the Flight Booking.

Validations: Shows the list of client who cancelled the Booking.

DATA DICTIONARY

In this project we handle databases through using the concept of Relational database

First One is ADMIN_LOGIN Table: -

Field Name Storage Type Length Constraint

Username varchar 25 primary key

Password varchar 20 -

Second is BookingTable: -

Field Name Storage Type Length Constraint

Ticket_no integer 10 primary key

Journey_date date - -

From_of varchar - -

To_of varchar - -

Flight_name varchar - -

Required_seats integer 8 -

Flight_no varchar - not null

Flight_fair integer 5 -

Total_amount integer 8 -

Name varchar - -

Age integer - -

Martial_status varchar - -

Sex varchar - -

Seat_no varchar - -

Address varchar 100 -

Street_no varchar - -

City_of varchar - -

State_of varchar - -

Country_of varchar - -

Pin_of integer 10 -

Phone_no integer 10 -

Email_of varchar - -

Third is Fligh_Cancellation Table: -

Field Name Storage Type Length Constraint

Ticket_no integer 10 primary key

Journey_date date - -

From_of varchar - -

To_of varchar - -

Flight_name varchar - -

Flight_no varchar - not null

Name varchar - -

Age integer - -

Martial_status varchar - -

Sex varchar - -

Seat_no varchar - -

Address varchar 100 -

Street_no varchar - -

City_of varchar - -

State_of varchar - -

Country_of varchar - -

Pin_of integer 10 -

Phone_no integer 10 -

Email varchar - -

Fifth is Flight Entry Table: -

Field Name Storage Type Length Constraint

Flight_no varchar - not null

Flight_name varchar - -

Flight_fair integer 5 -

Destination varchar 100 -

Remarks varchar 100 -

SQL STATEMENT TO CREATE DATABASE

Create Table Admin_login

Create Table Admin_login (username varchar primary key, password varchar (20));

Create Table Booking

Create Table Booking (Ticket_no integer(10) primary key, journey_date date, from_of varchar, to_of varchar, Flight_name varchar, Required_seats integer,Flight_no varchar, Flight_fair integer(5), Total_amount integer(8), Name varchar, Age integer, Martial_status varchar, Sex varchar, Seats_no varchar, Address varchar(100), Street_no varchar, City_of varchar, State_of varchar, Country_of varchar, Pin_of integer(10), Phone_no integer(10), Email_of varchar);

Create Table Flight_Cancellation

Create Table Fligh_Cancellation (Ticket_no integer (10) primary key, journey_date date, From_of varchar, To_of varchar, Flight_name varchar, Flight_no varchar not null, Name varchar, Age integer, Martial_status varchar, Sex varchar, Seat_no varchar, Address varchar (100), Street_no varchar, City_of varchar, State_of varchar, Country_of varchar, Pin_of integer (10), Phone_no integer (10), Email varchar);

Create Table Flight Entry

Create Table Flightentry (Flight_no varchar not null, Flight_name varchar, Flight_fair integer (5), Destination varchar (100), Remarks varchar (100));

Project Plan

This project on inventory control management system will be completed within four months starting from Fri 7/15/16.The estimated fund for this project is $2,500 The phases for this project include five steps of the development life cycle which are Analysis Phase, Planning Phase, Design Phase, and Implementation Phase, testing / maintenance Phase.

Team Structure

Sampled Project Schedule or Break down Structure

Task	Due Date	Responsible Member
Software Project Management Plan	Fri 7/15/16	ALL
Software Requirements Specifications	Thu 8/25/16	ALL
Software Architecture Design Document	Fri 8/26/16	ALL
Work Breakdown Structure	Fri 9/16/16	ALL
Milestone Report	Fri 11/11/16	ALL
Software Design Document (SDD)	Tue 12/20/16	ALL
Risk Management Plan	Fri 1/27/17	ALL
Quality Assurance Plan	Tue 2/28/17	ALL
Source and Object Code	Thu 3/9/17	ALL
User Manual	Fri 4/21/17	ALL

Length of the Project