Sie sind auf Seite 1von 40

CHAPTER - 1

INTRODUCTION
In todays airline industry users or customers can reserve seat or book flight from any
place in the world as long as they are connected to internet. The Innovation of technology has
made traveling in the air easier for customers with airline reservation or booking just a click
away. The fastest means of transportation today is by air. Thousands of people flock the airline
industry this days so that they can arrive their destination within a short period of time. Vehicles,
train e.t.c cannot drive across the Atlantic Ocean or the Pacific Ocean, so customers tend to
travel to other state, countries, and continents using air transportation. Their by with an hours
interval the customers would have arrive their destination. Therefore, if thousands of people use
the aero- planes on a daily basis to travel from one place to another.
Cost Estimation and Scheduling
The most common way of carrying out an economic assessment of software is by
comparing the expected cost of development and operation of the system with the benefits of
having it in place. Software cost is related to human, technical, environment, political and effort
applied to develop it.
There are many software cost estimation techniques available. Here COCOMO model is
used for cost estimation. Computing the development time using intermediate COCOMO model
is done in two stages. The parameter, the length of the product is estimated. Then using this
normal effort is calculated. This project is considered to be essentially straightforward and hence
it comes under organic mode. The normal effort (in person-months) is given by,
Normal Effort = 2.4 (5.5)1.05
= 14 person- months
To calculate the effort estimate, use the effort estimate:
Duration, D = 2.5(14)0.25
= 5.9months

The value for project duration enables the planner to determine a recommended number
of people, N, for the project. When calculating the number of people approximately seventeen
persons are included.
1.

Scheduling
Scheduling is the culmination of a planning activity that is a primary component of

software project management. When combined with estimation methods and risk analysis,
scheduling establishes a road map for the project manager. Scheduling begins with process
decomposition.
The scheduling is done with these functionally. The steps are given below.

Identify the task needed to complete the project.

Determine the dependency among different tasks.

Establish the most likely estimates for the duration of the identified task.

Scheduling is the rudimentary process, which makes the project to be developed in stipulated
time period. By applying the above schedule the project has been developed successfully.

CHAPTER 2
BACKGROUND STUDY
Existing System
In the current flight booking system is a manual one, where the receiver (travel agency)
should receive their booking details and enter into the form if that is made on SMS. In such
systems customers feels very difficult because if they need to book the ticket, they must use
internet and book the flights. And this is very difficult to the travel agency admin too.
Drawbacks

Manual work

More time consuming

not proper booking details

Chances for clerical errors

Storing and retrieving the movie ticket details it is very difficult

Proposed System
In the proposed system, flight ticket booking has done by systematically. The advantage of the
project is, this increases the reliability in flight ticket booking for both users and travel agencies.
Using the proposed system, the user can book their flight ticket via SMS. In the recent trend, the
proposed project of ticketing through non-internet based mobile phones has been developed
using .net platform. This will enable people using non- internet based mobile phones to easily
access ticketing services through SMS.
Advantages

Automatic entry of booking details from SMS.


Easy and reliable.
User doesnt need internet to book flight.
Easy and effective
Reduces the manual work.

Network specification
3

Device specification Architecture: A mobile phone with a built-in GSM modem, or


alternatively a dedicated GSM modem

PC with application
that uses
GSMComm

Mobile
Phone

Mobile
Phone

GSM
Network

Mobile
Phone

Mobile
Phone

Fig: 3.1 Device specifications Architecture Diagram

MODULES
4

1. Customer details registration


2. SMS CHANNEL
a. Receiving SMS
b. Sending SMS
3. Content extraction
4. Ticket blocking

5. Transaction and payment module


6. Reports
1. Customer details registration
The customer details registration module is the initial step of the project. In this module
the user or customer should send their details such as Name and mobile number via Short
message Service (SMS) to the given server number. After receiving the SMS server will extract
and store the customer details in customer table.
2. SMS Channel
SMS channel module is the gateway for sending and receiving SMS. This enables the
communication between user and server. This module performs communication setting in order
to send and receive SMS.
All messages which are sent by the users will be stored in SIM memory and that will be
extracted and stored in to the database. Every message will be stored in memory with a unique
index.
This module is an object of type GSM Communication which is required for sending and
receiving messages. This module helps to set the Communication port, Baud rate and time out
for the Communication object of type GSM communication.
3. Content Extraction
5

The third module implements the content extraction from received SMS. The system
performs the regular expression concept to split the received content. The content from the SMS
should have flight id, name, age and other relevant details in appropriate format.
4. Ticket Blocking
After successful content extraction, the system verifies the availability of tickets and
performs the ticket blocking process. Once the data has been entered in the database, the
confirmation message will send to the users mobile via SMS.
5. Transaction and Payment Module
After ticket booking, the system will send a confirmation message, the user should pay
amount via online. In order to provide optimal booking option, the system provides 5 days time
to pay amount online. With the consideration of security threads, the system avoided the SMS
based payment, so the user should pay amount via online.
6. Reports
Finally the system generates possible reports such as customer details, ticket booking
details and flight information reports.

CHAPTER - 4
SYSTEM REQUIREMENTS
4.1 HARDWARE REQUIREMENTS
6

The most common set of requirements defined by any operating system or software
application is the physical computer resources, also known as hardware, a hardware requirements
list is often accompanied by a hardware compatibility list (HCL). An HCL lists tested,
compatible, and sometimes incompatible hardware devices for a particular operating system or
application.
Processor

Intel Duel core

RAM

2 GB

Hard Disk

90GB

Printer

HP Ink Jet

Keyboard

Samsung

Mouse

Logi Tech (Optical)

4.2 SOFTWARE REQUIREMENTS


It is a complete description of the behavior of a system to be developed and It includes a
set of use cases that describe all the interactions the user will have with the software. In addition
to use cases, the SRS also contains non-functional requirements.
Operating System

Windows XP

Front End

ASP. NET

Coding language

C#. NET

Back End

SQL Server

PROGRAMMING ENVIRONMENT
ABOUT .NET FRAMEWORK
The .net framework is a new computing platform that simplifies application development
in the highly distributed environment of the internet.
OBJECTIVES OF .NET FRAMEWORK:
7

1. To provide a consistent object-oriented programming environment whether object


codes is stored and executed locally on Internet-distributed, or executed remotely.
2. To provide a code-execution environment to minimizes software deployment and
guarantees safe execution of code.
3. Eliminates the performance problems.
There are different types of application, such as Windows-based applications and Websbased applications. To make communication on distributed environment to ensure that
code be accessed by the .Net Framework can integrate with any other code.
COMPONENTS OF .NET FRAMEWORK
THE COMMON LANGUAGE RUNTIME (CLR)
The common language runtime is the foundation of the .NET Framework. It manages
code at execution time, providing important services such as memory management, thread
management, and removing and also ensures more security and robustness. The concept of code
management is a fundamental principle of the runtime. Code that target the runtime is known as
managed code, while code that does not target the runtime is known as unmanaged code.
THE .NET FRAME WORK CLASS LIBRARY
It is a comprehensive; object-oriented collection of reusable types used to develop
applications ranging from traditional command-line or graphical user interface (GUI)
applications based on the latest innovations provided by ASP. NET, such as Web Forms and
XML Webs services.
The . Net Framework can be hosted by unmanaged components that load the common
language runtime into their processes and initiate the execution of managed code, thereby
creating a software environment that can exploit both managed and unmanaged features.
FEATURES OF THE COMMON LANGUAGE RUNTIME
The common language runtime manages memory; thread execution, code execution, code
safety verification, compilation, and other system services these are all run on CLR.

Security.
8

Robustness.
Performance.

SECURITY
The runtime enforces code access security. The security features of the runtime thus
enable legitimate Internet-deployed software to be exceptionally featuring rich.
ROBUSTNESS
The runtime also enforces code robustness by implementing a strict type- and codeverification infrastructure called the Common Type System (CTS). The CTS ensures that all
managed code is self-describing.
PERFORMANCE
The runtime is designed to enhance performance. Although the common language
runtime provides many standard runtime services, managed code is never interpreted. A feature
called just-in-time (JIT) compiling enables all managed code to run in the native machine
language of the system on which it is executing.
ABOUT ASP .NET
ASP.NET is the next version of Active Server Pages (ASP); it is a unified Web
development platform that provides the services necessary for developers to build enterpriseclass Webs applications. While ASP.NET is largely syntax compatible, it also provides a new
programming model and infrastructure for more secure, scalable, and stable applications.
ASP.NET is a compiled, NET-based environment; user can author applications in any .NET
compatible language, including Visual Basic .NET, C#, and JScript .NET.
Additionally, the entire.NET Framework is available to any ASP. NET application.
Developers can easily access the benefits of these technologies, which include the managed
common language runtime environment (CLR), type safety, inheritance, and so on. ASP. NET
has been designed to work seamlessly with WYSIWYG HTML editors and other programming
tools, including Microsoft Visual Studio.NET.
9

Developers can choose from the following two features when creating an ASP. NET
application. Webs Forms and Webs services, or combine these in any way they see fit. Each is
supported by the same infrastructure that allows using authentication schemes; cache frequently
used data, or customizes your application's configuration, to name only a few possibilities. ASP.
NET provides a simple model that enables Webs developers to write logic that runs at the
application level. Developers can write this code in the global.aspx text file or in a compiled
class deployed as an assembly.
This logic can include application-level events, but developers can easily extend this
model to suit the needs of their Web application.ASP. NET provides easy-to-use application and
session-state facilities that are familiar to ASP developers and are readily compatible with all
other . NET Framework APIs. ASP.NET offers the IHttpHandler and IHttpModule interfaces.
ASP. NET takes advantage of performance enhancements found in the .NET Framework
and common language runtime. Additionally, it has been designed to offer significant
performance improvements over ASP and other Web development platforms. All ASP.NET code
is compiled, rather than interpreted, which allows early binding, strong typing, and just-in-time
(JIT) compilation to native code, to name only a few of its benefits. ASP.NET is also easily
factorable, meaning that developers can remove modules (a session module, for instance) that are
not relevant to the application they are developing.
Web Forms allows us to build powerful forms-based Web pages. When building these
pages that use ASP. NET server controls to create common UI elements, and program them for
common tasks. These controls allow to rapidly building a Web Form out of reusable built-in or
custom components, simplifying the code of a page. An XML Web service provides the means
to access server functionality remotely. Using Web services, businesses can expose
programmatic interfaces to their data or business logic, which in turn can be obtained and
manipulated by client and server applications.
ASP. NET provides extensive caching services (both built-in services and caching APIs).
ASP. NET also ships with performance counters that developers and system administrators can
monitor to test new applications and gather metrics on existing applications. ASP.NET is a
server-side technology. That is, it runs on the web server. Most web designers cut their teeth
10

learning client-side technologies such as HTML, JavaScript, and Cascading Style Sheets (CSS).
When a web browser requests a web page created with only client-side technologies, the web
server simply grabs the files that the browser (or client) requests and sends them down the line.
The client is entirely responsible for reading the markup in those files and interpreting that
markup to display the page on the screen.
C#.NET

C# language is intended to be a simple, modern, general-purpose, object-oriented


programming language.

The language, and implementations are used to provide support for software
engineering principles such as strong type checking, array bounds checking,
detection of attempts to use uninitialized variables, and automatic garbage
collection. Software robustness, durability, and programmer productivity are
important.

The language is intended for use in developing software components suitable for
deployment in distributed environments.

Source code portability is very important, as is programmer portability, especially


for those programmers already familiar with C and C++.

Support for internationalization is very important.

FEATURES

There are no global variables or functions. All methods and members must be
declared within classes. Static members of public classes can substitute for global
variables and functions.

11

Local variables cannot shadow variables of the enclosing block, unlike C and C+
+. Variable shadowing is often considered confusing by C++ texts.

In addition to the try...catch construct to handle exceptions, C# has a try...finally


construct to guarantee execution of the code in the finally block.

Multiple inheritances are not supported, although a class can implement any
number of interfaces. This was a design decision by the language's lead architect
to avoid complication and simplify architectural requirements throughout CLI.

Enumeration members are placed in their own scope.

Full type reflection and discovery is available.

C# currently has 77 reserved words.

DATA ACCESS WITH ADO.NET


As develop applications using ADO. NET, have different requirements for working with
data. Never need to directly edit an XML file containing data - but it is very useful to understand
the data architecture in ADO.NET.
ADO. NET offers several advantages over previous versions of ADO:

Interoperability
Maintainability
Programmability
Performance Scalability

INTEROPERABILITY

12

ADO.NET applications can take advantage of the flexibility and broad acceptance of
XML. Because XML is the format for transmitting datasets across the network, any component
that can read the XML format can process data. The receiving component need not be an ADO.
NET component.
MAINTAINABILITY
In the life of a deployed system, modest changes are possible, but substantial,
Architectural changes are rarely attempted because they are so difficult. As the performance load
on a deployed application server grows, system resources can become scarce and response time
or throughput can suffer.
PERFORMANCE
ADO. NET datasets offer performance advantages over ADO disconnected record sets. In
ADO.NET data-type conversion is not necessary.
SCALABILITY
ADO.NET accommodates scalability by encouraging programmers to conserve limited
resources. Any ADO. NET application employs disconnected access to data; it does not retain
database locks or active database connections for long durations.
XML WEB SERVICES
XML web services are applications that can receive the requested data using XML over
HTTP. XML web services are not tied to a particular component technology or object-calling
convention but it can be accessed by any language, component model, or operating system. In
Visual Studio . NET, user can quickly create and include XML web services using Visual Basic,
Visual C#, JScript, Managed Extensions for C++, or ATL Server.

SOAP
13

SOAP originally defined as Simple Object Access Protocol, is a protocol specification


for exchanging structured information in the implementation of Web Services in computer
networks. It relies on Extensible Markup Language (XML) for its message format, and usually
relies on other Application Layer protocols, most notably Hypertext Transfer Protocol (HTTP)
and Simple Mail Transfer Protocol (SMTP), for message negotiation and transmission.
CONSTRUCTORS AND DESTRUCTORS
Constructors are used to initialize objects, whereas destructors are used to destroy them.
In other words, destructors are used to release the resources allocated to the object. In C#. NET
the sub finalize procedure is available. The sub finalize procedure is used to complete the tasks
that must be performed when an object is destroyed. The sub finalize procedure is called
automatically when an object is destroyed. In addition, the sub finalize procedure can be called
only from the class it belongs to or from derived classes.
WSDL
The Web Services Description Language is an XML-based language that is used for
describing the functionality offered by a Web service. A WSDL description of a web service
provides a machine-readable description of how the service can be called, what parameters it
expects, and what data structures it returns. It thus serves a roughly similar purpose as a method
signature in a programming language.
GARBAGE COLLECTION
Garbage Collection is another new feature in C#. NET. The . NET Framework monitors
allocated resources, such as objects and variables. In addition, the . NET Framework
automatically releases memory for reuse by destroying objects that are no longer in use. In C#.
NET, the garbage collector checks for the objects that are not currently in use by applications.
When the garbage collector comes across an object that is marked for garbage collection, it
releases the memory occupied by the object.
UDDI

14

Universal Description, Discovery and Integration (UDDI) is a platform-independent,


Extensible Markup Language (XML)-based registry for businesses worldwide to list themselves
on the Internet and a mechanism to register and locate web service applications. UDDI was
originally proposed as a core Web service standard. It is designed to be interrogated by SOAP
messages and to provide access to Web Services Description Language (WSDL) documents
describing the protocol bindings and message formats required to interact with the web services
listed in its directory.
MULTITHREADING
C# . NET also supports multithreading. An application that supports multithreading can
handle multiple tasks simultaneously, user can use multithreading to decrease the time taken by
an application to respond to user interaction. To decrease the time taken by an application to
respond to user interaction, User must ensure that a separate thread in the application handles
user interaction.
ABOUT SQL-SERVER 2005
The OLAP Services feature available in SQL Server version 7.0 is now called SQL
Server 2005Analysis Services. The term OLAP Services has been replaced with the term
Analysis Services. Analysis Services also includes a new data mining component. The
Repository component available in SQL Server version 7.0 is now called Microsoft SQL Server
2000 Meta Data Services. References to the component now use the term Meta Data Services.
The term repository is used only in reference to the repository engine within Meta Data Services
SQL-SERVER 2005 database consist of six type of objects,
They are,
1. TABLE
2. QUERY
3. FORM
4. REPORT
5. MACRO
1. TABLE

15

A database is a collection of data about a specific topic. In relational database data


are stored in the form of table. It can consist of rows and columns.
VIEWS OF TABLE
The project work with a table consist of two types,
Design View
To build or modify the structure of a table user work in the table design. User
can specify what kind of data will be hold. Use Design view to arrange report items in the
report. Design view is sometimes called the design surface or layout view.
Datasheet View
Datasheet view shows the data in the database. It also allows us to enter and edit the
data. Design view allows us to create or change the table, form, or other database object,
and configure the fields.
2. QUERY
A query is a question that has to be asked the data. Access gathers data that
assurers the question from one or more table. The data that make up the answer is either
dynasts or a snapshot. .Each time user run query, and get latest information in the dynasts
.Access either displays the dynast or snapshot for us to view or perform an action on it
,such as deleting or updating.
3. FORMS
A form is used to view and edit information in the database record by record .A
form displays only the information user wants to see. Forms use the familiar controls
such as textboxes and checkboxes. This makes viewing and entering data easy. Work
with forms in several primarily there are two views are,

Design View
16

To build or modify the structure of a form, user work in forms design view. User
can add control to the form that are bound to fields in a table or query, includes textboxes,
option buttons, graphs and pictures.
Form View
The form view which displays the whole design of the form.
4. REPORT
A report is used to vies and print information from the database. The report can
ground records into many levels and compute totals and average by checking values from
many records at once. Also the report is attractive and distinctive because user has control
over the size and appearance of it.
5. MACRO
A macro is a set of actions. Each action in macros does something. Such as
opening a form or printing a report .Web write macros to automate the common tasks the
work easy and save the time.

17

CHAPTER 5
Feasibility Study
A system is a feasible system only if it is feasible within limited recourse and time. In this
system each and every process can be feasible for the user and also developer. It proved user
friendly input such as device independent inputs and getting proper solution for the problem.
The different types of feasible system that have to analyze are,

Technical Feasibility

Behavioral Feasibility

Economical Feasibility

Operational Feasibility

5.1.1. Technical Feasibility


Technical Feasibility is the assessment of the technical view of the system. The system is
developed for . net environment; a platform independent tool is used to develop the system.
The consideration those are normally associated with the technical feasibility include the
following
Development risk
Resource availability
Technology
The development risk concerns the probability, the function of all elements and its performance
should be same in all platforms and in the system that is being developed. This system is
developed according to the standards and the development software tools are selected in such a
way to avoid the problems cited above.

18

The software used to develop this system is Windows XP, visual studio. Net is done efficiently,
and the concept of SQL helps to create the application backend. These components are also
helpful in providing interactivity to Java applications.
5.1.2. Behavioral Feasibility
It is common knowledge that computers illustrations have something to do with turnover
transfers, retraining and changes in user or developer status. The main emphasis is customer
service, personal contacts with customers.
Feasibility report is directed towards management. It evaluates the impact of the
proposed changes on the area in question. The report is a formal document for management use,
brief enough and sufficiently non-technical to be understood.
5.1.3.Economical Feasibility
Economic feasibility or cost benefit is an assessment of the economic justification for a
computer based system project. Though this system the administrator can use the tool from
anywhere within their concern. The system is developed using the existing resources. So the
project is economically feasible.
This is the most frequently used method for evaluating the effectiveness of a user system.
More commonly, know as cost analysis the procedure is to determine the benefits and savings
that are expected from a candidate system and compare them with costs.
This system getting hundreds present economical feasibility. It will be achieved goal very
efficiently. And evolution of development cost (hardware and software needed) is weighted
against the ultimate income or benefit derived from the system. Finally, it is assured that this
project is economically feasible

19

5.1.4. Operational Feasibility


Operational Feasibility deals with the study of prospects of the system. This system
operationally eliminates all the tensions of the administrator and helps in effectively tracking the
project progress. This kind of automation will surely reduce the time and energy, which
previously consumed in manual work. Based on the study, the system proved to be operationally
feasible.
5.2. OUTPUT DESIGN
Output design generally refers to the results and information that are generated by the
system. For many end-users, output is the main reason for developing the system and the basis
on which they evaluate the usefulness of application.

The objective of a system finds its

shape in terms of the output. The analysis of the objective of a system leads to determination of
outputs. Outputs of a system can take various forms. The most common are reports, screens
displays, printed form, graphical drawing etc. the output also vary in terms of their contents,
frequency, timing and format.
The important and very useful outputs by the project are as follows
The flight ticket portal contains two type of outputs, one is system based another one is mobile
SMS. The user will get confirmation messages via SMS.
5.3 INPUT DESIGN
Input design is the process of converting user-originated inputs to a computer-based
format input data are collected and organized into group of similar data. Once identified,
appropriate input media are selected for processing.. Input design must be in such a way that it
must controlled the amount of input, avoid delay etc., it must be simple. The input design must
ensure user-friendly screens, with simplicity, providing ease of viewing and entering the data.

The main objective of designing input focus on


20

Controlling the amount of input required.

Avoiding delayed response

Controlling errors

Keeping process simple

Avoiding errors
The input design should contain the detailed information in which every user can

Understand the type of data they are going to enter or view .So this is very important in design .If
this fails then the user enter the data incorrectly which leads to many errors. The user should not
be able to view or edit the codes that are created. So that features should be disabling to users
while they are working on the package.
The project has been designed using visualstudio.net environment. The predefined
controls have used in the design environment. The forms include textbox, and combo box
controls to get inputs.

LOGIN FORM

This is the first form which contains user login, administrators login. The user or
administrator can enter the valid user name and password.

NEW USER registration

The new user can enter the details like fname, lname, Email Id, Phone Number along with
their account details,etc and registered.
5.4 CODE DESIGN
The code design should be such that with less amount of coding This system can achieve
more results. The speed of the system will be more if the coding is less. Whether the data in the
system is usable and readable by the system is depending on the coding.

21

In the project, the coding is being done such that proper validations are made to get the
perfect input. No error inputs are accepted. In addition care is taken such that the data integrity
and referential integrity is not violated in the database.
In addition, coding is designed such that concurrency avoidance of accessing the
database, limited user access to the table is made perfect.
DATABASE DESIGN
The database design is a must for any application developed especially more for the data
store projects. Since the chatting method involves storing the message in the table and produced
to the sender and receiver, proper handling of the table is a must.
Tables
5.5.1

Customer table

Column name

Data Type

Description

Customer_id

Numeric(10,0)

Id of the customer

Customer_name

Nvarchar(20)

Name of the customer

Mobile_number

Numeric(10,0)

Customer Mobile number

Age

Numeric(2,0)

Age of the customer

Gender

Nvarchar(6)

Gender of the customer

Emaild

Nvarchar(MAX)

Email id of the customer

5.5.2

Ticket blocking table:

22

Column name

Data Type

Description

Ticket_id

Nvarchar(20)

Flight ticket Id

Customer_id

Numeric (10,0)

Customer id

Flight_id

Nvarchar (10)

Flight id

Booking_date

datetime

Date of booking

Source

Nvarchar(30)

Starting place

Destination

Nvarchar (30)

Stopping place

Adult

Numeric (2,0)

Number of adults

Child

Numeric (2,0)

Number of children

Infants

Numeric (2,0)

Number of infants

F_class

Nvarchar(20)

First class

Received_date

datetime

Ticket receiving date

5.5.3

Booking and payment table

Column name

Data Type

23

Description

Booking_id

Nvarchar(20)

Id of the customer

ticket_id

Nvarchar(20)

Name of the customer

Customer_id

Numeric(10,0)

Customer Mobile number

Flight_id

Nvarchar(20)

Age of the customer

Booking_date

datetime

Gender of the customer

Amount

Numeric (MAX)

Email id of the customer

Payment_date

datetime

Date of payment done

Numeric field validation:

The mobile number field can contain only numbers that should be 10 number.

The individual modules are checked for accuracy and what it has to perform

Text field validation:

The text field can contain only the number of characters lesser than or equal to its size.

The text fields are alphanumeric in some tables and alphabetic in other tables. Incorrect
entry always flashes an error message.

24

APPENDICES
A. CONTEXT FLOW DIAGRAM ( flight ticket portal )

Send SMS to the


user

User details

User
registration

Compose
SMS

Flight
ticket
portal

Sends to the
server

Instruction SMS
Ticket
blocking

Ticket
booking

Payment details

Online
payment

Fig: A. Context Flow Diagram

25

Ticket blocking

Booking
confirmation

B. Data Flow Diagram


Level-0

Customer
Details
Customer

Online
Registr
ation

Store

Retrieve

Instruction
SMS

Fig: B.1 Level 0 Data Flow Diagram

26

Customer
table

Level-1

SMS
Customer

Send
SMS to
server

Store

Retrieve

Ticket
blocking
table

Open website
Check availability

Online
payment

Retrieve
Extracts customer
details
Ticket
blockin
g
process

And check payment


Books ticket
Store

Bookin_pay
ment table

Fig: B.2 Data Flow Diagram

27

Level2

User

Compose a message
with

Send SMS to the


server number

Name, phone number

Sends an instruction message to the


users
Such as the order of message
content

Split and
Store user
details into
the
database
Customer table

Compose a message
with

Air ticket booking process


begins

Source, destination,
number of passengers,
date, flight no etc,

Send SMS to the


server number

Booking confirmation
message

Pay online

SMS Server
will receive
and split the
content

Booking table

28

Payment table

Fig: B. 3Data Flow Diagram

ERD:

Cust
name

Age
Cust_id

Phone
no
Email

Cust_id

Ticket_i
d

Cus
tom
er_i
d

Customer

Flight_
id

Ticket_blocki
ng
1-m
1-m

Tic
ket
_id

Booking and
payment
Bookin
g_id
Flight_i
d

Ticket_i
d
Cust_id

Date

Amou
nt

Fig: C.1 Entity relationship Diagram

29

Sourc
e
Destin
ation
others

CHAPTER VI
DEVELOPMENT OF SYSTEM TESTING
6.1 System Testing
System testing is a type of testing to confirm that all code modules work as specified, and
that the system as a whole performs adequately on the platform on which it will be deployed.
System testing should be performed by testers who are trained to plan, execute, and report on
application and system code. They should be aware of scenarios that might not occur to the end
user, like testing for null, negative, and format inconsistent values.
System testing of software or hardware is testing conducted on a complete, integrated
system to evaluate the system's compliance with its specified requirements. A tester should be
able to repeat the steps that caused an error. Test techniques include, but are not limited to, the
process of executing a program or application with the intent of finding software bugs.
6.2 Testing and Methodologies
This system begins the testing process by developing a comprehensive plan to test the
general functionality and special features on a variety of platform combinations. Strict quality
control procedures are used. The process verifies that the application meets the requirements
specified in the system requirements document and is bug free.
At the end of each testing day, this system prepares a summary of completed and failed
test. And the application is redeveloped and retested until every item is resolved. All changes and
retesting are tracked through spreadsheets. Applications are not allowed to launch until all
identification problem are fixed. Finally a report is prepared at the end of testing to show exactly
what was tested and to list the final outcomes. This software testing methodology is applied in
four distinct phases:

Unit testing

Integration testing

30

6.2.1 Unit Testing


Unit testing is designed to test small pieces of functionality rather than the system
as a whole. This allows us to conduct the first round of testing to eliminate bugs before the other
major tests (i.e.) each module is tested individually. Unit testing is testing changes made in a
existing or new program to find out each module is found to be working satisfactorily. Here
every module will be tested.
Registration and Login module test
Component test-whether the SMS device is working or not
6.2.2 Integration Testing
Integration testing is a type of testing in which software and/or hardware
components are combined and tested to confirm that they interact according to their
requirements. Integration testing can continue progressively until the entire system has been
integrated.
It is also a software testing methodology used to test individual software
components or units of code to verify interaction between various software components and
detect interface defects. Components are tested as a single group or organized in an iterative
manner. After the integration testing has been performed on the components, they are readily
available for system testing. The following are the types of integration testing:

Top down Integration

Bottom-up Integration

6.2.3 Validation Testing


Test to determine whether an implemented system fulfills its requirements such as
checking of data for correctness or for compliance with applicable standards, rules, and
conventions. Validation testing is used to validate the fields in the form. It mainly focuses on text
field and numeric field.

31

6.3 QUALITY ASSURANCE


This system believed that testing should occur throughout the development process. This
system tested this software against the specifications in the system requirement document using
the scenarios developed earlier in the project.
Testing is applied in four distinct phasesunit testing, integration testing, system testing,
acceptance testing. During the system test this system designs and develops test cases to verify
that system requirements have been implemented and software works correctly. By this, This
system achieve better objectivity in the quality of the product.

CHAPTER - 7
SYSTEM IMPLEMENTATION
7.1 User Training
This system was developed very user friendly. No extra training was requiring using this
system. This system automatically guides (fully user guided) the user to give input and to
produce the output.
7.2 Operational Documentation
An online help which gives the clear idea about This system was attached with This
system. Whenever the user needs guidance he can get help from the help manual.

Once the implementation plan is decided, it is essential that the user of the system is
made familiar and comfortable with the environment.

A documentation providing the whole operations of the system is being developed

The user can work with it in a well consistent way

The system is developed user friendly so that the user can work the system from the tips
given in the application itself.
CHAPTER - 8
32

CONCLUSION
There are several reasons for transport authorities for introducing electronic ticketing
systems. However, they do not have the same priorities to all of them. Hereafter a list of
expectations compiled from the study:
Prevention of fraud
Fare flexibility
Improved multi-modal and multi-operator integration especially where method of operation
requires accurate allocation of fares to private operators.
Improved passenger convenience and ease of use
Efficiency savings
E-ticketing is an alternative to the conventional way of proving the availability and
validity of travel permission (e.g. paper tickets) through transferring the necessary information to
an electronic medium.
Electronic ticketing is a ticket sales information system, which are a tool and a basis for
improvement of ticket sales and payment. In addition with access control and ticket sales
management (reporting, accounting etc), it helps institutions cultural, tourism, sport and all other
institutions to browse transactions, to get know their customers and to increase their revenues.
Flight ticket portal has been developed by using Asp.net, because this will be the
advanced and easy to use the client / server technology so developed this project in .Net. Using
this project the user can book their tickets using SMS.
Overall the system is to be fairly usable. The conclusions that are derived from the
different usability areas are as follows: the project provides a reliable and easy way to book
tickets using mobile phones using SMS.
The system is found to be professional by the users because of the standardized layout
and familiar navigation.

CHAPTER - 9
FUTURE SCOPE AND FURTHER ENHANCEMENT OF THE PROJECT
33

The project Flight ticket portal is flexible enough to meet the requirements of the Customers.
This project also has the scope of enhancements like:
1- Home delivery of tickets may be provided.
2- Online Booking of Purchases of eatables (coldrinks, popcorn etc) can be provided.
3- Corporate booking: Multimedia support for corporate presentation can be provided.
Conference facility can be provided for corporate meetings in the hall. This will increase
the profit of cinema halls as well as the company organizing event.
4- Group booking: Any institute/company can book the tickets for students/clients and
special discount will be provided to them.

34

CHAPTER 10
BIBLIOGRAPHY
Books Referred
[1]
Introduction
By Gary J. Bronson

to

Programming

with

Visual

Basic

[2] Alex Homer , Professional C#.NET 1.1, 2004 Edition, Wrox Publications
[3] Clayton crooks II Learning .Net Through Applications
[4] Roger S Pressman, Software Engineering, 2000 Edition, Dreamtech Publications
[5] Steven Holzner, .NET Black Book, 2003 Edition, Dreamtech Publications
Websites
[6] www.msdn.microsoft.com
[7] www.vbcity.com
[8] www.vb.netheaven.com
[9] www.codeproject.com
[10] www.netjohn.com
[11] http://www.dreamincode.net
[12] http://www.a1vbcode.com

35

.NET

SCREENS:
Signup Page:

36

Login page:

37

Admin login:

38

SMS Kit Connection Settings Screen:

39

Das könnte Ihnen auch gefallen