Bus Reservation System Final Report

CHAPTER 1
INTRODUCTION
1.1 MOTIVATION AND OBJECTIVE
The main objective of this project is to provide the better work efficiency,
security, accuracy, reliability, feasibility. The error occurred could be reduced to nil
and working conditions can be improved and also provide following features:
Online Bus Ticket Booking Facility and Cancellation Facility.
Enhance of the security level in centralized system.
Register New Agent.
View Details of Agent, Bus Information, User Feedback
Different Payment Mode: Cash Card, Credit Card Etc.
1 E-HealthCare
CHAPTER 2
PROBLEM DEFINITION AND REQUIREMENT ANALYSIS
2.1 IDENTIFICATION OF NEED
The main objective of this project is to provide the better work efficiency, security, accuracy,
reliability, feasibility. The error occurred could be reduced to nil and working conditions can
be improved and also provide following features:
Online Bus Ticket Booking Facility and Cancellation Facility.
Enhance of the security level in centralized system.
Register New Agent.
View Details of Agent, Bus Information, User Feedback
Different Payment Mode: Cash Card, Credit Card Etc.
2.2 FEASIBILITY STUDY
A feasibility study is an evaluation and analysis of the potential of the proposed project
which is based on extensive investigation and research to give full comfort to the decisions
makers. Feasibility studies aim to objectively and rationally uncover the strengths and
weaknesses of an existing business or proposed venture, opportunities and threats as
presented by the environment, the resources required to carry through, and ultimately the
prospects for success. In its simplest terms, the two criteria to judge feasibility
are cost required and value to be attained.
As such, a well-designed feasibility study should provide a historical background of the

business or project, description of the product or service, accounting statements, details of
the operations and management, marketing research and policies, financial data, legal
requirements and tax obligations. Generally, feasibility studies precede technical
development and project implementation.
2 Bus Reservation System

2.2.1 TECHNOLOGY AND SYSTEM FEASIBILITY
The assessment is based on an outline design of system requirements, to determine whether

the company has the technical expertise to handle completion of the project. When writing a
feasibility report, the following should be taken to consideration:
A brief description of the business to assess more possible factor/s which could affect
the study
The part of the business being examined
The human and economic factor
The possible solutions to the problems
At this level, the concern is whether the proposal is both technically and legally feasible
(assuming moderate cost).
2.2.2 OPERATIONAL FEASIBILITY
Operational feasibility is a measure of how well a proposed system solves the problems, and
takes advantage of the opportunities identified during scope definition and how it satisfies the
requirements identified in the requirements analysis phase of system development.
The operational feasibility assessment focuses on the degree to which the proposed
development projects fits in with the existing business environment and objectives with
regard to development schedule, delivery date, corporate culture, and existing business
processes.

2.2.3 ECONOMIC FEASIBILITY
The purpose of the economic feasibility assessment is to determine the positive economic
benefits to the organization that the proposed system will provide. It includes quantification
and identification of all the benefits expected. This assessment typically involves a cost/
benefits analysis.
2.2.4 TECHNICAL FEASIBILITY
The technical feasibility assessment is focused on gaining an understanding of the present

technical resources of the organization and their applicability to the expected needs of the
proposed system. It is an evaluation of the hardware and software and how it meets the need
of the proposed system.
2.2.5 FINANCIAL FEASIBILITY
In case of a new project, financial viability can be judged on the following parameters:
Total estimated cost of the project.

Financing of the project in terms of its capital structure, debt equity ratio and
promoter's share of total cost.
Existing investment by the promoter in any other business
Projected cash flow and profitability.
The financial viability of a project should provide the following information.

Full details of the assets to be financed and how liquid those assets are.
Rate of conversion to cash-liquidity (i.e. how easily can the various assets be
converted to cash?).
Project's funding potential and repayment terms.
Sensitivity in the repayments capability to the following factors:
o Time delays.
o Mild slowing of sales.
o Acute reduction/slowing of sales.
o Small increase in cost.
o Large increase in cost.
o Adverse economic conditions.

2.3 PROJECT PLANNING
The concept is further developed to describe how the business will operate once the
approved system is implemented, and to assess how the system will impact the administrator
and user privacy. To ensure the products and /or services provide the required capability on-
time and within budget, project resources, activities, schedules, tools, and reviews are
defined. Additionally, security certification and accreditation activities begin with the
identification of system security requirements and the completion of a high level vulnerability
assessment.
PROJECT MANAGEMENT ACTIVITIES
PROJECT PLANNING
Establishing objectives.
Defining project.
Creating work breakdown Structure.
Determining resources
These task defining following .
PROJECT ORGANIZATION WORKS BEST WHEN

Works can be defined with a specific goal deadlines
The job is unique and somewhat unfamiliar to the existing organization.
The work contains complex interrelated tasks requiring specialized skills.
The project is temporary but critical to organization.
Often temporary structure.

Uses specialist from entire company .
Headed by project manager
Monitor schedule & costs.
Permanent structure called matrix organization.
WORK BREAKDOWN STRUCTURE
project
Major tasks in project.
Subtasks in major tasks.
Activities.

2.4 DATA FLOW DIAGRAM (DFD)
The Data Flow Diagram (DFD) is the graphical representation of the processes
and the flow of data among them. A data flow diagram illustrates the processes, data
stores, external entities and the connecting data flows in a system. The following
figure is an example of a typical DFD.
Figure: 2.1 Example of a Data Flow diagram
There are four components for a Data Flow Diagram. They are
External Entities/ Terminators are outside of the system being modeled.
They represent where information comes from and where it goes. These
are represented by rectangles.

Processes, usually represented by an ellipse (circle), which modify the
Input to generate the output.
Data Stores represents a place in the process where data rests. This is
represented by an open-ended rectangles or a cylinder symbol.
Data Flows, represented by arrows, are how data moves between
Terminators, processes, and data stores.

DATA FLOW DIAGRAM (DFD)
Login into
Passenger
Book Ticket Bus

Reservation
Ticket
System
Details Bus
Agency/
Online
Store in
Verify passenger
Report
Information
Report
Customer A\C
Passenger Information
Information
Table
Passenger
can submit feed back

Feedback Table

2.5 ENTITY RELATIONSHIP DIAGRAM
An Entity Relationship Diagram (ERD) gives a graphical representation of the

tables (entities) in the database and the relation between them.
Entity
An aggregation of a number of data elements.
Each data element is an attribute of the entity.
Entity type
a class of entities with the same attributes
Relationship
An association between two or more entities that is of particular interest.
ERD Development Process:
Identify the entities
Determine the attributes for each entity
Select the primary key for each entity
Establish the relationships between the entities
Draw an entity model
Test the relationships and the keys

ER MODEL FEATURES TO DESCRIBE DATA
Physical Entity Set
Attributes
Specialization
Generalization
Relationship
Single Line Connection Between
Entity and Relationship
Relationship

2.6 USE CASE DIAGRAM
A use case diagram at its simplest is a representation of a user's interaction with the
system and depicting the specifications of a use case. A use case diagram can portray the
different types of users of a system and the various ways that they interact with the system.
This type of diagram is typically used in conjunction with the textual use case and will often
be accompanied by other types of diagrams as well.
2.6.1 USE CASE FOR PASSANGER
Find Site or agency for

ticket booking
PASSANGE Apply for the ticket

R
Automatic search will

define that ticket is
available or not Map
Final Print of Ticket

Confirmation

2.6.2 USE CASE FOR AGENT
Take inputs from customer
AGENT
Check the ticket mode
If ticket is not booked he

book a new ticket or he can
also cancel booked ticket
Forward a message to
customers mob no.

2.7 FLOW DIAGRAM
Flow Diagram for bus reservation system

3. PLATFORM/TECHNOLOGY IN PROJECT
3.1 Front-end Environment (.NET Framework)
The Internet revolution of the late 1990s represented a dramatic shift in the way individuals
and organizations communicate with each other. Traditional applications, such as word
processors and accounting packages, are modeled as stand-alone applications: they offer
users the capability to perform tasks using data stored on the system the application resides
and executes on. Most new software, in contrast, is modeled based on a distributed
computing model where applications collaborate to provide services and expose functionality
to each other. As a result, primary role of most new software is changing into supporting
information exchange (through Web servers and browsers), collaboration (through e-mail and
instant messaging), and individual expression (through Web logs, also known as Blogs, and
e-zines Web based magazines). Essentially, the basic role of software is changing from
providing discrete functionality to providing services.
The .NET Framework represents a unified, object-oriented set of services and libraries that
embrace the changing role of new network-centric and networkaware software. In fact, the
.NET Framework is the first platform designed from the ground up with the Internet in mind.
Microsoft .NET Framework is a software component that is a part of several Microsoft

Windows operating systems. It has a large library of pre-coded solutions to common
programming problems and manages the execution of programs written specifically for the
framework. The .NET Framework is a key Microsoft offering and is intended to be used by
most new applications created for the Windows platform.

Benefits of the .NET Framework
The .NET Framework offers a number of benefits to developers:

A consistent programming model
Direct support for security
Simplified development efforts
Easy application deployment and maintenance
The .NET Class Library is a key component of the .NET Framework it is sometimes
referred to as the Base Class Library (BCL). The .NET Class Library contains hundreds of
classes you can use for tasks such as the following:
Processing XML
Working with data from multiple data sources
Debugging your code and working with event logs
Working with data streams and files
Managing the run-time environment
Developing Web services, components, and standard Windows applications
Working with application security
Working with directory services
The functionality that the .NET Class Library provides is available to all .NET languages,
resulting in a consistent object model regardless of the programming language developers
use.
Performance
ASP.NET aims for performance benefits over other script-based technologies (including
Classic ASP) by compiling the server-side code to one or more DLL files on the web server.
This compilation happens automatically the first time a page is requested (which means the
developer need not perform a separate compilation step for pages). This feature provides the
ease of development offered by scripting languages with the performance benefits of a
compiled binary.

However, the compilation might cause a noticeable but short delay to the web user when the
newly-edited page is first requested from the web server, but won't again unless the page
requested is updated further. The ASPX and other resource files are placed in a virtual host on
an Internet Information Services server (or other compatible ASP.NET servers; see Other
Implementations, below). The first time a client requests a page, the .NET framework parses
and compiles the file(s) into a .NET assembly and sends the response; subsequent requests
are served from the DLL files. By default ASP.NET will compile the entire site in batches of
1000 files upon first request. If the compilation delay is causing problems, the batch size or
the compilation strategy may be tweaked. Developers can also choose to pre-compile their
code before deployment, eliminating the
need for just-in-time compilation in a production environment
3.2 Back-end Environment (Ms Access)
Microsoft Access, also known as Microsoft Office Access, is a database

management system from Microsoft that combines the relational Microsoft Jet Database
Engine with a graphical user interface and software-development tools. It is a member of
the Microsoft Office suite of applications, included in the Professional and higher editions or
sold separately.
Microsoft Access stores data in its own format based on the Access Jet Database Engine. It
can also import or link directly to data stored in other applications and databases.[1]
Software developers and data architects can use Microsoft Access to develop application
software, and "power users" can use it to build software applications. Like other Office
applications, Access is supported by Visual Basic for Applications, an object-
oriented programming language that can reference a variety of objects including DAO (Data
Access Objects), ActiveX Data Objects, and many other ActiveX components. Visual objects
used in forms and reports expose their methods and properties in the VBA programming
environment, and VBA code modules may declare and call Windows operating-
system functions.

Features
Users can create tables, queries, forms and reports, and connect them together with macros.
Advanced users can use VBA to write rich solutions with advanced data manipulation and
user control. Access also has report creation features that can work with any data source that
Access can "access".
The original concept of Access was for end users to be able to "access" data from any source.
Other features include: the import and export of data to many formats
including Excel, Outlook, ASCII, dBase, Paradox, FoxPro, SQL Server, Oracle, ODBC, etc.
It also has the ability to link to data in its existing location and use it for viewing, querying,
editing, and reporting. This allows the existing data to change while ensuring that Access uses
the latest data. It can perform heterogeneous joins between data sets stored across different
platforms. Access is often used by people downloading data from enterprise level
databases for manipulation, analysis, and reporting locally.
There is also the Jet Database format (MDB or ACCDB in Access 2007) which can contain
the application and data in one file. This makes it very convenient to distribute the entire
application to another user, who can run it in disconnected environments.
One of the benefits of Access from a programmer's perspective is its relative compatibility
with SQL (structured query language) queries can be viewed graphically or edited as SQL
statements, and SQL statements can be used directly in Macros and VBA Modules to
manipulate Access tables. Users can mix and use both VBA and "Macros" for programming
forms and logic and offers object-oriented possibilities. VBA can also be included in queries.
Microsoft Access offers parameterized queries. These queries and Access tables can be
referenced from other programs like VB6 and .NET through DAO or ADO. From Microsoft
Access, VBA can reference parameterized stored procedures via ADO.
The desktop editions of Microsoft SQL Server can be used with Access as an alternative to
the Jet Database Engine. This support started with MSDE (Microsoft SQL Server Desktop
Engine), a scaled down version of Microsoft SQL Server 2000, and continues with the SQL
Server Express versions of SQL Server 2005 and 2008.
Microsoft Access is a file server-based database. Unlike clientserver relational database

management systems (RDBMS), Microsoft Access does not implement database
triggers, stored procedures, or transaction logging. Access 2010 includes table-level triggers
and stored procedures built into the ACE data engine. Thus a Client-server database system is
not a requirement for using stored procedures or table triggers with Access 2010. Tables,
queries, Forms, reports and Macros can now be developed specifically for web base
application in Access 2010. Integration with Microsoft Share Point 2010 is also highly
improved.

3.3 Internet Information Server (IIS)
Internet Information Services (IIS) formerly called Internet Information Server is

a web server software application and set of feature extension modules created
by Microsoft for use with Microsoft Windows.[2] IIS 7.5
supports HTTP, HTTPS, FTP, FTPS, SMTP and NNTP. It is an integral part of the Windows
Server family of products (and their client counterparts in the cases of Windows NT
4.0 and Windows 2000), as well as certain editions of Windows XP, Windows
Vista and Windows 7. IIS is not turned on by default when Windows is installed. The IIS
Manager is accessed through the Microsoft Management Console or Administrative Tools in
the Control Panel.
All versions of IIS prior to 7.0 running on client operating systems supported only 10
simultaneous connections and a single web site.
FEATURES
IIS 6.0 and higher support the following authentication mechanisms:
Anonymous authentication
Basic access authentication
Digest access authentication
Integrated Windows Authentication
UNC authentication
.NET Passport Authentication (Removed in Windows Server 2008 and IIS 7.0)
Certificate authentication
IIS 7.0 has a modular architecture. Modules, also called extensions, can be added or removed
individually so that only modules required for specific functionality have to be installed. IIS 7
includes native modules as part of the full installation. These modules are individual features
that the server uses to process requests and include the following:
Security modules Used to perform many tasks related to security in the request-
processing pipeline, such as specifying authentication schemes, performing URL
authorization, and filtering requests.

Content modules Used to perform tasks related to content in the request-
processing pipeline, such as processing requests for static files, returning a default
page when a client does not specify a resource in a request, and listing the contents
of a directory.
Compression modules Used to perform tasks related to compression in the

request-processing pipeline, such as compressing responses, applying Gzip
compression transfer coding to responses, and performing pre-compression of static
content.
Caching modules Used to perform tasks related to caching in the request-

processing pipeline, such as storing processed information in memory on the server
and using cached content in subsequent requests for the same resource.
Logging and Diagnostics modules Used to perform tasks related to logging and
diagnostics in the request-processing pipeline, such as passing information and
processing status to HTTP. sys for logging, reporting events, and tracking requests
currently executing in worker processes.
IIS 7.5 includes the following additional or enhanced security features:
Client certificate mapping

IP security
Request filtering
URL authorization
Authentication changed slightly between IIS 6.0 and IIS 7, most notably in that the
anonymous user which was named "IUSR_{machinename}" is a built-in account in Vista and
future operating systems and named "IUSR". Notably, in IIS 7, each authentication
mechanism is isolated into its own module and can be installed or uninstalled.
SECURITY
Earlier versions of IIS were hit with a number of vulnerabilities, especially the CA-
2001-13 which led to the infamous Code Red worm; however, both versions 6.0 and 7.0
currently have no reported issues with this specific vulnerability. In IIS 6.0 Microsoft opted to
change the behaviour of pre-installed ISAPI handlers, many of which were culprits in the
vulnerabilities of 4.0 and 5.0, thus reducing the attack surface of IIS. In addition, IIS 6.0
added a feature called "Web Service Extensions" that prevents IIS from launching any
program without explicit permission by an administrator.
By default IIS 5.1 and lower run websites in-process under the SYSTEM account, a default
Windows account with 'superuser' rights. Under 6.0 all request handling processes have been
brought under a Network Services account with significantly fewer privileges so that should

there be a vulnerability in a feature or in custom code it won't necessarily compromise the
entire system given the sandboxed environment these worker processes run in. IIS 6.0 also
contained a new kernel HTTP stack (http.sys) with a stricter HTTP request parser and
response cache for both static and dynamic content.
According to Secunia, as of June 2011, IIS 7 had a total of 6 resolved vulnerabilities

while IIS 6 had a total of 11 vulnerabilities out of which 1 was still unpatched. The unpatched
security advisory has a severity rating of 2 out of 5.
In June 2007, a Google study of 80 million domains concluded that while the IIS market
share was 23% at the time, IIS servers hosted 49% of the world's malware, the same
as Apache servers whose market share was 66%. The study also observed the geographical
location of these dirty servers and suggested that the cause of this could be the use of pirated
copies of Windows that could not obtain security updates from Microsoft. Microsoft has
corrected this situation; Microsoft now supplies security updates even to pirated copies of
Windows.

CHAPTER 4
SYSTEM DESIGN
Systems design is the process of defining the architecture, components,

modules, interfaces, and data for a system to satisfy specified requirements. Systems design
could see it as the application of systems theory to product development. There is some
overlap with the disciplines of systems analysis, systems architecture and systems
engineering.
Logical design
The logical design of a system pertains to an abstract representation of the data flows, inputs
and outputs of the system. This is often conducted via modeling, using an over-abstract (and
sometimes graphical) model of the actual system. In the context of systems design are
included. Logical design includes ER Diagrams i.e. Entity Relationship Diagrams.
Physical design
The physical design relates to the actual input and output processes of the system. This is laid
down in terms of how data is input into a system, how it is verified/authenticated, how it is
processed, and how it is displayed as output. In Physical design, following requirements
about the system are decided.
1. Input requirement,

2. Output requirements,
3. Storage requirements,
4. Processing Requirements,
5. System control and backup or recovery.
Put another way, the physical portion of systems design can generally be broken down into
three sub-tasks:
1. User Interface Design
2. Data Design
3. Process Design
User Interface Design is concerned with how users add information to the system and with
how the system presents information back to them. Data Design is concerned with how the
data is represented and stored within the system. Finally, Process Design is concerned with
how data moves through the system, and with how and where it is validated, secured and/or
transformed as it flows into, through and out of the system. At the end of the systems design
phase, documentation describing the three sub-tasks is produced and made available for use
in the next phase.
Physical design, in this context, does not refer to the tangible physical design of an
information system. To use an analogy, a personal computer's physical design involves input
via a keyboard, processing within the CPU, and output via a monitor, printer, etc. It would not
concern the actual layout of the tangible hardware, which for a PC would be a monitor, CPU,
motherboard, hard drive, modems, video/graphics cards, USB slots, etc. It involves a detailed
design of a user and a product database structure processor and a control processor. The H/S
personal specification is developed for the proposed system.

4.1 MODULARIZATION DETAILS
Ticket Booking Module

Ticket Cancellation Module
Check Ticket Status
Search Bus between Two status
Send feedback
Display various reports like bus details, all passenger details
Agent registration
Now we consider each module in brief.
4.1.1 TICKET BOOKING MODULE
In this project ticket booking module requires following details:-
1. Person name
2. PNR no
3. Source
4. Destination
5. Age
At the first passenger will search for a booking agency or website or an agent then
he can be able to book his travel ticket on particular date and time.

4.1.2 TICKET CANCELLATION MODULE
This module is for canceling the booked ticket. This module takes following
argument as input
PNR no
If related ticket is booked then it cancel that ticket and if there is no such
ticket is booked then it returns false result.
4.1.3 TICKET STATUS MODULE
This module is for checking status of particular ticket whether it is

booked or cancelled. As above module (Ticket cancellation module) it also takes one
argument:-
PNR no
4.1.4 SEARCH BUSES BETWEEN TWO STATIONS
This module is for searching buses between two desired stations. There are three
arguments needed:-
Source
Destination
Date
It returns a list of buses between those stations on a particular day.

4.1.5 SEND FEEDBACK MODULE
This module enables user to send feedback to related bus agency so that possible
flaws can be removed and maximum customer satisfaction can be achieved. User post his
view with precious suggestions in comment box.
4.1.6 DISPLAY VARIOUS REPORTS LIKE BUS DETAILS AND

PASSANGER DETAILS
This module provides information about bus and passenger as well.
If customer wants to know about a particular bus then he has to pass following information:-
Bus no
Date
And if he wants to know about a particular passenger or himself the he has to pass following
input:-
Pnr no or name
Date
4.1.7 AGENT REGISTRATION MODULE
When a new agent is hired, he must be registered before proceeding.
And there are following inputs are required:-
User name
Password
Confirm password

Security question
Security answer
4.2. DATABASE DESIGN
DATA STRUCTURES:
This part of the Design consists the overall database schema or we can say that tables
which consists various types of records. Table of aa database consists attributes, entities,
tuples for storing and manipulating records.
Some of the tables are as follows:
4.2.1 Agent Basic information
Attribute Name Data type Constraints

SNo AutoNumber Primary Key
Agent-ID Text Not null
Agent-Name Text Not Null
Father-Name Text -
Shop-Name Text -
Shop-City Text -
Shop-State Text -
Shop-Pin Number -
Phone-Number Number -
Mobile-Number Number -
This table is used for storing all details about agent of the bus agency.

4.2.2 FEEDBACK TABLE

SNo AutoNumber Primary Key
Name Text Not null
Email Text -
Phone no Number -
Subject Text -
Comment Text -
User type Text Not Null
This table is used for storing all information about feedback viz who posted this comment
and his mob no, email etc
PRIMARY KEY : - SNo
4.2.3 PASSANGER INFORMATION

PNR Number Primary Key
C_Name Text Not null
C_Phone Text -
C_to Text -
C_from Text
C_date Text
C_time Text
TotalSeat Number
Amount Number
Agent-ID Memo
This table is used for Storing all information about person who is going to tavel.
PRIMARY KEY : - PNR
4.2.4 LOGIN INFORMATION

Username Text -
Password Text -
This table is used for storing all usernames and passwords.

4.3. USER INTERFACE DESIGN
4.3.1 LOGIN FORM

This is Starting Page which is show in web browser.
4.3.2 ABOUT US PAGE

This page is for information about this software.
4.3.3 BOOK TICKET SCREEN PAGE

This page is for displaying before the user where he will input all the required aspects.
4.3.4 BOOK TICKET SCREEN (AFTER FILLING DETAILS)

4.3.5 BOOKED TICKET VIEW

This page shows preview of booking information.
4.3.6 TICKET CANCELLATION SCREEN

This page is for canceling the booked ticket.
4.3.7 CANCELLED TICKET VIEW (AFTER FILLING DETAILS)

4.3.8 CANCELLED TICKET VIEW

This form shows information regarding cancellation of ticket.
4.3.9 TICKET STATUS FORM

This form shows status of the ticket whether it is cancelled or still booked.
4.3.10 TICKET STATUS SCREEN (AFTER INSERTING NUMBER)

4.3.11 TICKET STATUS SCREEN

This form shows information about tickets mode (cancelled or booked).
4.3.12 AGENT REGISTRATION FORM

In this form registration of agent takes place.
4.3.13 AGENT REGISTRATION FORM (AFTER INSERTING DETAILS)

4.3.14 AFTER AGENT REGISTRATION CONGRATULATION SCREEN

This Congratulation page appears after agent registration being completed.
4.3.15 BUS SEARCH FORM

In this form user can search bus between two stations.
4.3.16 SEARCHED BUS LIST VIEW

In this form result shows after completing searching.
4.3.17 AGENT SEARCH FORM

In this form agent can be search by name.
4.3.18 ALL SEARCHED AGENT FORM

In this form all the searched agents show.
4.3.19 USER FEEDBACK SCREEN

In this form user can enter feedback.
4.3.20 ALL USER FEEDBACK LIST FORM

Listed feedback is shown in this form.
4.3.21 BUS LIST VIEW FORM

Listed buses are shown in this form.
4.3.22 PRIVACY AND POLICY

In this form privacy and policy is shown.
4.3.23 TERMS AND CONDITION FORM

In this form terms and conditions are shown.
4.3.24 FREQUENTLY ASKED QUESTIONS FORM

This is FAQs form.
4.3.25 CONTACT US FORM

This form is for helpdesk.
4.3.26 PHOTO GALLERY SCREEN FORM

This form is for photos of buses.
4.3.27 PHOTO THUMBNAIL VIEW SCREEN

This form provides thumbnail view of photos.
CHAPTER 5
IMPLEMENTATION AND MAINTENANCE

5.1 IMPLEMENTATION
INTRODUCTION
System implementation is the stage when the user has thoroughly tested the
system and approves all the features provided by the system. The various tests are performed
and the system is approved only after all the requirements are met and the user is satisfied.
The new system may be totally new, replacing an existing manual or

automated system, or it may be a major modification to an existing system. In either case,
proper implementation is essential to provide a reliable system to meet organizational
requirements. Successful implementation may not guarantee improvement in the organization
using the new system (that is a design question), but improper will prevent it.
Implementation is the process of having systems personnel check out and put
new equipment into use, train users, install the new application and construct any files of data
needed to use it. This phase is less creative than system design. Depending on the size of the
organization that will be involved in using the application and the risk involved in its use,
systems developers may choose to test the operation in only one area of the firm with only
one or two persons. Sometimes, they will run both old and new system in parallel way to
com-pare the results. In still other situations, system developers stop using the old system one
day and start using the new one the next.
The implementation of the web based or lan based networked project has some extra
steps at the time of implementation. We need to configure the system according the
requirement of the software.
TRAINING
Even well designed and technically elegant systems can succeed or fail because of

the way they are used. Therefore the quality of the training received by the personnel
involved with the system in various ways helps or hinders, and may even prevent, the
successful implementation of an information system.
Since, Human Resource Recruitment Process is web-based and user friendly, not
much effort was required in training process.
PARALLEL RUN
In this approach, the old system and the new system are used simultaneously
for some period of time so that the performance of the new system can be monitored and
compared with that of the old system. Also in case of failure of the new system, the user
can fall back on the old system. The risk of this approach is that the user may never want
to shift to new system.
IMMEDIATE CUT-OFF
In this method, the use of the old system ceases as soon as the new system is
implemented and bought in to palace. The old system becomes redundant from the day of
implementation of the new system. There is the high risk involved in this approach if the
new system is not tested rigorously. This is because of the fact that if the new system
fails, then there will not be anything to fall back upon. The advantage of this approach is
that both the systems need not be used simultaneously.
Implementation Tools

The project was implemented using Java server pages with Struts Capabilities. The
implementation work was carried out in Windows 7 platform.
1) ASP.Net
2) IIS server
3) SQL server
Coding
This means program construction with procedural specifications has finished and the
coding for the program begins:
Once the design phase was over, coding commenced
Coding is natural consequence of design.
Coding step translate a detailed design representation of software into a

programming languae realization.
Main emphasis while coding was on style so that the end result was an optimized
code.
The following points were kept into consideration while coding:
Coding Style
The structured programming method was used in all the modules the project. It
incorporated the following features
The code has been written so that the definition and implementation of each
function is contained in one file.

A group of related function was clubbed together in one file to include it when
needed and save us from the labors of writing it again and again.
Naming Convention
As the project size grows, so does the complexity of recognizing the purpose of the
variables. Thus the variables were given meaningful names,whihch would help in
understanding the context and the purpose of the variable.
The function names are also given meaningful names that can be easily understood by
the user.
Indentation
Judicious use of indentation can make the task of reading and understanding a
program much simpler. Indentation is an essential part of a good program. If code id intended
without thought it will seriously affect the readability of the program.
The higher-level statements like he definition of the variables, constants and the
function are intended, with each nested block intended, stating their purpose in the
code.
Blank line is also left between each function definition to make the code look neat.
Indentation for each source file stating he purpose of the file is also done.
5.2 MAINTENANCE:

Maintenance or enhancement can be classified as: -
Corrective
Adaptive
Perfective.
Corrective maintenance means repairing processing or performance failures or

making changes because of previously uncorrected problems or false assumptions.
Adaptive maintenance means changing the program function.
Perfective maintenance means enhancing the performance or modifying the

program(s) to respond to the users additional or changing needs.
Maintenance is actually the implementation of the post implementation review

plan.
As important as it is, many programmers and analysts are reluctant to perform or

identify themselves with the maintenance effort. There are psychological, personality and
professional reasons for this. In any case, a first class effort must be made to ensure that
software changes are made properly and in time to keep the system in tune with user
specifications.
Maintenance is costly. One way to reduce maintenance costs is through

maintenance management and software modification audits. Software modification
consists of program rewrites system level updates, and re-audits of low ranking programs
to verify and correct the soft spots.
The outcome should be more reliable software, a reduced maintenance

backlog, and higher satisfaction and morale among the maintenance staff.
CHAPTER 6

TESTING AND DEPLOYMENT
6.1 SYSTEM TESTING:
Here the System testing involved is the most widely used testing process consisting of
five stages as shown in the figure. In general, the sequence of testing activities is component
testing, integration testing, and then user testing. However, as defects are discovered at any
one stage, they require program modifications to correct them and this may require other
stages in the testing process to be repeated.
Unit testing
Module
testing
Sub-system
testing
System
testing
Acceptance
testing
(Component testing) (Integration testing) (User testing)
Figure 7.1

Testing is the process of detecting errors. Testing performs a very critical role for
quality assurance and for ensuring the reliability of the software. The results of testing are
used later on during maintenance also.
Testing is vital to the success of the system. System testing makes a logical assumption that if
the parts of the system are correct, the goal will be successfully achieved. In adequate testing
or non-testing leads to errors that may not appear until months or even years later (Remember
the New York three day power failure due to a misplaced Break statement).
This creates two problems:
1. The time lag between the cause and the appearance of the problem.
2. The time interval effect of the system errors on files and the records on the system.
A small error can conceivably explode into a much larger problem. Effective testing early in
the process translates directly into long term cost savings from a reduced number of errors.
Another reason for system testing is its utility as a user oriented vehicle before
implementation. The best program is worthless if it does not meet the user requirements.
Unfortunately, the users demands are often compromised by efforts to facilitate program or
design efficiency in terms of processing time or design efficiency.
Thus in this phase we went to test the code we wrote. We needed to know if the code
compiled with the design or not? Whether the code gave the desired outputs on given inputs?
Whether it was ready to be installed on the users computer or some more modifications were
needed?
Through the web applications are characteristically different from their software counterparts
but the basic approach for testing these web applications is quite similar. These basic steps of
testing have been picked from software engineering practices. The following are the steps, we
undertook:

1. The content of the Intranet site is reviewed to uncover Content Errors. Content
Errors covers the typographical errors, grammatical errors, errors in content
consistency, graphical representation and cross referencing errors
2. The design model of the web application is reviewed to uncover the navigation errors.
Use cases, derived as a part of the analysis activity allows a web designer to exercise
each usage scenario against the architectural and navigational design. In essence these
non-executable tests help to uncover the errors in navigation.
3. When web applications are considered the concept of unit changes. Each web page
encapsulate content navigation links, content and processing elements(Forms, Scripts,
JSPs as in our case). It is not always possible to test each of these individually. Thus
is the base of the web applications the unit to be considered is the web page. Unlike
the testing of the algorithmic details of a module the data that flows across the module
interface, page level testing for web applications is driven by content, processing and
links encapsulating the web page.
4. The Assembled web application is tested for overall functionality and content
delivery. the various user cases are used that test the system for errors and mistakes.
5. The Web application is tested for a variety of environmental settings and is tested for
various configurations and upon various platforms.
The modules are integrated and integration test are conducted.
6. Thread based testing is done to monitor the regression tests so that the site does not
become very slow is a lot of users are simultaneously logged on.
7. A controlled and monitored population of end users tests Intranet application, this all
comprises of the User Acceptance Testing.
Because web application evolves continuously, the testing process is an ongoing

activity, conducted by web support staff in our case the Organizations IS people who will
finally update and manage the application.

PSYCHOLOGY OF TESTING
The aim of testing is often to demonstrate that a program works by showing that it has
no errors. The basic purpose of testing phase is to detect the errors that may be present in the
program. Hence one should not start testing with the intent of showing that a program works,
but the intent should be to show that a program doesnt work. Testing is the process of
executing a program with the intent of finding errors.
TESTING OBJECTIVES:
The main objective of testing is to uncover a host of errors, systematically and with
minimum effort and time. Stating formally, we can say,
Testing is a process of executing a program with the intent of finding an error.
A successful test is one that uncovers an as yet undiscovered error.
A good test case is one that has a high probability of finding error, if it exists.
The tests are inadequate to detect possibly present errors.
The software more or less confirms to the quality and reliable standards.

6.2 LEVELS OF TESTING
In order to uncover the errors present in different phases, we have the concept of
levels of testing. The basic levels of testing are
Client Needs
Acceptance Testing
Requirements
System Testing
Design
Integration Testing
Code
Unit Testing

Unit testing
Unit testing focuses verification effort on the smallest unit of software i.e. the
module. Using the detailed design and the process specifications, testing is done to uncover
errors within the boundary of the module. All modules must be successful in the unit test
before the start of the integration testing begins.
Integration Testing
After unit testing, we have to perform integration testing. The goal here is to
see if modules can be integrated properly, the emphasis being on testing interfaces between
modules. This testing activity can be considered as testing the design and hence the emphasis
on testing module interactions.
System Testing
Here the entire software system is tested. The reference document for this
process is the requirements document, and the goal is to see if software meets its
requirements.
Acceptance Testing
Acceptance Testing is performed with realistic data of the client to demonstrate that
the software is working satisfactorily. Testing here is focused on external behavior of the
system; the internal logic of program is not emphasized.
Test cases should be selected so that the largest number of attributes of an equivalence
class is exercised at once. The testing phase is an important part of software development. It
is the process of finding errors and missing operations and also a complete verification to
determine whether the objectives are met and the user requirements are satisfied.

6.3 WHITE BOX TESTING
This is a unit testing method, where a unit will be taken at a time and tested
thoroughly at a statement level to find the maximum possible errors.
I tested step wise every piece of code, taking care that every statement in the code is
executed at least once. The white box testing is also called Glass Box Testing.
I have generated a list of test cases, sample data, which is used to check all possible
combinations of execution paths through the code at every module level.
White-box test focuses on the program control structure. Test cases are derived to
ensure that all statement in the program control structure. Test cases are derived to ensure that
all statement in the program control structure. Test cases are derived to ensure that all
statement in the program has been executed at least once during testing and that all logical
conditions have been exercised. Basis path testing, a white box technique, makes use of
program graphs (or graph matrices) to derive the set of linearly independent test that will
ensure coverage. Condition and data flow testing further exercising degrees of complexity.
BLACK BOX TESTING
This testing method considers a module as a single unit and checks the unit at
interface and communication with other modules rather getting into details at statement level.
Here the module will be treated as a block that will take some input and generate output.
Output for a given set of input combinations are forwarded to other modules.
Black-box test are designed to uncover errors functional requirement without regard to
the internal workings of a program. Black-box testing techniques focus on the information
domain of the software, deriving test cases by partitioning the input and output domain of a
program in manner that provides through test coverage. The black-box test is used to
demonstrate that software functions are operational, that input is properly produced, and that

the integrity of external information are maintained. A black-box test examines some
fundamental aspect of a system with little or no regard for the integral logical structure of the
software.
Graph based testing methods explore the relationship between and behavior of program
objects. Equivalence partitioning divides the input classes of data are likely to exercise
specific software function. Boundary values analysis probes the programs ability to handle
data at the limits of acceptability.
6.4 TEST INFORMATION FLOW
A strategy for software testing may also be viewed in the context of the spiral. Unit
testing begins at the vortex of the spiral and, concentrates on each unit, component of the
software as implemented in source code. Testing progresses moving outward along the
spiral to integration testing, where the focus is on designed the construction of the
software architecture. Taking another turn outward on spiral, we encounter validation
testing,
Where requirements established as part of software requirements analysis are validated

against the software that has been constructed. Finally, we arrive at system testing, where
the software and other system elements are tested as a whole. To test computer software, we
spiral out along stream lines that broaden the scope of testing with each turn.
Considering the process from a procedural point of view, testing within the context of
software engineering is actually a series of four steps that are implemented sequentially. The
steps are shown in Figure. Initially, tests focus on each component individually, ensuring that
it functions properly as unit. Hence, the name unit testing. Unit testing makes heavy use of
white-box testing techniques, exercising specific paths in modules control structure to ensure
complete coverage and maximum error detection.

TESTING TECHNIQUES
System Testing
Validation Testing
Integration Testing
Validation testing

INFORMATION FLOW OF DATA FOR TESTING
Evaluation
Software
Configuration
Test Results
Error
Error Rate
Data
Testing Expected Results

Debug
Reliability
Model
Test Configuration
Predicated Reliability
Correction

CHAPTER 7
SYSTEM SECURITY
7.1 Introduction
One might think that there is a little reason to be concerned about security in an
intranet. After all, by definition an intranet is internal to ones organization; outsider cannot
access it. There are strong arguments for the position that an intranet should be completely
open to its users, with little or no security. One might not have considered ones intranet on
any other light.
On the other hand, implementing some simple, built-in security measures in ones intranet
can allow one to provide resources one might not have considered possible in such context.
For example, one can give access to some Web Pages to some people without them available
to owner entire customer base, with several kinds of authentication.
Intranet security is, then, a multifaceted issue, with both opportunities and dangers,
especially if ones network is part of the Intranet.
There are basically two types of security associated with this system:
7.2 Physical security:-
Damage due to natural causes like earth tremor, flooding, water logging, fire hazards,
atmospheric or environmental conditions etc..For overcoming these difficulties the
replica of the data are automatically stored at various networks and for environmental
conditions Air conditioning environment is created.

7.3 Data security:-
There are basically two problems associated with data security:-
a). Data not being available to the authorized person at the time of need.
b). Data becoming available to the unauthorized person.
To overcome these difficulties the following access facilities has been provided:-
i) Identification:-
Unique Ids for the different users have been provided.
ii) Authentication:-
System checks the password under the particular user identification. The computer
permits the various resource to the authorized person.
iii) Authorization:-
The access control mechanism to prevent unauthorized logging to the system.
7.4 Need for Security
Many people view computer and network security in a negative light, thinking
of it only in terms of restricting access to services. One major view of network security is
that which is not expressly permitted is denied. Although this is a good way of thinking
about how to connect other organization to the internet, one can, and possibly should, view
intranet security from a more positive angle.
Property set up, intranet security can be an enabler, enriching ones intranet
with services and resources one would not otherwise be able to provide. Such an overall
security policy might be described as that which is not expressly denied is permitted.

This does not mean that one should throw caution to the wind and make everything
available to ones users on ones intranet. There are many things to consider when placing
sensitive business data out on ones intranet. It may fall into the wrong hands, or worse, be
used against ones business. For example, some of ones users might have information they
would li9ke to make available, provided access to it can be limited to a specified group-for
example, confidential management or financial information. Without the ability to ensure that
only those who have the right to see such information will have access, the custodians of data
will not be willing to put it on ones intranet. Providing security increases ones
organizations ability to use the important collaborative aspects of an intranet.
The more defensive approach, preventing abuse of ones intranet, is also given play,
however. Organizations needs for security in an intranet can vary widely. Businesses in
which confidentiality and discretion are the norm in handling proprietary information and
corporate intellectual property have different needs than a college or university, for example.
Academic institutions generally tilt toward making the free exchange of ideas a primary
interest. At the same time, though the curiosity (to use a polite word) of undergraduates
requires strong needs for security. Keeping prying sophomores out of university
administration computing resources is a high priority; for example, students have been known
to try to access grade records(their own or those of others) for various reasons.

CHAPTER 8
SOFTWARE AND HARDWARE REQUIREMENT
8.1 Hardware Requirements
Processor: Pentium-IV
RAM: 512 MB
O/S: Windows-XP SP3
Hard Disk: 2GB
8.2 Software Requirements
Operating System: Microsoft Windows XP/7.
IDE: Visual Studio 2010 (Framework 4.0)
Database Server: MS Access.

CHAPTER 9
FUTURE ENHANCEMENT
1 Can be extended to manage inventory
By integrating it with the inventory information and management techniques

we can it as Accounting with inventory System.
2 Can be extended for Bi-Language
By integrating it with the English language in project we can extend it to use

bi-language software (Hindi and English).
3 Can be extended for Multi-user
By integrating networking and other concepts we can extends it to use it as

multi-user environment in place of single user environment.
4 Can be added more Reports as per Requirement
By integrating the more report like station wise report, ticket information etc.
5 Mobile Ticket Booking
This application can be up-graded from web application to mobile accounting.

Conclusion
At the end of the Report and project development we founds that overall performance
of this project is 80 to 90 % are perfect, for its working functionality. Because project
documentation provides such capabilities which can responsible to evaluates the
performance and accuracy level of the project.
So at the end of this, we found that this project provide the accurate result in the
working area of Ticket Booking, Cancellation, searching information and add the new
user

BIBLIOGRAPHY
1. www.stackoverflow.com
2. www.c-sharpcorner.com
3. www.mindcracker.com
4. www.dotnetcurry.com
5. www.dotnetspider.com

Bus Reservation System Final Report

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Bus Reservation System Final Report

Загружено:

Авторское право:

Доступные форматы

CHAPTER 1

1.1 MOTIVATION AND OBJECTIVE

Enhance of the security level in centralized system.

Register New Agent.

View Details of Agent, Bus Information, User Feedback

Different Payment Mode: Cash Card, Credit Card Etc.

PROBLEM DEFINITION AND REQUIREMENT ANALYSIS

2.1 IDENTIFICATION OF NEED

Enhance of the security level in centralized system.

Register New Agent.

View Details of Agent, Bus Information, User Feedback

Different Payment Mode: Cash Card, Credit Card Etc.

2.2 FEASIBILITY STUDY

As such, a well-designed feasibility study should provide a historical background of the

2 Bus Reservation System

The assessment is based on an outline design of system requirements, to determine whether

The human and economic factor

The possible solutions to the problems

2.2.2 OPERATIONAL FEASIBILITY

3 Bus Reservation System

2.2.4 TECHNICAL FEASIBILITY

The technical feasibility assessment is focused on gaining an understanding of the present

2.2.5 FINANCIAL FEASIBILITY

Total estimated cost of the project.

Existing investment by the promoter in any other business

Projected cash flow and profitability.

The financial viability of a project should provide the following information.

4 Bus Reservation System

Project's funding potential and repayment terms.

Sensitivity in the repayments capability to the following factors:

o Mild slowing of sales.

o Acute reduction/slowing of sales.

o Small increase in cost.

o Large increase in cost.

o Adverse economic conditions.

5 Bus Reservation System

PROJECT MANAGEMENT ACTIVITIES

Creating work breakdown Structure.

These task defining following .

PROJECT ORGANIZATION WORKS BEST WHEN

6 Bus Reservation System

The work contains complex interrelated tasks requiring specialized skills.

The project is temporary but critical to organization.

Often temporary structure.

Headed by project manager

Monitor schedule & costs.

Permanent structure called matrix organization.

WORK BREAKDOWN STRUCTURE

Subtasks in major tasks.

7 Bus Reservation System

Figure: 2.1 Example of a Data Flow diagram

External Entities/ Terminators are outside of the system being modeled.

are represented by rectangles.

8 Bus Reservation System

Input to generate the output.

represented by an open-ended rectangles or a cylinder symbol.

Data Flows, represented by arrows, are how data moves between

Terminators, processes, and data stores.

9 Bus Reservation System

Book Ticket Bus

can submit feed back

10 Bus Reservation System

An Entity Relationship Diagram (ERD) gives a graphical representation of the

An aggregation of a number of data elements.