Online Flight Ticket Reservation System

Online Flight Ticket Reservation System

Experiment No: 1

A STUDY EXPERIMENT ON STAR UML 5.0

Experiment Date:

STUDY EXPERIMENT ON STAR UML 5.0

AIM:-

To study the basic concepts of Unified Modeling Language.

UML NOTATION

· Unified Modeling Language.

· Set of notations and conventions used to describe and model an application.

· Universal language for modeling systems.

· Standard notation for OO modeling systems.

· Does not specify methodology to develop an application.

UML DIAGRAMS

· Class Diagram

· Use Case Diagram

· Behavioral Diagram

ü Interaction Diagram

§ Sequence Diagram

§ Collaboration Diagram

ü State Chart Diagram

ü Activity Diagram

· Implementation Diagram

ü Component Diagram

ü Deployment Diagram

CLASS DIAGRAM

· Shows the static structure of the model.

· Collection of static modeling elements such as classes and their relationships connected as a graph.

· Provides visual representation of objects, relationships and their structures.

Class:-

· A class is a set of objects that share a common structure and common behavior.

· It is represented as:

Interface:-

· Specifies the externally-visible operations of a class and/or component.

Association:-

· Model properties of associations.

· The properties are stored in a class and linked to the association relationship.

· Example,

Generalization:-

· A generalize relationship is a relationship between a more general class or use case and a more specific class or use case.

· Example,

USE CASE DIAGRAM

· Set of use cases enclosed by system boundary, communication association between actors and use cases, and generalization among use cases.

Actors:-

· External factors that interacts with the system from the user's perspective.

Use Cases:-

· Set of scenarios that describe how actor uses the system.

· Represented as,

Relationship:-

· Communication – communications with the use case normally.

· Uses – Shown by generalization arrow from the use cases.

· Extends – Used when one case does more than another that is similar to it.

BEHAVIOR DIAGRAM

INTERACTION DIAGRAM

· Diagrams that describes how group of objects are collaborated.

SEQUENCE DIAGRAM:

· Describes the behavior of the system through interaction between the system and the environment in time sequence.

· Two dimensions:

ü Vertical dimension – represents time.

ü Horizontal dimension – represents objects.

· Life line – Object's existence during the interaction.

<Event>

COLLABORATION DIAGRAM:

· An interaction diagram that shows the order of messages that implement an operation or a transaction.

· Collaboration diagrams show objects, their links, and their messages.

1. <Event

Object:-

· An object has state, behavior, and identity.

· Objects interact through their links to other objects.

Link:-

· A link is an instance of an association, analogous to an object.

Message:-

· A message is the communication carried between two objects that trigger an event.

STATECHART DIAGRAM

· Models the dynamic behavior of individual classes or any other kind of object.

· Shows the sequences of states, events, and actions.

State:-

· Represents a condition or situation during the life of an object during which it satisfies some condition or waits for some event.

Start State:-

· Shows the beginning of workflow.

End state:-

· Represents the final or terminal state.

ACTIVITY DIAGRAM

· Used for modeling the sequence of activities in a process

· Special case of a state machine in which most of the states are activities and most of the transitions are implicitly triggered by completion of the actions in the source activities.

Activity:-

· Represents the performance of task or duty in a workflow.

Swim lanes:-

· Represents organizational units or roles within a business model.

IMPLEMENTATION DIAGRAM

· Shows the implementation phase of system development.

· Two types of implementation diagrams:

ü Component diagram

ü Deployment diagram

COMPONENT DIAGRAM

· Models the physical components in the design.

· A graph of the design’s components connected by dependency relationships.

· Includes concept of packages.

· Package is used to show how classes are grouped together.

DEPLOYMENT DIAGRAM

· Shows the configuration of runtime processing elements and software components.

· It is a graph of nodes connected by communication association.

· Nodes are the components that are connected to other components through dependencies.

· Used in conjunction with component diagrams to show the distribution of physical modules.

RESULT:-

Thus the different conceptual models under UML have been studied.

Experiment No: 2

SOFTWARE REQUIREMENTS SPECIFICATION FOR ONLINE FLIGHT TICKET RESERVATION SYSTEM

Experiment Date:

SOFTWARE REQUIREMENT SPECIFICATION

AIM

The aim of the experiment is to prepare and document the Software Requirements Specification for the project “Online Flight Ticket Reservation System”

1. INTRODUCTION

1.1 Purpose

1.2 Scope

1.3 Definition, Acronyms, and Abbreviations

1.4 Reference

1.5 Overview

2. Overall Description

2.1 Product Perspective

2.1.1 System Interfaces

2.1.2 User Interfaces

2.1.3 Hardware Interfaces

2.1.4 Software Interfaces

2.1.5 Communication Interfaces

2.1.6 Memory Interfaces

2.1.7 Operations

2.1.8 Site Adaptation Requirements

2.2 Product Functions

2.3 User Characteristics

2.4 Constraints

2.5 Assumptions and Dependencies

3. Specific Requirements

3.1 External Interfaces Requirements

3.1.1 User Interfaces

Flight Details Screen

Passenger Details Screen

Ticket Reservation/Cancellation Screen

3.1.2 Hardware Interfaces

3.1.2 Software Interfaces

3.1.3 Communication Interfaces

3.2 Software Product Features

3.2.1 Flight Details Maintenance

3.2.2 Passenger Details Maintenance

3.2.3 Ticket Reservation Maintenance

3.2.4 Ticket Cancellation Maintenance

3.2.5 Report Generation

3.2.6 User Account Information Maintenance

3.3 Performance Requirements

3.4 Design Constraints

3.5 Software System Attributes

3.6 Logical Database Requirements

3.7 Other Requirements

1. INTRODUCTION

The aim of the document is defining the overall software requirements for Online Flight Ticket Reservation System. The final product will entirely depend on this documentation.

1.1 PURPOSE

• This specific documentation describes the capabilities that will be provided by the software application “Online Flight Ticket Reservation System. It also defines the required constraints of the system and it is useful for development team, testing and end users of the product

1.2 SCOPE:

PROBLEM STATEMENT:

The name of the software is “ONLINE FLIGHT TICKET 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 and it also provides the customers with details of cost of the ticket and allows the customer to modify a particular part of his reservation and he/she can modify all his details.

1.3 DEFINITIONS ACRONYMS AND ABBREVIATION:

i. OFTR- Online Flight Ticket Reservation System

ii. PNR- Passenger Name Record

iii. Round Trip- Both Up and Down trip

iv. One Way Trip- Either Up or Down trip

1.4 REFERENCE:

(i) IEEE Recommended practice for SRS- IEEE Standard 830-1993

(ii) “Object Oriented Analysis and design”

1.5 OVERVIEW:

• The SRS document gives an idea about the requirements and features of the system.

2. OVERALL DESCRIPTION:

The system OFTRS is developed to automate the Online Flight Ticket Reservation in Airlines.

2.1 PRODUCT PERSPECTIVE:

The application will be a window-based, independent software product.

2.1.1 SYSTEM INTERFACE:

• None

2.1.2 USER INTERFACE:

• The following are the screen provided in the application.

· Login Screen

· Flight Details Screen

· Passenger Details Screen

· Ticket Reservation/Cancellation Screen

2.1.3 HARDWARE INTERFACE:

Minimum Requirements of the system are,

Processor- 233 MHZ

Memory- 64 MB

Monitor- Super VGA (800×600) or higher resolution monitor with 256 colors

Hard Disk-5GB

CD RW Drive-52X USB Port

2.1.4 SOFTWARE INTERFACE:

Operating system- Windows 98

Front End Tool -Java

Back End Tool-MYSQL

UML Software- Star UML5.0

2.1.5 COMMUNICATION INTERFACES:

• Not required

2.1.6 MEMORY CONSTRAINTS

Minimum system requirements

Ram-128MB

Hard Disk-4BG

2.1.7 OPERATION

OFTR

· Insert

· Delete

· Update

2.1.8 SITE ADAPTATION REQUIREMENTS

• The stand alone system must able to support the hardware and software interfaces.

2.2 PRODUCT FUNCTIONS

A summary of major functions that the software will perform are

· Flight Details

· Reservation

· Cancellation

2.3 USER CHARACTERISTICS

• Administrator – Can update the database.

• Student- he must know how to operate the software. He must have a technical knowledge to handle the system.

2.4 CONSTRAINTS

• The developed system is meant for standalone system only. So it cannot be used for online management.

2.5 ASSUMPTIONS AND DEPENDENCIES

The book details in the database entirely depend upon the information provided in books that are available in the Library.

OFTRS system works on the assumption that the Student must come to the Library to take or return his/her book of their own interest.

3. SPECIFIC REQUIREMENTS

This section contains the software requirements to a level of detail sufficient to enable designers to design the system and tester to test the system.

3.1 EXTERNAL INTERFACE REQUIREMENTS

3.1.1 USER INTERFACES

• Login Screen:

• Main Menu Screen:

• Book Details Screen:

• Student Details Screen:

• Username: String of the alphabets of length up to 8

• Password: String of Alphabets of Length up to 6

• Role: Two types of role will be there- Administrator and Passenger.

FLIGHT DETAILS SCREEN

• Flight_no: Numeric, 4 Digit No

• Flight_ Name: Alphabetic, Up to a length of 50 characters

• Departure: Alphabetic, up to a length of 50 characters

• Arrival: Alphabetic, up to a length of 50 characters

• Time:

• Cost: Numeric, 9 Digit No

PASSENGER DETAILS SCREEN

TICKET RESERVATION/CANCELLATION SCREEN

3.1.2 HARDWARE INTERFACE

Minimum Requirements of the system are,

Processor- 233 MHZ

Memory-64 MB

Monitor- Super VGA (800×600) or higher resolution monitor with 256 colors

Hard Disk-5GB

3.1.3SOFTWARE INTERFACE:

Operating system- Windows 98

Front End Tool -Java

Back End Tool-MYSQL

UML Software- Star UML5.0

3.1.4 COMMUNICATION INTERFACES

• Not Required

3.2 SOFTWARE PRODUCT FEATURES

Flight Details Maintenance

Passenger Details Maintenance

Reservation Details Maintenance

Cancellation Details Maintenance

Description Validity checks Sequencing information

Error Handling/Response to abnormal situations

3.2.1 FLIGHT DETAILS MAINTENANCE

Description

Validity checks

Sequencing information

Error Handling/Response to abnormal situations

3.2.2 PASSENGER DETAILS MAINTENANCE

Description

Validity checks

Sequencing information

Error Handling/Response to abnormal situations

3.2.3 TICKET RESERVATION MAINTENANCE

Description

Validity checks

Sequencing information

Error Handling/Response to abnormal situations

3.2.4 TICKET CANCELLATION MAINTENANCE

Description

Validity checks

Sequencing information

Error Handling/Response to abnormal situations

3.2.5 REPORT GENERATION

i) Flight details Report

ii) Passenger Details Report

3.3 PERFORMANCE REQUIREMENTS

• None

3.4 DESIGN CONSTRAINTS

• None

3.5 SOFTWARE SYSTEM ATTRIBUTES

· Security

· Usability

3.6 LOGICAL DATABASE REQUIREMENTS

The following information will be placed in the database

· Flight Details

· Passenger Details

· Ticket Reservation /Cancellation Details

3.7 OTHER REQUIREMENTS

• None

RESULT

The Software Requirements Specification for the project” Online Flight Ticket Reservation System” has been analyzed and documented successfully.

Experiment No: 3

DATA DICTIONARY FOR ONLINE FLIGHT TICKET RESERVATION SYSTEM

Experiment Date:

DATA DICTIONARY

AIM:

The aim of the experiment is to prepare a data dictionary of the project OFTR System

DICTIONARY:

Name : Passenger

Alias : None

Where to use &How to use:

Passenger Details

Print ticket

Reservation/cancellation

Context Description:

Passenger Details=Id+Name+Age+Address+Ph.No+

Country+State+Gender

ID=* Any data type integer of length 10*

Name = *any data type string of length 20*

Age =*any data type integer of length 2*

Address=*Any data type varchar of length 50*

Ph. No=*Any data type integer of length 10*

Country = *Any data type string of length 20*

State=*Any data type string of length 20*

Gender=*Any data type string of length 20*

Name : Flight

Alias : None

Where to use &How to use:

Flight Details

Print ticket

Reservation/cancellation

Context Description:

Flight Details=Flightno+name+source+destination+timings+cost

FlightNo=*Any data type integer of length 10*

Name = *any data type string of length 20*

Source=*Any data type varchar of length 50*

Destination = *Any data type string of length 20*

Timings=*Any data type date*

Cost=*Any data type float of length 10*

Name : Ticket information

Alias : None

Where to use &How to use:

Print ticket

Reservation/cancellation

Context Description:

Ticket Information=Passengerno+name+source+destination+timings+cost

ID=* Any data type integer of length 10*

Name = *any data type string of length 20*

Age =*any data type integer of length 2*

FlightNo=*Any data type integer of length 10*

Name = *any data type string of length 20*

Source=*Any data type varchar of length 50*

Destination = *Any data type string of length 20*

Timings=*Any data type date*

Cost=*Any data type float of length 10*

RESULT

The Data dictionary for the project “OFTR System” has been documented successfully.

Experiment No: 4

DATAFLOW DIAGRAM FOR ONLINE FLIGHT TICKET

RESERVATION SYSTEM

Experiment Date:

DATA FLOW DIAGRAM

In order to design a better solution, the DFD for system including all technical processing details is given bellow.

LEVEL 0 DATA FLOW DIAGRAM

REQUEST FOR INFORMATIONFLIGHT/FARE/DISCOUNT

Computer Science & Engineering Software Engineering Lab

Online Flight Ticket Reservation System

PASSENGER

INFORMATION

Computer Science & Engineering Software Engineering Lab

Online Flight Ticket Reservation System

1.0

GENERAL ENQUIRY

BOOKING ENQUIRY

Computer Science & Engineering Software Engineering Lab

Online Flight Ticket Reservation System

NEW PNR INFORMATION

2.0

PASSENGER ENQUIRY

Computer Science & Engineering Software Engineering Lab

Online Flight Ticket Reservation System

Computer Science & Engineering Software Engineering Lab

Online Flight Ticket Reservation System

RESERVATION REQUEST

TICKET CONFIRMATION &STATUS

3.0

BOOKING COUNTER

Computer Science & Engineering Software Engineering Lab

Online Flight Ticket Reservation System

CANCELLATION REQUEST

4.0

CANCELLATION

ACKNOWLEGMENT

Computer Science & Engineering Software Engineering Lab

Online Flight Ticket Reservation System