(ANJALI) Dange Chowk Call Girls Just Call 7001035870 [ Cash on Delivery ] Pun...
Airline information system
1. Benha University
Faculty of Engineering, Shoubra
Computer Systems Department
Travelians System
Team Members
1-Iman Sabry
2-AmiraGamal
3-Rehabnagib
4-Nourhan Mahmoud
5-EsraaMohammed
6-nadin Abdallah
7-Maria Ayman
SupervisedBy:
3. Information Systems Documentation Template
3
Acknowledgments:
First of all, we would like to express our gratitude and appreciation for our supervisor,
Dr.AbdElwahab Elsammak.for his professional guidance and insightful advices.Also we must all
thank our . instructor Eng.mofida forher continuous assistance and support.
Special thanks for Mr. from for his great help and support during the system requirement
determination process of the analysis/ Design/ Programming phase of the project.
Faculty of Engineering, Shoubra
2019
1-Iman Sabry
2-AmiraGamal
3-Rehab nagib
4-NourhanMahmoud
5-Esraa Mohammed
6-nadinAbdallah
7-MariaAyman
4. Information Systems Documentation Template
4
Contents
Acknowledgement I
Contents II
Abstract III
Project Plan IIII
CHAPTER 1 SYSTEM REQUIREMENTS
1.1 System Scope
1.2 Business Objectives
1.3 Facts Finding
1.3.1 Interviews
1.3.2 Problems of the Current System
1.3.3 Forms & Reports of the Current System
1.4 Development Process
CHAPTER 2 SYSTEM ANALYSIS
2.1 Used Methodology
2.2 Analysis Models
2.3 Processes Logic
CHAPTER 3 SYSTEM DESIGN
3.1 System Database Design
3.1.1 ER Diagram
3.1.2 Tables Design
3.2 User Interface Design
3.2.1 Summary of Screens (Pages)
3.2.2 Forms (Pages) Design
3.2.3 Reports Design
CHAPTER 4 SYSTEM IMPLEMENTATION
4.1 Used Technologies
4.1.1 Database
4.1.2 Programming
4.1.3 Reporting
4.2 System Implementation Plan
4.2.1 Administration
4.2.2 Basic System Data
4.2.3 Transactions
4.3 System Messages
5. Information Systems Documentation Template
5
CHAPTER 5 SYSTEM TESTING
5.1 Testing Check List
5.2 Test Cases
CHAPTER 6 FUTURE WORK & CONCLUSION
APPENDIX A Source Code Listing
APPENDIX B INSTALLATION GUIDE
APPENDIX C USER MANUAL
8. Information Systems Documentation Template
8
CHAPTER 1
SYSTEM REQUIREMENTS
1.1 SYSTEM SCOPE:
Our System Deals With Airports , Once a client want to see a flight he will
registerto the system then will see which date is available to book a ticket to this
flight and the cost of all flights , firstly a client will choose from these available flights
which he want then choose the number of passenger, at this momentthe system
will show the total costof all passengerwhich he selected ,if one of clients want to
canceled it’s flight will confirm it by the system or call us
9. Information Systems Documentation Template
9
1.2 BUSINESS OBJECTIVES:
Our project covers a wide scope designed to implementcomputerized system
for the following Requirements:
1. Functional Requirements
1-registration
2-choosing flight line
3-show the available flights date
4-choosing type of flight
5-show the costof this flight
6-booking
6-puching cost (online ore offline)
7-cancelling flight
8-show policity of cancelling
9-confirm cancelling
2. Nonfunctional Requirements
10. Information Systems Documentation Template
10
1.3 FACTS FINDING
1.3.1 Interviews
Interview Agenda
Date : Time:
Place:
Participants:
Name Job
1.
2.
3.
Objectives:
-
-
-
-
-
Documents to be Prepared:
-
-
-
-
INTERVIEW SUMMARY:
14. Information Systems Documentation Template
14
Implementation
System Requirements
Testing
Analysis
Deign
1.4 DEVELOPMENT PROCESS
We decided to apply the Waterall/Iterative/Prototyping/…. developmenttechnique.
The reason for using this technique is ……
Figure 1.1: Development Process Phases
15. Information Systems Documentation Template
15
Chapter 2
SYSTEM ANALYSIS
2.1 USED METHODOLOGY:
Structured or Object-Oriented approach
16. Information Systems Documentation Template
16
2.2 ANALYSIS MODELS
Event/use cases Table
Event Trigger Source Use case Response Destination
passenger
wants to
search for a
flight
Search
request
Passenger
or clerk
Search for
flight
Suitable
Flights
Information
Passenger /
clerk
Making a
New user
account
New
account
Request
Passenger /
clerk
Create new
Account
Create a
member ID
Passenger /
clerk
Paying for
the
Tickets
Pay
inquiry
Passenger /
clerk
Pay for
tickets
Data
updating
Credit / Bank
Canceling
tickets
online
Cancel
book
Passenger Cancel
booked
tickets
Data
updating
Credit / Bank
Canceling
tickets with
telephone
Cancel
book
clerk Cancel
booked
tickets
Data
updating
Credit / Bank
Passenger
want to
login
Login
request
Passenger /
clerk
Login Data
validating
Passenger /
clerk
Editing
personal
information
Edit
inquiry
Passenger /
clerk
Edit
personal
information
Data
updating
Viewing
reviews
Viewing
request
Passenger /
clerk
View
reviews
View
information
Passenger /
clerk
Writing
reviews
Review
request
Passenger Write
reviews
Data
updating
Booking
with
telephone
Book
inquiry
Passenger /
clerk
book with
telephone
Booking the
ticket /
sending
tickets ID
Passenger /
clerk
17. Information Systems Documentation Template
17
Viewing
offers
Viewing
request
Passenger /
clerk
View offers View
information
Passenger /
clerk
Actors
-passenger
-Clerk
-Bank
Models (According to the used Methodology)
UML Diagram:
Create new account
Login
Edit
basics information
Search for flight
19. Information Systems Documentation Template
19
2.3 PROCESSES LOGIC
Structured English or Pseducode(forStructured)
Scenario (for Object-Oriented)
20. Information Systems Documentation Template
20
Chapter 3
SYSTEM DESIGN
3.1 SYSTEM DATABASE DESIGN:
Entities Determination
Relationships between Entities
Normaization
3.1.1 ENTITY RELATIONSHIP DIAGRAM (ERD):
The ER-Diagram represents the overall logical structure of a database, which
is independentof any software or data storage structure. The database of our
system is shown in figure 3.1. This modeldescribes the relationship among
the tables.
22. Information Systems Documentation Template
22
3.1.2 TABLES DESIGN:
1-AdminsTable:
1.1 Table Columns:
a- Admin ID: This is the number given to admins.
b- UserName: This is the name that has to choose.
c- Password: This is the password that the admin choose it.
2.
3.
4.
26. Information Systems Documentation Template
26
Chapter 4
SYSTEM IMPLEMENTATION
4.1 Used Technologies
4.1.1 Database
4.1.2 Programming
4.1.3 Reporting
27. Information Systems Documentation Template
27
4.2 System Implementation Plan
4.2.1 ADMINISTRATION
The System administrator is responsibleforcontrolling and managing the
Figure 4.1: Admin Login
32. Information Systems Documentation Template
32
Chapter 5
SYSTEM TESTING
To test our system, we should start testing each page one at a time. All the pages
are accessedand tested.
5.1 Testing Check List
Testing checklist for each page:
1- The design of the page
2- The links
3- The menus
4- The functionalities in the page
5- The validation in the page
6- Test page with random data
34. Information Systems Documentation Template
34
Chapter 6
FUTURE WORK AND CONCLUSION
The Project Team managed to develop
The team hopes that resources will be allocated in the future to implement and
operate the system.
The following parts of XXXXXXX System were set aside for future
implementation:
-
-
-
