Design and Implementation of a Computerised Airplane Passenger Manifest Information (A Case Study of Sosoliso Airways)

31 PAGES (2445 WORDS) Computer Science Project
INTRODUCTION
This passenger manifest information (PMI) is a kind of records that help individual flight to organized their passenger in a flight. This record in the flight. This record help them to know the members of passenger in the flight, without their records they can known the numbers of passenger in the flight. So the passenger manifest information contained the:
(1)Full name
(2)Date of birth
(3)Social security number
(4)Emergency contact
(5)Telephone number
From passenger traveling on flight with sosoliso airline (e.g., during the sosoliso airline disaster family assistance act of December 10th 2005. this law was passed to address the difficult associated with notification of the families in the aftermath of sosoliso airline crashes). This proposal is also being issued to fulfill a recommendation contained in the initial and final report of families that has be affect in the crashes. This passenger manifest information (PMI), is used to point out identify data elements  that may point to a passenger who represents a security risk. Once highlighted, analytical specialists can them manually review these records and identify those  passengers who should be subjected to additional screening upon their arrival.

TABLE OF CONTENT
COVER PAGE
TITLE PAGE
APPROVAL PAGE
DEDICATION 
ACKNOWLEDGEMENT
TABLE OF CONTENT
CHAPTER ONE
1.0 INTRODUCTION
1.1  OVERVIEW OF THE EXISTING SYSTEM
DESCRIPTION AND ANALYSIS OF THE EXISTING SYSTEM
METHOD OF DATA COLLECTION
SOURCE OF DATA
INTERVIEW METHOD
1.2.2 REFERENCE TO WRITING TEXT
1.3 INPUT ANALYSIS
1.4 PROCESS ANALYSIS
1.5 OUTPUT ANALYSIS
1.6 PROBLEMS OF THE EXISTING SYSTEM
1.7 JUSTIFICATION OF THE NEW SYSTEM

CHAPTER TWO
2.0 DESIGN OF THE NEW SYSTEM
2.1 OUTPUT SPECIFICATION AND DESIGN
2.2 INPUT SPECIFICATION
2.3 FILE DESIGN
2.4 PROCEDURE CHART
2.5 SYSTEM FLOW CHART
2.6 SYSTEM REQUIREMENTS

CHAPTER THREE
3.0 IMPLEMENTATION
3.1 PROGRAM DESIGN
3.2 PROGRAM FLOW CHART
3.3 PSEUDO CODE

CHAPTER FOUR
4.0 DOCUMENTATION
4.1 OPERATIONAL GUIDE
4.2 SOURCE CODE LISTING

CHAPTER FIVE
5.0 RECOMMENDATION AND CONCLUSIONS
CONCLUSION

REFERENCE