Bus Reservation
Bus Reservation
Bus Reservation
REPORT
ON
“BUS RESERVATION SYSTEM”
Chapter 1 Introduction
System
Chapter 5 System Analysis
Chapter 10 Conclusion
Introduction
In bus reservation system there has been a collection of buses, agent who are
booking tickets for customer’s journey which give bus number and departure
time of the bus. According to its name it manages the details of all agent,
tickets, rental details, and timing details and so on. It also manages the updating
of the objects.
In the tour detail there is information about bus, who has been taking
customers at their destination, it also contain the detailed information about the
customer, who has been taken from which bus and at what are the number of
members he or she is taking his/her journey.
This section also contain the details of booking time of the seat(s) or
collecting time of the tickets, this section also contain the booking date and the
name of agent which is optional, by which the customer can reserve the seats
for his journey
The main objective of this project to provide the better work efficiency,
security, accuracy, reliability, feasibility. The error occurred could be reduced
to nil and working conditions can be improved.
Development model
Development model
Our project life cycle uses the waterfall model, also known as classic life cycle
model or linear sequential model.
System/Information
Engineering
Software requirements analysis involves requirements for both the system and
the software to be document and reviewed with the customer.
3. Design
4. Code Generation
5. Testing
Once code has been generated, program testing begins. The testing focuses on
the logical internals of the software, ensuring that all statement have been
tested, and on the functional externals; that is, conducting test to uncover errors
and ensure that define input will produce actual results that agree with required
results.
6. Support
Software will undoubtedly undergo change after it is delivered to the customer.
Change will occur because errors have been encountered, because the software
must be adapted to accommodate changes in its external environment or
because the customer requires functional or performance enhancements .
System Study
Before the project can begin, it becomes necessary to estimate the work to be
done, the resource that will be required, and the time that will elapse from start
to finish. During making such a plan we visited site many more times.
We started to asking context-free questions; that is, a set of questions that will
lead to a basic understanding of the problem. The first set of context-free
questions was like this:
What do you want to be done?
Who will use this solution?
What is wrong with your existing working systems?
Is there another source for the solution?
Can you show us (or describe) the environment in which the solution
will be used?
After first round of above asked questions. We revisited the site and asked
many more questions considering to final set of questions.
Are our questions relevant to the problem that you need to be solved?
Are we asking too many questions?
Should we be asking you anything else?
2.2.2 Feasibility
Software cost and effort estimation will never be an exact science. Too may
variables—human, technical, environmental, political—can affect the ultimate
cost of software and effort applied to develop it. However, software project
estimation can be transformed a black art to a series of systematic steps that
provide estimates with acceptable risk.
estimation.
Unfortunately, the first option, however attractive, is not practical. Cost estimates
must be provided “Up front”. However, we should recognize that the longer we
wait, the more we know, and the more we know, the less likely we are to make
serious errors in our estimates.
The second option can work reasonably well, if the current project is quite
similar to past efforts and other project influences (e.g., the customer, business
conditions, the SEE, deadlines) are equivalent. Unfortunately past experience has
not always been a good indicator of future results.
The remaining options are viable approaches the software project estimation.
Ideally, the techniques noted for each option be applied in tandem; each used as
cross check for the other. Decomposition techniques take a “divide and conquer”
approach to software project estimation. By decomposing a project into major
functions and related software engineering activities, cost and effort estimation
can be performed in the stepwise fashion.
D = f (vi)
Each of the viable software cost estimation options is only as good as the
historical data used to seed the estimate. If no historical data exist, costing rests
on a very shaky foundation.
Estimates of Effort
A decomposition of the product function
The selection of the appropriate process model and task set
Decomposition of tasks
PERT chart for this application software is illustrated in figure 3.1. The critical
Path for this Project is Design, Code generation and Integration and testing.
Aug-2008
Aug 15,2008
Documentati Finish
on and Jan 3, 2008
Report
Oct 30, 2008
Management System”.
Finish: Jan 3,
2008
Figure: 4.2 Gant chart for the Project University Study Center Management
System. Note: Wk1—week1, d1—day1.
System Analysis
Software requirements analysis is a process of discovery, refinement,
modeling, and specification. Requirement analysis proves the software designer
with a representation of information, function, and behavior that can be
translated to data, architectural interface, and component -level designs. To
perform the job properly we need to follow as set of underlying concepts and
principles of Analysis.
considered.
Data and control objects can be related to other data and control objects.
For example, the date object Status declare has one or more relationships with
the objects like total no of flying, period left for the maintenance of aircraft an
others.
5.1.2 Modeling
The second and third operational analysis principles require that we build
models of function and behavior.
Input
Processing
And output.
The functional model begins with a single context level model (i.e., the name
of the software to be built). Over a series of iterations, more and more
functional detail is gathered, until a through delineation of all system
functionality is represented.
Horizontal partitioning:
Acceptance Rejection
The above six questions are made as per the Andriole suggestions for
prototyping approach.
E-R DIAGRAM:
BUS RESERVATION
SYSTEM
Give
service
Divid
BUSES
Work
area
Care
DIFFERENT
examin TYPE OF Full
Wor
BUSES
SLEEPER
OR
WITHOUT DEPARTMENT SEATS
SLEEPER
The following DFD shows how the working of a reservation system could be
smoothly managed:
WORK AREAS
BUSES RESERVED
RECORDS AGENT
AGENT
DETAILS
REPORT TABLE
DETAIL DESCRIPTION OF DATA FLOW DIAGRAM:
We have STARBUS as our database and some of our tables (relation) are
and TIMELIST
STARBUS
AGENTBASICINFO
FEEDBACK
PASSANGERIFNO
STATIS
TIMELIST
In our table AGENT_BASIC_INFO we have following field such as agent_id,
AGENT_BASIC_INFO
AGENT_ID
AGENT_NAME
AGENT_FNAME
AGENT_SHOP_NAME
AGENT_SHOP_ADDRESS
AGENT_SHOP_CITY
AGENT_PHON_NUMBER
AGENT_MOBIL_NUMBER
AGENT_CURRENT_BAL
In our FEEDBACK table we have fields like name, Email, Phon, Subject,
Email
Name
Phone
FEEDBACK
Comment Subject
User_type
In our table PASSANGER_INFO we have filed like bill_no, c_name, c_phone,
C_name
C_phon
Bill_no
C_to
Status
PASSANGER
_INFO C_from
Agent_id
C_time
Amount
Seat_no
Total_seat
In the table of TIME_LIST we have fields such as Sno, Satation_name,
Station_name
Sno
Rate_perSeat
TIME_LIST
Bus_number Time
Reach_time
PROCESS LOGIC:
the more they are comfortable with us, the more customers we have
visiting our reservation unit .the above tables and modules facilitates
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, the 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 network-
aware software. In fact, the .NET Framework is the first platform designed
from the ground up with the Internet in mind.
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 developer’s use.
Elements of the .NET Framework
The .NET Framework consists of three key elements as show in below diagram
ASP.NET
Window Forms
Web Server Web Form Visual
Studio.NET
Operating System
The CLR is also responsible for compiling code just before it executes. Instead
of
producing a binary representation of your code, as traditional compilers
do, .NET
compilers produce a representation of your code in a language common to
the .NET Framework: Microsoft Intermediate Language, often referred to as
IL. When your code executes for the first time, the CLR invokes a special
compiler called a Just In Time (JIT) compiler, Because all .NET languages
have the same compiled representation, they all have similar performance
characteristics. This means that a program written in Visual Basic .NET can
perform as well as the same program written in Visual C++ .NET.
The benefits of using the .NET Class Library include a consistent set of
services available to all .NET languages and simplified deployment, because
the .NET Class Library is available on all implementations of the .NET
Framework.
3. Unifying components
Until this point, this chapter has covered the low-level components of the .NET
Framework. The unifying components, listed next, are the means by which you
can access the services the .NET Framework provides:
ASP.NET
Windows Forms
Visual Studio .NET
Characteristics
Pages
ASP.NET pages, known officially as "web forms", are the main building block
for application development. Web forms are contained in files with an ASPX
extension; in programming jargon, these files typically contain static (X)HTML
markup, as well as markup defining server-side Web Controls and User
Controls where the developers place all the required static and dynamic content
for the web page. Additionally, dynamic code which runs on the server can be
placed in a page within a block <% -- dynamic code -- %> which is similar to
other web development technologies such as PHP, JSP, and ASP, but this
practice is generally discouraged except for the purposes of data binding since
it requires more calls when rendering the page.
Note that this sample uses code "inline", as opposed to code behind.
<%@ Page Language="C#" %>
<script runat="server">
</script>
<html xmlns="http://www.w3.org/1999/xhtml">
<head runat="server">
<title>Sample page</title>
</head>
<body>
<form id="form1" runat="server">
<div>
The current time is: <asp:Label
runat="server" id="Label1" />
</div>
</form>
</body>
</html>
Code-behind model
Example
The above tag is placed at the beginning of the ASPX file. The CodeFile
property of the @ Page directive specifies the file (.cs or .vb) acting as the
code-behind while the Inherits property specifies the Class the Page derives
from. In this example, the @ Page directive is included in SamplePage.aspx,
then SampleCodeBehind.aspx.cs acts as the code-behind for this page:
using System;
namespace Website
{
public partial class SampleCodeBehind :
System.Web.UI.Page
{
protected override void Page_Load(EventArgs e)
{
base.OnLoad(e);
}
}
}
In this case, the Page_Load () method is called every time the ASPX page is
requested. The programmer can implement event handlers at several stages of
the page execution process to perform processing.
System Design
1. Index page
This webpage is the starting page of the Website.It gives the followings:
Login for the Admin and Agent
TollFree number of the other city.
Display adventage of the StarBus
Links for TicketBooking, Agent and Recovery password.
Links for Feedback, FAQ, Terms and Condition’s.
2. Status.
Accessed by anyone.
Information about the booking which seat is booked and which
is empty.
3. Agent name.
As in the above image the Agent name webpage is displaying :
Accessed by anyone.
Contains information about name, address and phone number
of the agent.
4. Feedback
As in the above image Feedback webpage is displaying:
5. FAQ
As in the above image FAQ webpage is displaying:
Accessed by anyone.
Useful for customer
Contain information when to reach the starting point and what
should do, in case when our ticket is lost.
8. Login page
It required user name who forget its password and then click on
Next button.
And also provide link for administration and other.
10. Identity Confirmation.
Username
Password
Email
Security Question.
Security Answer.
As in the above image the Create agents continue page web page is
displaying:
Name
Father’s Name
Shop Name
Shop City
Shop phone number
Mobile Number
Deposit amount
Agent ID
Name
Shop Name
Shop City
Current Balance
Mobile Number
THANKYOU.