This software project is aimed at automation of online ticket booking. Objective of the project is to develop customize software package for ticket booking.
When we do this task manually then it become very hard to manage the ticket booking .So are developing this system to manage booking of ticket automatically. In this Bus Ticket Booking project we develop the system that can help the user to book their ticket online. In this project we take care of every services related to travelling and online ticket booking .When you start your traveling tour you have to book ticket so we help you in booking your traveling ticket
1. 1
PREFACE
The Online Bus Ticket Booking is a web-based application that allows visitors check bus
ticket availability, buy bus ticket and pay the bus ticket online. This system is established
for all the home/office users after gaining access from the administrator. Online Bus
Booking provides bus transportation system, a facility to reserved seats, cancellation of
seats and different types of enquiry which need an instant and quick reservation. This
system can be used by the users in performing online reservation via internet for their all
business purposes. Users can use this program directly on their websites and no need to
install it.
2. 2
INDEX:-
Acknowledgement:-
Introduction:-
ī About Project
ī About Client
Initial Requirement:-
System Analysis:-
ī Objective
ī Existing System
ī Proposed System Description
Feasibility Study:-
ī Financial And Economic Feasibility
ī Technical Feasibility
ī Operational Feasibility
System Requirement:-
ī Platform
3. 3
ī Hardware Requirement
ī Software Requirement
ī System Requirement and Specification
ī Functional Requirement
ī Non Functional Requirement
ī Security Requirement
ī Output Requirement
ī Output of the bus booking Project
ī Architecture & Proposed System
ī Module Description
System Design:-
ī Architectural Design
ī Logical Design
ī Physical Design
ī Software Process Models
ī Water Fall Model
ī The Waterfall model can be shown graphically
ī The Functional Module System
ī Table Schema
Data Flow Diagram:-
ī Symbol Of DFD
4. 4
ī DFD â0âLevel
ī DFD â1âLevel
ī Data Flow Chart
ER Diagram:-
ī Guideline Form Drawing ER Diagram
ī ER Diagram Uses
ī Benefits of ER diagrams
ī ER Diagram Templates
ī ER Diagrams Usage
Bibliography & Reference:-
5. 5
ACKNOWLEDGEMENT
The software project âONLINE BUS TICKET BOOKINGâ is an original work of mine. But I
would never have able to complete it alone on my own. I always needed help an support to
complete it. This help and came in many forms from different people. I have opportunity to
express my profound sense of gratitude and respect to all those who helped me throughout the
duration of this project.
First of all I would like to thank my supervisor Mr. KAMALA PRASAD GUPTA
under whose guidance I complete the software project without his support, I was literally
impossible to complete it. His guidance was like a streak of light on a no-moon night to me. It
was immense importance. It was he who explained the topic in detail to me, told me about
making this software project presentable.
I would also thank my chat friends who were available even at very late hours of and
helped me in acquiring valuable information from the World Wide Web. I am really a great
learning experience.
Last but not least I thank all who have helped me directly and indirectly (GOD) at time
of need.
Gaurav Kumar Rai
6. 6
INTRODUCTION
About Project-
This software project is aimed at automation of online ticket booking. Objective of the
project is to develop customize software package for ticket booking.
When we do this task manually then it become very hard to manage the ticket
booking .So are developing this system to manage bookingof ticket automatically. In this
Bus Ticket Booking project we develop the system that can help the user to book their
ticket online. In this project we take care of every services related to travelling and online
ticket booking .When you start your traveling tour you have to book ticket so we help
you in booking your traveling ticket .
About client-
It is developed so that the costumer can easily check the bus availability status, the
costumer also book the ticket from any place and any time and pay the amount of ticket
from anywhere. The system must have a database which contain the customer
information, it must be able to accurately give the bus information such as the bus
schedule and also have a nice interface to make it easier to use. Finally, the application
must also be a user-friendly for commercial purpose.
7. 7
INITIAL REQUIREMNT
When a project is started an initial investigation is carried out. During this phase
of study users need has recognized and other requirements are determined. Once
the problem has been defined a study is carried out to select the best system i.e.
a feasible system that meets performance requirements. So Feasibility is the
determination of whether or not a project is worth doing and the process followed
in making this determination is called a Feasibility Study. In order to conduct the
feasibility study we have seven distinct, but inter-related types of feasibility, these
are Technical feasibility, Operational feasibility, Economical feasibility, Social
feasibility, Management feasibility, Legal feasibility and Time feasibility. Out of these
seven three are key feasibilities to consider, these are:
ī Technical Feasibility
ī Economical Feasibility
ī Operational feasibility
9. 9
SYSTEM ANALYSIS
System analysis and design refers to the process of
examining a situation with the intent of improving it through better procedure and
methods. System design is the process of planning a new system or one to
replace or complement an existing system. But before this planning can be done,
we must thoroughly understand the system and determine how computer can best
be used to make its operation more effective. System analysis is, therefore, the
process of gathering and interpreting facts, diagnosing problems and using the
information to recommend improvements to system.
ī Understand the ticket problem before you begin to create the bus ticket analysis
model.
ī Develop prototypes that enable abuser to understand how human machine
interaction will occur.
ī Record the bus ticket origin of and the reason for every requirement.
ī User multiple behavioral views of booking requirement like building data,
function and models.
ī Work to eliminate ambiguity.
10. 10
Objective-
The main objective of the system will lead to increase in the ticket booking efficiency of
the project Staff and members of the Ticket Booking Agency with little throughput.
This system project is made as user friendly as possible so that any one can use it with
little knowledge of system computers. the ticket booking project will reduce the ticket
booking tedious job of system paperwork by keeping all the project details of bus ticket
booking, cancelling tickets are stored in the form database in computerâs hard disk. Up-
to-date information of the system Performance status and other enquires. We provide up
to date information that is not possible manually. he objective of my project is to make
easy the ticket booking project system of Ticket Booking Agency simple, reliable, user
friendly, and corrective. Moreover less time consuming as compared to manual work.
11. 11
Existing System
This website is very easy to operate it provide database about
Institute, Courses and main advantage of this project is that it will generate an
environment such that more than one person could solve his problem together ,
customer have to give query for getting desire solution. This project has been
developed on HTML and PHP. It has been developed and implemented for regular
use by the user. It is very easy to understand and operate. Hence it is/Will be totally
user friendly & interactive website.
ī The work is done manually.
ī Those who are interested in inquiring about the bus type, its Tickets price,
available seats, facility of the bus etc. has to walk to the booking office.
ī This creates a huge relief for the customer of the office on weekend to send their
time.
12. 12
Proposed System Description
The system is very simple in design and to implement. The system required very low
system resources and the system will work in almost all configurations. It has got
following feature:
ī It will ensure data accuracy.
ī Records will be efficiently maintained by DBMS.
ī Availability of seats can be enquired easily.
ī Passenger can also cancel their tickets easily.
ī Minimum time needed for the various processing.
ī It will provide better service.
Stated that system design is to create a technical solution that satisfies the functional
requirement for the system. At this point in the project life cycle there should be a
Function Specification, written primarily in business terminology containing a complete
description of the operational needs of the various organizational entities that will use the
system. The challenge is to translate all of this information into Technical Specifications
that accurately describe the design of the system, and that can be used as input system
construction.
14. 14
FEASIBILITY STUDY
When a project is started an initial investigation is carried out.
During this phase of study users need has recognized and other requirements are
determined. Once the problem has been defined a study is carried out to select the
best system i.e. a feasible system that meets performance requirements. So Feasibility is
the determination of whether or not a project is worth doing and the process
followed in making this determination is called a Feasibility Study. In order to
conduct the feasibility study we have seven distinct, but inter-related types of
feasibility, these are Technical feasibility, Operational feasibility, Economical feasibility,
Social feasibility, Management feasibility, Legal feasibility and Time feasibility.
The objective of the feasibility study is not only to solve the problem but also to
acquire the sense of its scope. During the study, the problem definition is crystallized and
aspects of the problem be included in the system are estimated. Cost and benefits are
estimate with greater accuracy at this stags. There keys constraints are involved in
feasibility study.
ī Financial and Economic feasibility.
ī Technical feasibility.
ī Operational feasibility.
15. 15
Financial And Economic Feasibility-
Economic feasibility or cost benefit is an assessment of the economic justification for a
computer system project. Since the system is a web based, any number of employer can
use this tool from anywhere and anytime.
Not only the cost of hardware, softwareâĻetcâĻis considered but also benefits in
the form of reduced cost are considered. The immigrant can be apply for the VISA online
without going to foreign exchange.
Technical Feasibility-
According to roger S. pressman âtechnical feasibilityâ is the assessment of the technical
of the system. The develop for platform independent environment VB and SQL server are
used to developed the system. The technical feasibility has been carried out. The system
is technical feasible for developed. The system can be developed with exiting facility.
The technical consideration evaluates the hardware requirement, software technology
etcâĻas per the requirement VB as front end SQL server as back end.
16. 16
Operating Feasibility-
Operational feasibility deals with study prospectus of the system. This system
operationally eliminates all the tensions of the tensions of the admin and
effectively tracking the project process. This kind of automation will surely reduce time
and energy, which previously consumed in manual work. Based on the study, the system
is provided to be operationally feasible.
Processed feasibility is beneficial only it meet the user requirement. This system will
certainly be supported since it produces good results lots of work.
18. 18
SYSTEM RQUIREMENT
The system requirement definition is concerned with the analysis of the existing system with the
aim of determining and structuring the requirement of the proposed system. It is achieved with
the aid of user requirement. The analysis stage was specifically carried out in focus of the
functionality dataflow at online bus ticket booking.
Platform-
Windows is very powerful scalable Operating System that provides basic file and prints services
as well as robust platform for server application. Main features are as follow-
īˇ An easier way to use Interface and tools
īˇ More extensive Network Performance.
īˇ Enhanced communication features.
19. 19
Hardware Requirement
īˇ Processor: Intel Pentium IV
īˇ Processor speed: 1.4 GHz
īˇ RAM : 2 GB or above
īˇ Hard disk : 250 GB OR above
Software Requirement-
īˇ Operating System: Windows 2000,2007,2008
īˇ Web Bowser: Chrome and Mozilla Firefox
īˇ Internet Browser
īˇ M.S. platform
īˇ Microsoft SQL Server 2008
Language used:
Front End: HTML, PHP
Back End: Microsoft SQL Server 2008.
20. 20
System Requirement And Specification
The System Requirement Specification (SRS) will provide a detailed description of the
requirement for the âONLINE BUS TICKET BOOKINGâ. This SRS will allow for a
complete understand of what is needed for the bus ticket booking construction. The clear
understanding of the bus ticket booking and itâs functionality will allow for the correct
software to be developed for the end user and thus will be used for the development of
the future stages of the project. This SRS will also provide the function for the project.
From this SRS, the âONLINE BUS TICKET BOOKINGâ can be designed, constructed,
and finally tested.
This SRS will be used by the software engineers constructing the âONLINE BUS TICK
BOOKINGâ and the Bus end user. The software engineers will use the SRS so that to fully
understand the expectations of this ONLINE BUS TICKET BOOKINGâ to construct the
appropriate software.
21. 21
Functional Requirement-
Functional Requirement define the specific function that the system perform, along with
the data operated on by the functions. The functional requirements are presented in
scenarios that depict an operational system from the perspective of its end user. Included
are one or more example of all system feature and an enumeration of all the specific
requirement associated with these feature.
ī The system shall incorporate mechanism to authenticate its user.
ī The system shall verify and validate all user input and should notify in case
of error detection and should help the user in error correction.
ī The system shall allow sharing of files in the system.
ī The system shall allow quick message to be exchange without face to face
interaction.
22. 22
Non-functional Requirement-
Non-functional requirements address aspects of the system other than the specific
functions it performs. These aspects include system performance, costs, and such general
system characteristics as reliability, security, and portability. The non-functional
requirements also address aspects of the system development process and operational
personnel. It includes the following:
ī The system shall be used friendly and consistent
ī The system shall provide attractive graphical interface for the user
ī The system shall allow developer access to installed environment
ī The system shall target customer base.
23. 23
Security Requirement-
The System use SSL (secured socked layer) in all transactions that include any
confidential customer information. The system must automatically log out all customer
after a period of inactivity. The system should not leave any cookies on the customerâs
computer containing the userâs password. The systemâs back-end servers shall only be
accessible to authenticated management.
Passenger Service Representatives and managers will be able to log in to the BUS
TICKET BOOKING. Passenger Service Representative will have access to the
Reservation/Booking subsystem. Managers will have access to the management
subsystem as well as the Reservation/booking subsystems. Access to the various
subsystem will be protected by a user log in screen that requires a user name and
password.
24. 24
Output Requirement:-
Company's customer can buy bus ticket online and pay the bus ticket through Credit
Card. Others bus companies also can use the online system to easy their customer to buy
bus ticket. Further more, the online system is expected to help ease especially the counter
staff at the selling counter who has to deal with numerous sales daily. It should also assist
the branch manager in calculating their daily collections and generating reports. In the
long-term operation, the sales of tickets at Transnational are expected to increase as
passengers' satisfaction is almost guaranteed with the availability of accurate information,
shorter queues and better services.
25. 25
Output of the bus booking Project:
Login bus ticket Module: This booking system is a very first module in this project a
person can want to enter into this software project he/she must have pass through this
module, in other word we can say that this is Authentication module because the user
authenticates with his/her password and username.
New User Module: In this booking system module we can create new user his/her
username, password and his rights as our choice.
Bus Type Master: This booking system module deals with the bus ticket management of
the booking system bus type information such as the bus type id, bus type name, bus
description etc.
ADD BUS TYPE INFO. TO THE Bus Ticket DATABASE
Bus Master: This booking system module deals with bus master related data such
as bus id, bus name, capacity, start time , start position ,destination etc.
26. 26
ADD BUS MASTER DETAILS TO THE DATABASE
Customer Transaction: This ticket booking module deals with the bus
ticket management of the booking system customer information such customer name,
customer id ,street code, city code etc.
ADD CUSTOMER DETAILS TO THE DATABASE
ROUTE MASTER: This ticket booking module is responsible for managing the bus route
related details such as route id, route name, start position, destination etc.
ADD ROUTE DETAILS TO THE BUS ROUTE MASTER
Based on the input provided system will show the desired output/report.
ī Bus Ticket Information
ī customer Information booking system
ī Fine Details
ī Branch Information booking system
ī bus ticket Price details
ī Status of the bus Ticket
ī User Card details
ī
27. 27
Architecture of The Proposed System-
This process supports existing infrastructure requirements and provides specific
recommendations for hardware and network solutions based on existing and projected
user needs. Application requirements, data resources, and people within an organization
are all important in determining the optimum hardware solution. It is represented using a
three tier architecture that comprises of user interface, process management and Database
Management System (DBMS). It shows the components of the system, the services they
provide and the way they communicate to bring about the system functionality.
28. 28
Module Description-
Admin Module
This module deals with addition and deletion of routes, buses available, pick up points,
dropping points, bus codes, passenger details and bus details. He has the complete control
over the application. Only admin can perform these functionalities.
Bookings and Cancellation Module
The following functionalities are included in this module
īˇ Search routes
īˇ Select bus
īˇ Select seats and pick up points
īˇ Provide information and payment gateway
īˇ Print booked ticket
īˇ Cancel the ticket
īˇ User suggestions/complaints
30. 30
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
be seen as the application of systems theory to product development. There is some
overlap with the disciplines of systems analysis, systems architecture and systems
engineering.
Architectural design
The architectural design of a system emphasizes the design of the systems architecture
that describes the structure, behavior and more views of that system and analysis.
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,
designs are included. Logical design includes entity-relationship diagrams (ER
diagrams).
Physical design
The physical design relates to the actual input and output processes of the system. This is
explained in terms of how data is input into a system, how it is verified/authenticated,
31. 31
how it is processed, and how it is displayed. In physical design, the 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
32. 32
The Software Process Models
A structured set of activity required to develop a software system
ī Specification
ī Design
ī Validation
ī Evolution
A software process model is an abstract representation of a process. It presents a
description of a process from some particular perspective.
The Water fall model:-
The development model which is best suited to my software
project is the waterfall model, which is the simplest process model, which states that
phases are organize in a linear order. In waterfall model, the sequence of activities
performed in software development project is: requirement analysis, project planning,
system design and detail design, coding and testing.
Linear ordering of activities has some important consequences. First,
to clearly identify the end of a phase and beginning of the next phase, some certification
33. 33
mechanism has to be employed as the end of each phase. This is usually done by some
verification and validation means that will ensure that output of a phase is consist with its
input, and the output of phase is consist with the overall requirement of the system.
There are two basic assumptions for justifying the linear ordering of
phase in the manner proposed by the waterfall model:
1. For a successful project resulting in a successful product, all phase in the waterfall
model must be performed any way.
2. Any different ordering of the phase will result in a less successful software
product.
34. 34
The Waterfall model can be shown graphically
System feasibility
validation
System Design
verification
Coding
verification
Testing and
Integration
Installation Operation
And Maintenance
Detailed design
verification
Requirement analysis and
Project planning
validation
Feasibility
Report
Requirement
document
Project plan
Design
Document
Detailed Design
Document
Program
Test plan, test
Manuals
Installation
Report
35. 35
The Functional Models System
extends
extends
Search
Seat
Sing up
Log in
Check seat
Payment of
seat
Reserved
seat
print
logout
customer
verify
acknowled
gement
Add vehicle
Add driver
Generate report
admin
36. 36
Designing Approach
Top down design:
The TOP DOWN approach starts from the highest level component of the hierarchy and
proceed through to lower levels. A top down design approach start by the major
component of the system. Decomposing them into their lower level component and
iterative until the desired label of detail is achieved. Top down design method is in some
form of step wise refinement. Starting from a abstract design in each step the design is
refine to more concrete level, until we reach a level were no more refinement is needed.
A system consists of components, which have components of their own;
indeed a system is a hierarchy of components. The highest level component correspond to
the total system. The top down approach from the highest level component of hierarchy
and proceeds through to lower levels. By contrast a bottom up approach starts with the
lowest level component of the hierarchy and proceeds through progressively higher levels
to the top level components.
The top down approach has been promulgated by many researches and has
been found to be extremely useful for design. Most design methodologies are based on
the top down approach.
A top down approach suitable only if the specifications of the systems are
clearly known and the system development is from scratch. However, if a system is to be
built from an existing system, a bottom approach is more suitable, as it starts from some
existing components
37. 37
Table Schema
Table :-Bus Detail
Column
name
Type Computed Length Prec Scale Null able Trim
Trailing
Blank
Fixed len
null
source
Bus no. Int No 4 10 0 no (n/a) (n/a)
Bus reg.
no.
varchar No 50 yes No Yes
Bus type Varchar No 20 Yes no Yes
Bus
capacity
Small int No 2 5 0 Yes (n/a) (n/a)
Table:- City Detail
Column
name
Type Computed Length Prec Scale Null
able
Trim
Trailing
Blank
Fixed
lennull
source
City code Int no 4 10 0 no (n/a) (n/a)
City detail Varchar No 50 yes no yes
38. 38
Table:- User Detail
Column
name
Type Computed Length Prec Scale Null
able
Trim
Trailing
Blank
Fixed
lennull
source
User id Bright No 8 no (n/a) (n/a)
First name Varchar No 100 Yes No Yes
Lastname Varchar No 100 Yes No Yes
Username Varchar No 100 Yes No Yes
password Varchar No 100 Yes No Yes
User Dob Datetime No 8 Yes (n/a) (n/a)
User
gender
Varchar No 15 Yes No Yes
Designation Varchar No 100 Yes No Yes
Email Varchar No 100 Yes No Yes
Contacts
no.
Bigint No 8 Yes (n/a) (n/a)
Address Varchar No 100 Yes No Yes
Group id Int No 4 10 0 Yes (n/a) (n/a)
Jin date Datetime No 8 yes (n/a) (n/a)
40. 40
DATA FLOW DIAGRAM
Data Flow Diagramming is a means of representing a system at any level of details with a
graphic network of symbols showing data flows, data stores, data processes, and data
source/destination.
The data flow diagram is analogous to a road map. It is a network model of all
possibilities with different details shown on different hierarchical levels. This processes of
representing different details level is called âlevelingâ or âportioningâ by some data flow
diagram advocates. Like a road map, there is no start point or stop point, no time or timing, or
steps to get somewhere, we just know that the data path must exist because at some point it will
be needed. A road map has shown all existing or planned roads because the road is needed.
Details that are not shown on different levels of the data flow diagram such as volumes, timing,
frequency etc. is shown on supplementary diagrams are in the data dictionary. For example, data
store contents may be shown in the data dictionary.
Data Flow Diagram (DFD) uses a number of symbols to represent the systems.
Data Flow Diagram also known as âBubble Chartâ is used to clarify system requirements and
identifying the major transformation that will become programs in system design. So it is the
starting point of the design phase that functionally decomposes the requirements specifications
down to the level of details.
īˇ A square shows the entity.
īˇ A circle shows the process.
41. 41
īˇ An open Ended Rectangle shows the data store.
īˇ An arrow shows the data flow.
īˇ The DFD can be up to several levels. The 0 level DFD states the flow of data in the
system as seen from the outward in each module.
īˇ The first level DFD shows more detail, about the single process of the 0 level DFD.
īˇ The second level DFD can show even more details and so on.
Features of DFD
īˇ The exceptional simplicity of the DFD zymology is one reason why data oriented
analysis techniques is the most widely used.
īˇ The data flow diagram is a graphical tool that can be very valuable during the system
analysis.
īˇ The DFD depicts information flow without explicit notation of control.(e.g. conditions of
loops).
īˇ The level 0 data flow diagram should depict the software as a single bubble.
īˇ Primary input/output files should be maintained.
īˇ One bubble at a time should be refined.
There is a natural tendency to over complicate the DFD. This happens when we try to show too
many details early.
42. 42
Symbols of DFD:-
The Data Flow Diagram shows the flow of data. It is generally made of symbols given below
The various symbols used for DFD are:-
īˇ Square
A square defines a source (originator) or destination of system data.
īˇ Arrow
An arrow identifies data flow-data in motion. It is a pipeline throw which information
flows.
īˇ Circle
A circle or a bubble represents is a process that transforms incoming data flow into
outgoing data flow. Circle basically represents a process.
43. 43
īˇ Open Rectangle
An open Rectangle is data storeâdata at rest, or temporary repository of data. Open
rectangle basically denotes data storage.
Decision- indicate a point where the outcome of a decision indicate the next step.
Input or output operation show input and output from a process
Data base â A step that result in information begin stored.
44. 44
DATA FLOW DIAGRAM â0âLevel
STATICS
QUERY
UPDATE
STSTICS
QUERY
GENERATE INDENT
STSTICS
BUS
TICKET
BOOKING
REGISTERED
USER
GUEST USER
ADMIN
INDENT
ACCOUNT
DEPARTEMENT
45. 45
1ST
LEVEL DFD
Id password and type
Maintained Data
Data will check data retrieved form
Show main form Out
User command
User Id
password
And type
If valid then
Main form
47. 47
DATA FLOW CHART
YES
start
Load main value
Enter valid password
Enter to admin
Enter detail for the task
Verify detail
Anothertask
Display report
Update detail and process
report
Print report
Exit
Data base
49. 49
Guidelines For Drawing ER Diagram-
When gathering information I have to-
ī Identify the entity in the system
ī Identify the attributes of the system
ī Identify the relationship between the entity
Entity-
Entity is the distinguishable object that has a conceptual or physical existence in the
system. Each entity has some specific attributes. An entity is a fundamental thing of an
organization and it has its own identity, which distinguishes it from other entity. An
entity type is the description of all entities to which a common definition and common
relationship and attribute apply.
Relationship-
A relationship is an âassociation among entitiesâRelation is the link between objects
through which a entity is related with other entity.
Attribute-
An attribute is the property or characteristic of an entity. Each entity type has a set of
attribute associated with it.
50. 50
Notation of ER Diagram-
The overall logical structure of a database can be expressed graphically by ER Diagram.
These are the notations used in ER Diagram-
RECTANGLE- It represents the entity set.
ELLIPES- It represents attributes.
DIAMONDS- It represents relationship among entities.
LINES- It links attribute to entity and entity set to relationship.
ER Diagrams Usage
While able to describe just about any system, ER diagrams are most often associated with
complex databases that are used in software engineering and IT networks. In particular,
ER diagrams are frequently used during the design stage of a development process in
order to identify different system elements and their relationships with each other. For
example, an inventory software used in a retail shop will have a database that monitors
elements such as purchases, item, item type, item source and item price.
51. 51
ER Diagram Templates
Below are some ER diagram templates so you can get started quickly. Clicking on the image and
in the new page that opens click the âUse as Templateâ button.
Benefits of ER diagrams
ER diagrams constitute a very useful framework for creating and manipulating databases. First,
ER diagrams are easy to understand and do not require a person to undergo extensive training to
be able to work with it efficiently and accurately. This means that designers can use ER diagrams
to easily communicate with developers, customers, and end users, regardless of their IT
proficiency. Second, ER diagrams are readily translatable into relational tables which can be
used to quickly build databases. In addition, ER diagrams can directly be used by database
developers as the blueprint for implementing data in specific software applications. Lastly, ER
diagrams may be applied in other contexts such as describing the different relationships and
operations within an organization.
52. 52
ER DIAGRAM OF ONLINE BUS TICKET BOOKING
BUS
Bus no. source
Departure
time
Destination
BOOKING
Ticket
Ticket No.
Source
Age
Sex
Departure
time
Date of
journey
53. 53
Bibliography & References
With tremendous advances in software technology, it is very essential for software
to be up to date and user interactive keeping this fact in view, I have tried my best to keep
it to such level as of todayâs. So, to make it to this level, I had to consult many books and
media. These are the list of books and media, I have consulted:-
BOOKS
ī âIntroduction to Cloud Computing Architectureâ 1st Edition June 2009, Sun
Microsystems Inc.
ī Pankaj Jalote, âAn approach to software engineeringâ, third edition, 2005, Narosa
Publishing House.
ī Leon &Leon, âDatabase Management Systemâ, Vikas Publishing House.
ī Elmasri , Navathe,â Fundamentals of database systems â,addition Wesley
WEBSITES:-
1. www.google.co.in
2. www.wikipedia.com