Airline Reservation Project

Airline Reservation System
Sobhasaria Engineering College

Gokulpura, Sikar
SESSION 2009-10
PROJECT ON
AIRLINE RESERVATION SYSTEM
Submitted By:
To:
Tejprakash Saini
BranchComputer Science
Mr. Sandeep Srivastava
IIIrd Year (Vth SEM)

Roll NO.-- 07ESOCS122
Project on
AIRLINE RESERVATION SYSTEM
ACKNOWLEDGEMENT
I would like to take this opportunity to express my gratitude towards all the people who have in various ways, helped in the successful completion of my project. I must convey my gratitude to Mr. Sandeep Srivastava for giving me the constant source of inspiration and help in preparing the project, personally correcting my work and providing encouragement throughout the project.
INDEX
1.) INTRODUCTION a) PURPOSE b) SCOPE c) DEFINITION d) REFERENCE e) OVERVIEW GENERAL DESCREPTIVE a) PRODUCT PRESPRECTIVE b) PRODUCT FUNCTION OVERVIEW c) USER CHARSTATICS d) GENERAL CONSTRAINTS SPECIFIC REQUIREMENTS a) EXTERANAL INTERFACE REQUIREMENTS I) USER INTERFACE II) HARDWARE INTERFACE III) SOFTWARE INTERFACE b) c) d) e) 4.) FUNCTIONAL REQUIREMENTS PERFORMANCE REQUIREMENTS DESIGN CONSTRAINTS ATTRIBUTES
Page NO.
5 5 5 5 7 7 8 8 9 9 9 10 10 10 10 11 11 15 15 16 17 17 22 39 43 46 48 49
2.)
3.)
SYSTEM ANALYSIS & DESIGN a) FEASIBILITY STUDY b) UML DIAGRAMS c) E-R DIAGRAM d) DATA FLOW DIAGRAM TESTING AND DEBUGGING CONCLUTION PROGRAM OUTPUT
5.)
6.) 7.)
1. INTRODUCTION :
1.1 ) PURPOSE
The main purpose of this software is to reduce the manual errors involved in the airline reservation process and make it convenient for the customers to book the flights as when they require such that they can utilize this software to make reservations, modify reservations or cancel a particular reservation.
1.2) SCOPE
The name of the software is AIRLINE RESERVATION SYSTEM. This software provides options for viewing different flights available with different timings for a particular date and provides customers with the facility to book a ticket, modify or cancel a particular reservation it provide the customers with details of cost of the ticket and but it does not allow the customer to modify a particular part of his reservation and he/she cant modify all his details.
1.3) DEFINITIONS, ACRONYMS AND ABBREVIATIONS

ARS-Airline Reservation System LAN-Local Area Network GUI-Graphical User Interface OS-Operating System RAM-Random Access Memory MB-Mega Bytes GB-Giga Bytes Mbps-Mega bits per second HDD-Hard Disk Drive
PROBLEM DEFINITION
The definition of our problem lies in manual system and a fully automated system. Manual system : The system is very time consuming and lazy. This system is more prone to errors and sometimes the approach to various problems is unstructured.
Technical system :
With the advent of latest technology if we do not update our system then our business result in losses gradually with time. The technical systems contains the tools of latest trend i.e. computers printers, fax, Internet etc. The systems with this technology are very fast, accurate, user-friendly and reliable.
. TECHNICAL SYSTEM
Need of Airlines system

A few factors that directs us to develop a new system are given below -: 1) Faster System
2) 3) 4) 5)
Accuracy Reliability Informative Reservations and cancellations from anywhere to any place
AIRLINES SYSTEM
RESERVATION
CANCELLATION
UPDATION
1.4) REFERENCES
The books and materials referred during the pre-development stages of the project include 1. Software Engineering-A Practitioners Approach By Roger S. Pressman 2. Software Engineering-By James Peters
1.5) OVERVIEW
The rest of the document deals about all the main features of this software each will its purpose and its main functions. It also gives details about the interface with other products and related functionality of each product.
2. OVERALL DESCRIPTION
2.1) PRODUCT PERSPECTIVE :The ARS software is an independent application. It is a self-contained product. The system interfaces, user interfaces and hardware interfaces related with this software are defined as follows.
I.
System Interfaces
The client systems should be able to share the data available in the data base through the network connection.
II.
User Interfaces
The screen formats and menu structure should be in such a way that even have users will find it easy to use. The product must be use-friendly and very inter-active. The functionality provided by the system like displaying error messages should adapt itself to the different users of the software.
III.
Hardware Interfaces
i. Keyboard ii. Monitor iii. Mouse etc
IV. V.
used.
Software Interfaces
Name of the language: C++
Communication Interfaces
There is an LAN used for communication among the different client systems to be
VI.
Memory Constraints
The system would require disk space of 10 GB and a 256 MB HDD and 64 MB RAM for client systems.
VII.
Operation
The users can first make a reservation in a particular flight for a particular date and time. The system provides the customer with a pin code which gives him access to either make any changes in his reservation or cancel a reservation. These must also be back up of data to enable any easy recovery from any features.
The ARS software is an independent and self-contained product and no modification are required to adapt to a particular installation.
2.2) PRODUCT FUNCTIONS :The major functions include y Providing flight details y Flight bookings for a particular destination, date and time and also providing with a pin code. y Allowing the customer to modify or cancel his reservation provided the correct pin code is given. y Displaying a report of the number of people flying in a particular flight.
2.3) USER CHARACTERISTICS :No technical experience is required basic knowledge of handling system is sufficient.
2.4) CONSTRAINTS :y y y y y y y y Regulatory policies: It is a mandatory that no text book must be left empty or contains insufficient data. Hardware limitations: There must be a 64 MB on board memory Control functions: The software must be very user-friendly and display appropriate error messages. Interfaces to other applications: Not applicable. Parallel operations: It must support many users simultaneously. Reliability requirements: Data redundancy and use of special/blank characters must be avoided. Safety/security considerations: The application must be exited always normally. Higher order language requirements: C++
2.5) ASSUMPTIONS AND DEPENDENCIES :It is assumed that the details of the cost of ticket are already known to the customer. Future changes like providing different types of flights with different classes like business class, economic class will allow the customers to benefit from one facility.
3. SPECIFIC REQUIREMENTS
3.1) EXTERNAL INTERFACE REQUIREMENTS I. User Interfaces
The interface must be easy to understand. The user interface includes y SCREEN FORMATS/ORGANIZATION: The introductory screen will be the first to be displayed which will allow the users to choose either of the two options, viewing flight detail or booking a ticket. y WINDOW FORMAT/ORGANIZATION: When the user chooses some other option, then the information pertaining to that choice will be displayed in a new window which ensures multiple windows to be visible on the screen and the users can switch between them. y DATA FORMAT: The data entered by the users will be alpha numeric. y ERROR MESSAGES: When there are some exceptions raising error like entering invalid details, then error messages will be displayed prompting the users to re-enter the details.
II.
Hardware Interfaces
The system must basically support certain input and output devices. Their descriptions are as follows. Name of Item Description of Purpose Source of Input/ Description of output Key board To accept data from user like Source of Input pin code, personal details, flight details To display the bookings Destination of Output mode E.g.: Destination chosen with date and timings
Monitor
10
III.
Software Interfaces
Operating System: windows 95/98/me/2000/xp/NT/vista/7 RAM: 64 MB Graphics card: Supports any HDD Space: 5MB
IV.
Communication Interfaces
Every client system connected through LAN establishes a communication only with the server and not with any client system. An LAN of 10 Mbps is used.
3.2). FUNCTIONAL REQUIREMENTS :

I. FEATURE 1
The ability of the software is to provide the details of the flights available and allow the customers to choose a particular destination and make a reservation
A. PURPOSE
The purpose of this is to enable the users to view the different flights available so as to make it convenient for him to make a reservation.
B. STIMULUS/RESPONSE
Once the user chooses the particular option, the web pages corresponding to that are to be displayed on the screen i.e., it will display the different flights available to their respective destinations and allow the customer to book a ticket.
C. ASSOCIATED FUNCTIONAL REQUIREMENTS

Once the user makes a reservation, he must be provided with a pin code.
(i). INTRODUCTION
The user must be provided with the required information within 10 seconds.
11
(ii). INPUTS
The user must enter the destination with date and timings and must make reservation by giving his personal details like name, address, age, gender, nationality.
(iii). PROCESSING
Recognizing the correct details are entered that a message is displayed confirming his reservation and displays the pin code.
II.
FEATURE 2
The software allows the user to modify an already existing reservation made by the customer if in case there are any changes that are to be modified in the reservations of the ticket.
A. PURPOSE
The purpose is to allow the customer to make any changes in his personal details or flight booking details.
Once the user requests for changing his reservation, it must be displayed on the screen prompting the customer to enter his pin code.
C. ASSOCIATED FUNCTIONALITY REQUIREMENTS

If the pin code provided by the customer does not match, then would notify the person by displaying error messages.
(i). INTRODUCTION
The system will allow the customer to modify his reservation provided correct pin code has been entered by him.
(ii). INPUT
The user should enter his pin code which gives him access to modify his reservation.
12
(iii). PROCESSING
The pin code is processed and checked for his validity. If it is correct then the user can modify his reservation else an error message will be displayed asking the user to enter the correct pin code number.
(iv). OUTPUT
Given the correct pin code, the user can now modify his reservation. A new pin code will be generated for the customers.
III.
FEATURE 3
The software allows the user to cancel an already existing reservation made by the customer who has booked the ticket.
A. PURPOSE
The purpose is to allow the customer to cancel his reservation if not required.
Once the user requests for canceling his reservation, it must be displayed on the screen prompting the customer to enter his pin code.

If the pin code provided by the customer does not match, then it would notify the person by displaying error messages.
(i). INTRODUCTION: The system will allow the customer to cancel his reservation provided correct pin code has been entered by the customer. (ii). INPUT: The user should enter his pin code which gives him access to
cancel his reservation.
(iii). PROCESSING: The pin code is processed and checked for its validity. If
it is correct, then the user can cancel his reservation else an error message will be displayed asking the user to enter the correct pin code number.
(iv). OUTPUT: Given the correct pin code, the user can now cancel his
reservation.
13
IV.
FEATURE 4
The software must also give a report on the number of reservations made for a particular flight.
A. PURPOSE
The purpose is to enable the administrator to view the number of people in a particular flight.
Once the user requests for this option, all the details of the customers who have made reservation will be displayed.

If no reservations are made, then a message is displayed that no bookings have been made.
(i). INTRODUCTION :
The system will allow the administrator to view all the details of the customer who have made reservations.
(ii). INPUT :
The administrator must enter the password so that access is given only to him to view the details of all the customers.
(iii). PROCESSING:
The password is processed and checked for its validity. If it is not correct, then the administrator is asked to enter the correct password.
(iv). OUTPUT:
Given the correct password, the administrator can view all the details of customers with date and time of their bookings made.
Algorithm :
in this phase further i had designed algorithms for various technical sub problem a few than are enclosed here with.
Reservation :
14
Step 1: Step 2: Step 3: Step 4: Step 5: Step 6: flight.
a person comes to reserve a ticket. then he gives his full details in customer form those details were written. then computer cheque the date what date the person reserved then system justify the specific flight id if customer want domestic or international flight then system check availability of
Step 7: Step 8: Step 9: Step 10: Step 11: Step 12: Step 13: Step 14: Step 15:
if seat is empty then system reserved the seat. then ticket is generated. the ticket is confirmed. if the condition is not applied then it check next seat and justified it. if it is not also empty then it checks next by next. if there is no seat then system take ticket which is not confirmed then it give waiting list. end.
Cancellation :
Step 1: a passenger comes to cancel the ticket Step 2: then the system open the delete form Step 3: it display all the passenger list Step 4: then user enter its password of flight. Step 5: Step the system show record is deleted. when passenger come to reserved a ticket then system find out the flight details.
3.3) PERFORMANCE REQUIREMENTS
y y
At any instant, a maximum of four nodes or users will be given access simultaneously. Since the program handles multiple users, if more than one person attempts to same date to the files stored in the data base, the program will lock the data file using a 2-phase commit protocol to prevent simultaneous access.
15
3.4) DESIGN CONSTRAINTS

y y y Requires 256 MB on-board memory. Based completely on Windows functionality platform. The software should be portable and must be inaccessible to unauthorized users.
3.5)
I.
y y
ATTRIBUTES Reliability
The factors needed to establish the software expected reliability are The user inputs should be valid and within the given range. Normal termination of the program.
II.
Availability
The factors guarantee the softwares availability includes proper termination and correct input details. Also the resources used for the project development are Microsoft Certified which speaks of its high quality standards.
III.
y y y
Security
It must be ensured that access will be provided to the authorized persons through user ID and password. Network security will be provided by the use of firewalls. Checks can be performed at regular intervals to ensure data integrity.
IV.
Maintainability
The software will be developed by implementing the concept of modularity which in turn reduces the complexity involved in maintaining it. The administrator should have a sound technical knowledge about maintaining the software and further enhancements will be undertaken by the developer.
V.
Portability
The application is portable which ensures its adaptability for use on different computer terminals with different operating systems and standards.
16
4. SYSTEM ANALYSIS & DESIGN

Systems analysis is a process of collecting factual data, understand the processes involved, identifying problems and recommending feasible suggestions for improving the system functioning. This involves studying the business processes, gathering operational data, understand the information flow, finding out bottlenecks and evolving solutions for overcoming the weaknesses of the system so as to achieve the organizational goals. System Analysis also includes sub dividing of complex process involving the entire system, identification of data store and manual processes. The major objectives of systems analysis are to find answers for each business process: What is being done, How is it being done, Who is doing it, When is he doing it, Why is it being done and How can it be improved? It is more of a thinking process and involves the creative skills of the System Analyst. It attempts to give birth to a new efficient system that satisfies the current Needs of the user and has scope for future growth within the organizational constraints. The result of this process is a logical system design. Systems analysis is an iterative process that continues until a preferred and acceptable solution emerges.
I.
THE FEASIBILITY STUDY
The Feasibility study is an analysis of possible alternative solutions to a problem and a recommendation on the best alternative. It can decide whether a process be carried out by a new system more efficiently than the existing one. The feasibility study should examine three main areas; - market issues, - technical and organizational requirements, - financial overview. The results of this study are used to make a decision whether to proceed with the project, or table it. If it indeed leads to a project being approved, it will - before the real work of the proposed project starts - be used to ascertain the likelihood of the project's success. A feasibility study should provide management with enough information to decide : 1. Whether the project can be done; 2. Whether the final product will benefit its intended users; 3. What are the alternatives among which a solution will be chosen (during subsequent phases)? 4. Is there a preferred alternative? Content of a feasibility study Things to be studied in the feasibility study:
17
The present organizational system Stakeholders, users, policies, functions, objectives... Problems with the present system Inconsistencies, inadequacies in functionality, performance Possible solution alternatives Sticking with the current system is always an alternative Different business processes for solving the problems Different levels/types of computerization for the solutions Advantages and disadvantages of the alternatives
Types of Feasibility :--The feasibility study includes complete initial analysis of all related system. Therefore the study must be conducted in a manner that will reflect the operational, economic as well as technical and scheduling feasibility of the system proposal. These are the four main types of feasibility study.
(i). Operational Feasibility :

This aspect defines the urgency of the problem and the acceptability of any solution. It shows if the system is developed, will it be used. The operational study shows that there would be no manpower problems, labor objections, manager resistance, organizational conflicts and policies; also external issues, including social acceptability, legal aspects and government regulations are fulfilled in this. It shows that the current work practices and procedures support a new system and social factors is that this system will make the work easier for the cashier or who so ever may be the user of this system. Operational- There is no operational problem associated to this project. Performance- The current mode of operation is adequate throughout. Information- The current mode of system provides the end users and managers with timely, pertinent, accurate and usefully formatted information. Economy- The current mode of operation is very cost effective and requires no further investment. Control- The current mode of operation offer effective controls to protect against fraud and to guarantee accuracy and security of data and information. Efficiency- The current mode of operation makes maximum use of available resources, including people, time etc.
18
(ii). Technical Feasibility:

In technical feasibility the following issues are taken into consideration. The required technology for our system is available very easily. As the project is a small scale project we just required a few people to work as tester, programmer and debugger for the software and hardware. The technical aspect explored that the project was completely feasible with the limits of current technology and this technology is available within the budget and schedule. As input device we just required a keyboard which is easily available and we saved the data in text files which are to be used in all operating systems. As an output device to we just required the monitor and printer which are available easily. The choice of processing unit depends on the user and this is feasible with all of them
By the analyst: The proposed solution is completely practical. The technology used is very much possessed in the current scenario. The schedule is reasonable and the people concerned are capable from technical point of view. The technology can be easily applied to todays scenario.
(iii). Schedule Feasibility:

A project will fail if it takes too long to be completed before it is useful. Typically this means estimating how long the system will take to develop, and as this system is completed in a given time period using some methods like payback period therefore its completely feasible. The project timetable is fully reasonable. Given our technical expertise, the project deadlines are reasonable. A particular schedule is prepared by our analyst by whom its estimated that we would be completing the project as per the desirable deadline provided to us.
(iv). Economic Feasibility:

Economic analysis or we can say the cost/benefit analysis tells us the effectiveness of our system. For any system if the expected benefits equal or exceed the expected costs, the system
19
can be judged to be economically feasible and the same goes for ours to as this system proves to be utterly feasible in economic logic. To check the economic feasibility, cost benefit analysis is done in which expected costs and benefits are evaluated. By economic analysis we evaluated the effectiveness of the system proposed to us.
Cost/Benefit Analysis:The cost/benefit analysis suggested that: The project completely justified. The project can be done, within given cost constraints The minimal cost to attain a certain system was nominal
Difficulties:Discovering and assessing benefits and costs; they were both be intangible, hidden and hard to estimate, it's also hard to rank multi-criteria alternatives Examples of particular benefits: cost reductions, error reductions, increased flexibility of operation, improved operation, better (e.g., more accurate) and more timely information. Conclusion:An entrepreneur accurately calculated the cost versus benefits before taking an action. Time Based: Contrast to the manual system management generates any report just by single click. Cost Based: No special investment is needed to manage the tool. No specific training is required for employees to use the tool. Investment requires only once at the time of installation. The software used in this project is freeware so the cost of developing the tool is minimal.
20
II.
UML(Unified Modeling Language)
Unified Modeling Language (UML) is a standardized general-purpose modeling language in the field of software engineering. The standard is managed, and was created by, the Object Management Group. UML includes a set of graphical notation techniques to create visual models of softwareintensive systems.
Overview
The Unified Modeling Language (UML) is used to specify, visualize, modify, construct and document the artifacts of an object-oriented software intensive system under development. 1. UML offers a standard way to visualize a system's architectural blueprints, including elements such as:
y y y y y y y
actors business processes (logical) components activities programming language statements database schemas, and reusable software components.
2. UML combines best techniques from data modeling (entity relationship diagrams), business modeling (work flows), object modeling, and component modeling. It can be used with all processes, throughout the software development life cycle, and across different implementation technologies.[3] UML has synthesized the notations of the Booch method, the Object-modeling technique (OMT) and Object-oriented software engineering (OOSE) by fusing them into a single, common and widely usable modeling language. UML aims to be a standard modeling language which can model concurrent and distributed systems. UML is a de facto industry standard, and is evolving under the auspices of the Object Management Group (OMG). OMG initially called for information on object-oriented methodologies that might create a rigorous software modeling language. Many industry leaders have responded in earnest to help create the UML standard.
UML Notation Baseline

Use Case Diagrams Class Diagrams
21

Package Diagrams Activity Diagrams State-Transition Diagrams Event Trace (Interaction) Diagrams Sequence Diagrams Collaboration Diagrams Deployment Diagrams
Activity Diagram :
Activity diagrams represent the business and operational workflows of a system. An Activity diagram is a dynamic diagram that shows the activity and the event that causes the object to be in the particular state. The easiest way to visualize an Activity diagram is to think of a flowchart of a code. The flowchart is used to depict the business logic flow and the events that cause decisions and actions in the code to take place. So, what is the importance of an Activity diagram, as opposed to a State diagram? A State diagram shows the different states an object is in during the lifecycle of its existence in the system, and the transitions in the states of the objects. These transitions depict the activities causing these transitions, shown by arrows. An Activity diagram talks more about these transitions and activities causing the changes in the object states.
Elements of activity diagram :

Initial Activity:
This shows the starting point or first activity of the flow denoted by a solid circle. This is similar to the notation used for Initial State.
Activity:
Represented by a rectangle with rounded (almost oval) edges.
Decisions:
22
Similar to flowcharts, a logic where a decision is to be made is depicted by a diamond, with the options written on either sides of the arrows emerging from the diamond, within box brackets.
Horizontal/Vertical Synch Bar :

Horizontal and vertical synchronization bar used to synchronize different activities together and represented by horizontal and vertical bar.
Swim Lanes :
Activity diagrams provide another ability, to clarify which actor performs which activity.. If we wish to distinguish in an Activity diagram the activities carried out by individual actors, vertical columns are first made, separated by thick vertical lines, termed "swim lanes," and name each of these columns with the name of the actor involved. Each of the activities placed below the actor performing these activities and then shows how these activities are connected.
23
Concurrent Activities:
Some activities occur simultaneously or in parallel. Such activities are called concurrent activities. For example, listening to the lecturer and looking at the blackboard is a parallel activity. This is represented by a horizontal split (thick dark line) and the two concurrent activities next to each other, and the horizontal line again to show the end of the parallel activity.
Final Activity:
The end of the Activity diagram is shown by a bull's eye symbol, also called as a final activity.
24
Fig.- Activity diagram of ARS
25
Sequence Diagram :
A Sequence diagram depicts the sequence of actions that occur in a system. The invocation of methods in each object, and the order in which the invocation occurs is captured in a Sequence diagram. This makes the Sequence diagram a very useful tool to easily represent the dynamic behavior of a system. A Sequence diagram is two-dimensional in nature. On the horizontal axis, it shows the life of the object that it represents, while on the vertical axis, it shows the sequence of the creation or invocation of these objects. Because it uses class name and object name references, the Sequence diagram is very useful in elaborating and detailing the dynamic design and the sequence and origin of invocation of objects. Hence, the Sequence diagram is one of the most widely used dynamic diagrams in UML. Sequence Diagram elements :
Object:
The primary element involved in a sequence diagram is an Objectan instance of a class. A Sequence diagram consists of sequences of interaction among different objects over a period of time. An object is represented by a named rectangle. The name to the left of the ":" is the object name and to its right is the class name.
Message:
The interaction between different objects in a sequence diagram is represented as messages. A message is denoted by a directed arrow. Depending on the type of message, the notation differs. In a Sequence diagram, you can represent simple messages, special messages to create or destroy objects, and message responses.
26
Sequence diagram:
Customer
System
1. Search Flight ( )
2. Display available flights
3. Book Flight ( ) Verify Details &write in file
4. Confirm Booking ( )
5. Ticket enquiry ()
6. Display ticket details 7. Ticket cancellation ( ) Delete ticket details from file
8. Exit ( )
Exit from program
27
Use Case Diagrams

Show the external actors and their connection to the functionality (use cases) of The system Use cases provide the basis of communication between sponsors/customers and implementers in the planning of a project Capture some user-visible function May be small or large Achieves a discrete goal for the
Explanation:
Use Case diagrams identify the functionality provided by the system (use cases), the users who interact with the system (actors), and the association between the users and the functionality. Use Cases are used in the Analysis phase of software development to articulate the high-level requirements of the system. They essentially are created to visualize the relationships between actors and use cases. The primary goals of Use Case diagrams include: Providing a high-level view of what the system does Identifying the users (actors) of the system Determining areas needing human-computer interfaces The basic components of Use Case diagrams are the Actor, the Use Case, and the Association.
Actor
28
An Actor, as mentioned, is a user of the system, and is depicted using a stick figure. The role of the user is written beneath the icon. Actors are not limited to humans. If a system communicates with another application, and expects input or delivers output, then that application can also be considered an actor.
UseCase
A Use Case is functionality provided by the system, typically described as verb+object (e.g. Register Car, Delete User). Use Cases are depicted with an ellipse. The name of the use case is written within the ellipse.
Association
Associations are used to link Actors with Use Cases, and indicate that an Actor participates in the Use Case in some form. Associations are depicted by a line connecting the Actor and the Use Case. An association can be labelled <<uses>> or <<extends>>. Uses means that a particular use case explicitly incorporates the behaviour of another use case at a specified level in that use case. Extends is used to separate optional behaviour from mandatory behaviour.
29
Use Case Diagram :
30
III.
E-R DIAGRAM
In this phase initially I had designed E-R diagram of the processes , in order to identify various entities and relationship set ,entity set ,attributers, link attributes The Diagram of this process as under. After this step We had tried design the data base for the new system and normalized it The tables motivated in data dictionaries enclosed as annex II is an outcome of this step
The symbol of entities are shown bellow:-
Entity sets
Relationship set
line Attributes
Entity Relationship Diagram Notations

Peter Chen developed ERDs in 1976. Since then Charles Bachman and James Martin have added some sligh refinements to the basic ERD principles.
Entity
An entity is an object or concept about which you want to store information. Entity
Weak Entity
31
Attributes are the properties or characteristics of an entity.
Entity
Key attribute
A key attribute is the unique, distinguishing characteristic of the entity. For example, an employee's social security number might be the employee's key attribute. Attribute
Multivalued attribute
A multivalued attribute can have more than one value. For example, an employee entity can have multiple skill values.
Attribute
Derived attribute
A derived attribute is based on another attribute. For example, an employee's monthly salary is based on the employee's annual salary.
Attribute
Relationships
Relationships illustrate how two entities share information in the database structure.First, connect the two entities, then drop the relationship notation on the line.
Relationship
cardinality
Cardinality specifies how many instances of an entity relate to one instance of another entity.
32
E-R DIAGRAM
33
IV. DATA FLOW DIAGRAM (DFD)
Data Flow Diagramming is a means of representing a system at any level of detail with a graphic network of symbols showing data flows, data stores, data processes, and data sources/destination. Data Flow Diagrams are composed of the four basic symbols shown below.
34
LEVEL 0: DFD OF RESERVATION SYSTEM :
Reservation
User
Display
Cancellation
LEVEL 1 : a. DFD OF RESERVATION:
User
Reservation
Accept Details
Reserve in the file
FILE
35
LEVEL 1 (b).DFD OF CANCELLATION
User
Cancellation
Accept the Details
Cancel in the file
FILE
LEVEL 2. DFD OF ENQUIRY:
User
Display
Read Passenger details
FILE
Display in tabular form
36
5.
TESTING & DEBUGGING
Software testing is a process of running with intent of finding errors in software. Software testing assures the quality of software and represents final review of other phases of software like specification, design, code generation etc.
I.
Black-box (Functional ) Testing:
Black box testing treats the software as a "black box" without any knowledge of internal implementation. Black box testing methods include: equivalence partitioning, boundary value analysis, all-pairs testing, fuzz testing, model-based testing, traceability matrix, exploratory testing and specification-based testing. Specification-based testing: Specification-based testing aims to test the functionality of software according to the applicable requirements. Thus, the tester inputs data into, and only sees the output from, the test object. This level of testing usually requires thorough test cases to be provided to the tester, who then can simply verify that for a given input, the output value (or behavior), either "is" or "is not" the same as the expected value specified in the test case. Specification-based testing is necessary, but it is insufficient to guard against certain risks. Advantages and disadvantages: The black box tester has no "bonds" with the code, and a tester's perception is very simple: a code must have bugs. Using the principle, "Ask and you shall receive," black box testers find bugs where programmers do not. But, on the other hand, black box testing has been said to be "like a walk in a dark labyrinth without a flashlight," because the tester doesn't know how the software being tested was actually constructed. As a result, there are situations when (1) a tester writes many test cases to check something that could have been tested by only one test case, and/or (2) some parts of the back-end are not tested at all. Therefore, black box testing has the advantage of "an unaffiliated opinion," on the one hand, and the disadvantage of "blind exploring," on the other.
II.
White-box testing:
In white box testing knowing the internal working of the product, tests can be conducted to ensure that internal operations are performed according to specification and all internal components have been adequately exercised. In white- box testing logical path through the software are tested by providing test cases that exercise specific sets of conditions and loops.
37
Using white-box testing software developer can derive test case that Guarantee that all independent paths within a module have been exercised at least once. Exercise all logical decisions on their true and false side. Exercise all loops at their boundaries and within their operational bound. Exercise internal data structure to ensure their validity. At every stage of project development I have tested the logics of the program by supplying the invalid inputs and generating the respective error messages. All the loops and conditional statements are tested to the boundary conditions and validated properly.
III.
Interface Testing :
Interface testing is one of the most important software tests in assuring the quality of software products. In a nutshell, human beings are able to communicate with hardware through an interface. Interface is actually software that consists of sets of messages, commands, images, and other features that allow communication between a device and a user. Various companies use this type of software testing to make sure that their customers will not encounter any problem when using a particular software product once it is delivered to them. In addition, developers usually want their products to be supported by more than one language thus, their need to understand the interface. In this test, developers come up with changes or revisions and introduce these to a software application by taking note of the feedback from end-users. Usually, each end-user is assigned a specific task. During the course of this test, the program flow is checked and evaluated to determine if it matches the natural strategy of the user in navigating within the application. Moreover, this test determines which application areas are initially and usually accessed and its user-friendliness as well. A moderator is often tasked to undertake this quality assurance test. Throughout the process, he does not need to communicate anything to the end-user. Rather, he will only be documenting or recording the reaction of the user towards the application. At the session's end, he interviews the end-users and endorses their feedback to the software developer. This way, interface testing improves the software's overall acceptance and the consumer's user experience. Factors like functionality, performance speed, the time needed to use the program, the ease with which the user remembers using the program, user satisfaction, and the rate of user errors are the usual criteria that developers have for a well-designed user interface.
38
6.
conclusion
Though the system still contains a lot of scope of improvement in it. But its overall look and feel gives rough picture of on existing automation system.
39
7.
PROGRAM OUTPUT
OUTPUT -------------------------------------------------------------------------------AIRLINE RESERVATION SYSTEM -------------------------------------------------------------------------------MENU: 1:FLIGHTS 2:RESERVATION 3:DISPLAY 4:CANCELLATION 5:EXIT Enter your choice : 1 --------------------------------------------------------------------------------
40
FIG.: Screenshot to chose the RESERVATION option
41
42
43
44
45
46
47
48
49
50
TEST CASES
INPUT
Reservation: reserve { .. .. .. .. }
PROCESSING
Reservation system: Input the details about the passenger and the flight in which they are willing to travel. It generates a password for the passenger.
OUTPUT
Enter the passenger details: Name-abc Address-CH-17,Bajaj Road, Sikar E-Mail id-nhjs@yahoo.co.in Telephone no-9829472222 Enter the date of traveling1:domestic 2:international Enter the mode: 2 Enter the plane 4or5or6-6 PASSWORD 171
Cancellation: cancel { .. .. .. .. }
Enter the password:21 Cancellation: Input the Password of Reservation cancelled the passenger to be deleted. And cancels the flight.
51

Airline Reservation Project

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Airline Reservation Project

Caricato da

Copyright:

Formati disponibili

Airline Reservation System

Sobhasaria Engineering College

AIRLINE RESERVATION SYSTEM

Mr. Sandeep Srivastava

IIIrd Year (Vth SEM)

Airline Reservation System

AIRLINE RESERVATION SYSTEM

Airline Reservation System

Airline Reservation System

Airline Reservation System

1.3) DEFINITIONS, ACRONYMS AND ABBREVIATIONS

Airline Reservation System

Need of Airlines system

Airline Reservation System

Airline Reservation System

Airline Reservation System

Airline Reservation System

3.1) EXTERNAL INTERFACE REQUIREMENTS I. User Interfaces

Airline Reservation System

3.2). FUNCTIONAL REQUIREMENTS :

C. ASSOCIATED FUNCTIONAL REQUIREMENTS

Airline Reservation System

C. ASSOCIATED FUNCTIONALITY REQUIREMENTS

Airline Reservation System

C. ASSOCIATED FUNCTIONAL REQUIREMENTS

Airline Reservation System

C. ASSOCIATED FUNCTIONAL REQUIREMENTS

Airline Reservation System

Step 1: Step 2: Step 3: Step 4: Step 5: Step 6: flight.

3.3) PERFORMANCE REQUIREMENTS

Airline Reservation System

3.4) DESIGN CONSTRAINTS

Airline Reservation System

4. SYSTEM ANALYSIS & DESIGN

THE FEASIBILITY STUDY

Airline Reservation System

(i). Operational Feasibility :

Airline Reservation System

(ii). Technical Feasibility:

(iii). Schedule Feasibility:

(iv). Economic Feasibility:

Airline Reservation System

Airline Reservation System

UML(Unified Modeling Language)

UML Notation Baseline

Airline Reservation System

Elements of activity diagram :

Airline Reservation System

Horizontal/Vertical Synch Bar :

Airline Reservation System

Airline Reservation System

Fig.- Activity diagram of ARS

Airline Reservation System

Airline Reservation System

2. Display available flights

3. Book Flight ( ) Verify Details &write in file

Exit from program

Airline Reservation System

Use Case Diagrams

Airline Reservation System

Airline Reservation System

Use Case Diagram :