Railway e Ticketing
Content
JAMIA HAMDARD
RAILWAY E-TICKETING(RESERVATION)
SOFTWARE ENGINEERING LAB
BTCS 407
SUBMITTED TO –
ANIL KUMAR MAHTO
SUBMITTED BY GROUP –
IDRISH KAPADIA (2013-310-020)
KASHISH AHUJA (2013-310-021)
MANISH JOSHI (2013-310-022)
1. PROJECT OVERVIEW
Purpose
Operator
Assumption
Overview
2. SYSTEM ANALYSIS
Initial investigation
Software attributes
Feasibility analysis
3. PROJECT PLANNING
SOFTWARE PROCESS DEVELOPMENT MODEL
Water fall model
4. SOFTWARE DESIGNING
Objective of s/w designing
S/W design concepts
5. SOFTWARE PROJECT PLANNING
Objective
Activities
SDLC
6. PROGRAMMING LANGUAGE
About VB.NET
About MS Accesss
7. SYSTEM REQUIREMENT
Hardware requirement
Software requirement
8. DIAGRAMS
Data flow diagram (DFD)
9. FORM DESIGNING
Schreen short
Coding
Data base
10.
TESTING
Purpose
Principals of s/w testing
11.
PROJECT FUTURE SCOPE
PROJECT OVERVIEW :PURPOSE :THE PURPOSE OF THIS APPLICATION ARE AS FOLLOWS :Provides complete railway database solution, including
passenger
Train, seat database, storing of train seat list & status. Complete
data based
administration
Generate various reports for administration like, Total /members
registered for
passenger, no of available seat,
OPERATOR
reservation form
Train list form
Fare data base form
Train status form
ADMIN
1)CAN READ AND WRITE INFORMATION ABOUT ANY
MEMBER.
2 )System has powerful logical access management in place,
each user must
be
identified by login id and strict password policy is applied to
secure
the system
Technology used :-
1. FRONT END : VB.NET
2. BACK END
: MS-access
OPERATOR:
1)THIS APPLICATION IS USED TO CONVERT THE MANUAL
AAPLICATION TO THE
ONLINE APPLICATION.
2)CUSTOMIZED DATA WILL BE USED IN THIS APPLICATION.
3)USER DOES NOT HAVE RIGHT TO ENTER INFORMATION ABOUT
BOOKS.
OVERVIEW :PROJECT IS RELATED TO RAILWAY MANAGEMENT WHICH
PROVIDES READING SERVICES TO ITS
MEMBERS. ANY PERSON CAN BECOME SEE OF THE RAILWAY BY
FILLING THE PRESCRIBED FORM.
THEY CAN GET THE RESERVATION.
FUNCTIONALITY :(a) ONLINE RESERVATION
(b) SEE TRAIN LIST
(c) GET FARE LIST
SYSTEM ANALYSIS
Initial investigation :This was the first phase and consisted of a brief survey of
areas involved and
resulted in taking the next phase . It was subdived into a
preliminary investigation
followed by a more detailed feasibility study .
The objectives of the phases were :
1. To determine the feasibility of computerization of this
website.
2. To define clearly the objective , scope and limitation of the
project.
3. To establish a good working relation between the various
developers.
4. To identify likely benefits this should accrue from the
introduction of the
website. s/w system attributes:(a)Realibility =- The system is realiable enough as the
database permanently stored and
backups can be kept easily , as well as the hard copies of
various reports also plays
major roles here.
(b)Availability =- The system should be available all the time as
and when required .The
availibility may be complete for administrator or partial for
others.
(c)Maintainability =- The system should be easy to maintain for
the administrator .
(d)Scalability =- The system should be easy to extend ,i.e. new
features can be easily added ,
for future extension.
(e)Security =- The system is secure enough , as limited
peivilages are given to other . They
cannot make any modification to database.
FEASIBILITY ANALYSIS :Feasibility is the determination of wheather or not a project is
worth . The process following
in making this determination is called “FEASIBILITY STUDY”.A
feasibility study is conducted
to select the best system that meets performance
requirements.Once it has been
determined that a project is feasible , the analyst can go ahead
and prepare the project
speacification which finalizes project requirements.
The feasibility of the system developed has been discussed in
the following points :
1. The system being developed in using VB.NET as a front end
tool & MS ACCESS
Server as a back end tool.
2. The developed system does not require any special trained
users since it
offers a very user friendly environment and online help.
3. Advanced security measures are taken in the hotel
management system to
prevent unathorized access ,malicious destruction of data .
4. Internet capabilities make it easy to provide access to
documents and
applications accros the internet from within the application. 5.
There is no direct cost since the developed system does not
require any
special hardware eg. Dedicated computer system.
S/W PROCESS DEVELOPMENT MODEL:1. Objectives of s/w designing :Identify different types of software, based on the usage
Show differences between design and coding.
Define concepts of structured programming.
Illustrate some basic design concepts.
See how to design for testability and maintainability.
Introduce some formal design notations.
1. Software design concept :The design concepts provide the software designer with a
foundation from which
more sophisticated methods can be applied. A set of fundamental
design concepts
has evolved.
They are:
1. Abstraction - Abstraction is the process or result of
generalization by reducing
the information content of a concept or an observable
phenomenon, typically in
order to retain only information which is relevant for a particular
purpose.
2. Refinement - It is the process of elaboration. A hierarchy is
developed by
decomposing a macroscopic statement of function in a stepwise
fashion until
programming language statements are reached. In each step, one
or several
instructions of a given program are decomposed into more
detailed instructions.
Abstraction and Refinement are complementary c
3. Modularity - Software architecture is divided into components
called modules.
4. Software Architecture - It refers to the overall structure of the
software and the
ways in which that structure provides conceptual integrity for a
system. A good
software architecture will yield a good return on investment with
respect to the
desired outcome of the project, e.g. in terms of performance,
quality, schedule
and cost.
5. Control Hierarchy - A program structure that represents the
organization of a
program component and implies a hierarchy of control. 6.
Structural Partitioning - The program structure can be divided
both horizontally
and vertically. Horizontal partitions define separate branches of
modular
hierarchy for each major program function. Vertical partitioning
suggests that
control and work should be distributed top down in the program
structure.
7. Data Structure - It is a representation of the logical relationship
among
individual elements of data.
8. Software Procedure - It focuses on the processing of each
modules individually
9. Information Hiding - Modules should be specified and designed
so that
information contained within a module is inaccessible to other
modules that
have no need for such information.
SOFTWARE PROJECT PLANNING :Project Planning is an aspect of Project Management that focuses
a lot on Project
Integration. The project plan reflects the current status of all
project activities and is used to
monitor and control the project.
Project Planning helps in : - Facilitating communication
- Monitoring/measuring the project progress, and
- Provides overall documentation of
assumptions/planning decisions
Typically Project Planning can include the following types of
project Planning: 1) Project Scope Definition and Scope Planning
2) Project Activity Definition and Activity Sequencing
3) Time, Effort and Resource Estimation
4) Risk Factors Identification
5) Cost Estimation and Budgeting
6) Organizational and Resource Planning
7) Schedule Development
8) Quality Planning
9) Risk Management Planning
10) Project Plan Development and Execution
11) Performance Reporting
12) Planning Change Management
13) Project Rollout Planning
OBJECTIVES OF PROJECT PLANNING :Objectives set the realistic targets to achieve during the project.
You should use best
practice in project management and set ‘SMART’ objectives that
are:
1- Specific Be clear about what will be achieved
2- Measurable Quantify results and measure when they have
been achieved
3- Achievable Ensure they can be achieved
4- Realistic Can be attained with within project resources
5- Timed Can be attained within a specified timescale.
ACTIVITIES OF PROJECT PLANNING :The input to the planning activity is the requirement specification
& the output
is the project plan ie. , planning activities are:1. Cost estimation
2. Schedule &milestones
3. Staffing personnel plan
4. S/W quality assurance plans (SQA)
5. Configuration management plans
6. Project monitoring plans
7. Risk management
Flow chart:
A flowchart is a type of diagram that represents an algorithm or
process,
showing the steps as boxes of various kinds, and their order by
connecting these with arrows. This diagrammatic representation
can
give a step-by-step solution to a given problem. Process
operations are
represented in these boxes, and arrows connecting them
represent flow
of control. Data flows are not typically represented in a flowchart,
in
contrast with data flow diagrams; rather, they are implied by the
sequencing of operations. Flowcharts are used in analyzing,
designing,
documenting or managing a process or program in various fields.
A typical definition of "Flow Chart" usually reads something like...
A flow chart is a graphical or symbolic representation of a
process. Each
step in the process is represented by a different symbol and
contains a
short description of the process step. The flow chart symbols are
linked
together with arrows showing the process flow direction.
Different flow chart symbols have different meanings. The most
common
flow chart symbols are:
1. Terminator: An oval flow chart shape indicating the start or end
of
the process.
2. Process: A rectangular flow chart shape indicating a normal
process
flow step.
3. Decision: A diamond flow chart shape indication a branch in
the
process flow.
4. Connector: A small, labeled, circular flow chart shape used to
indicate a jump in the process flow.
5. Data: A parallelogram that indicates data input or output (I/O)
for a
process.
6. Document: used to indicate a document or report (see image
in
sample flow chart below).
Software development life cycle (SDLC) :The Systems development life cycle (SDLC), or Software
development
process in systems engineering, information systems and
software engineering,
is a process of creating or altering information systems, and the
models
and methodologies that people use to develop these systems. In
software
engineering, the SDLC concept underpins many kinds of software
development
methodologies. These methodologies form the framework for
planning and
controlling the creation of an information system: the software
development
process.
The SDLC is a process used by a systems analyst to develop an
information system,
training, and user (stakeholder) ownership. Any SDLC should
result in a high quality
system that meets or exceeds customer expectations, reaches
completion within
time and cost estimates, works effectively and efficiently in the
current and
planned Information Technology infrastructure, and is inexpensive
to maintain and
cost-effective to enhance. Computer systems are complex and
often (especially with
the recent rise of service-oriented architecture) link multiple
traditional systems
potentially supplied by different software vendors. To manage this
level of
complexity, a number of SDLC models or methodologies have
been created, such as
"waterfall"; "spiral; "Agile software development"; "rapid
prototyping";
"incremental"; and "synchronize and stabilize".
system requirements:
• 500MHz or faster 32-bit or 64-bit processor
• 256MB of RAM
• 2GB available hard disk space (32-bit) or 20GB (64-bit)
• 1024x768 resolution monitor
• Windows XP with Service Pack 3, Windows Vista with SP1,
Windows Server
2003 R2 with MXXML 6.0, Windows Server 2008 (32-bit or 64-bit),
Windows
DATA FLOW DIAGRAM (DFD) :A data flow diagram (DFD) is a graphical representation of the
"flow" of data through
an information system, modeling its process aspects. Often they
are a preliminary step
used to create an overview of the system which can later be
elaborated.
A DFD shows what kinds of data will be input to and output from
the system, where the
data will come from and go to, and where the data will be stored.
It does not show
information about the timing of processes, or information about
whether processes will
operate in sequence or in parallel (which is shown on a flowchart.
Data flow diagrams were proposed by Larry Constantine, the
original
developer of structured design, based on Martin and Estrin's
"Data flow
graph" model of computation.Data flow diagrams are one of the
three
essential perspectives of the structured-systems analysis and
design method SSADM. The sponsor of a project and the end
users will need to be
briefed and consulted throughout all stages of a system's
evolution. With a
data flow diagram, users are able to visualize how the system will
operate,
what the system will accomplish, and how the system will be
implemented.
The old system's dataflow diagrams can be drawn up and
compared with the
new system's data flow diagrams to draw comparisons to
implement a more
efficient system. Data flow diagrams can be used to provide the
end user with
a physical idea of where the data they input ultimately has an
effect upon the
structure of the whole system from order.
RAILWAY E-TICKETING(RESERVATION)
SOFTWARE ENGINEERING LAB
BTCS 407
SUBMITTED TO –
ANIL KUMAR MAHTO
SUBMITTED BY GROUP –
IDRISH KAPADIA (2013-310-020)
KASHISH AHUJA (2013-310-021)
MANISH JOSHI (2013-310-022)
1. PROJECT OVERVIEW
Purpose
Operator
Assumption
Overview
2. SYSTEM ANALYSIS
Initial investigation
Software attributes
Feasibility analysis
3. PROJECT PLANNING
SOFTWARE PROCESS DEVELOPMENT MODEL
Water fall model
4. SOFTWARE DESIGNING
Objective of s/w designing
S/W design concepts
5. SOFTWARE PROJECT PLANNING
Objective
Activities
SDLC
6. PROGRAMMING LANGUAGE
About VB.NET
About MS Accesss
7. SYSTEM REQUIREMENT
Hardware requirement
Software requirement
8. DIAGRAMS
Data flow diagram (DFD)
9. FORM DESIGNING
Schreen short
Coding
Data base
10.
TESTING
Purpose
Principals of s/w testing
11.
PROJECT FUTURE SCOPE
PROJECT OVERVIEW :PURPOSE :THE PURPOSE OF THIS APPLICATION ARE AS FOLLOWS :Provides complete railway database solution, including
passenger
Train, seat database, storing of train seat list & status. Complete
data based
administration
Generate various reports for administration like, Total /members
registered for
passenger, no of available seat,
OPERATOR
reservation form
Train list form
Fare data base form
Train status form
ADMIN
1)CAN READ AND WRITE INFORMATION ABOUT ANY
MEMBER.
2 )System has powerful logical access management in place,
each user must
be
identified by login id and strict password policy is applied to
secure
the system
Technology used :-
1. FRONT END : VB.NET
2. BACK END
: MS-access
OPERATOR:
1)THIS APPLICATION IS USED TO CONVERT THE MANUAL
AAPLICATION TO THE
ONLINE APPLICATION.
2)CUSTOMIZED DATA WILL BE USED IN THIS APPLICATION.
3)USER DOES NOT HAVE RIGHT TO ENTER INFORMATION ABOUT
BOOKS.
OVERVIEW :PROJECT IS RELATED TO RAILWAY MANAGEMENT WHICH
PROVIDES READING SERVICES TO ITS
MEMBERS. ANY PERSON CAN BECOME SEE OF THE RAILWAY BY
FILLING THE PRESCRIBED FORM.
THEY CAN GET THE RESERVATION.
FUNCTIONALITY :(a) ONLINE RESERVATION
(b) SEE TRAIN LIST
(c) GET FARE LIST
SYSTEM ANALYSIS
Initial investigation :This was the first phase and consisted of a brief survey of
areas involved and
resulted in taking the next phase . It was subdived into a
preliminary investigation
followed by a more detailed feasibility study .
The objectives of the phases were :
1. To determine the feasibility of computerization of this
website.
2. To define clearly the objective , scope and limitation of the
project.
3. To establish a good working relation between the various
developers.
4. To identify likely benefits this should accrue from the
introduction of the
website. s/w system attributes:(a)Realibility =- The system is realiable enough as the
database permanently stored and
backups can be kept easily , as well as the hard copies of
various reports also plays
major roles here.
(b)Availability =- The system should be available all the time as
and when required .The
availibility may be complete for administrator or partial for
others.
(c)Maintainability =- The system should be easy to maintain for
the administrator .
(d)Scalability =- The system should be easy to extend ,i.e. new
features can be easily added ,
for future extension.
(e)Security =- The system is secure enough , as limited
peivilages are given to other . They
cannot make any modification to database.
FEASIBILITY ANALYSIS :Feasibility is the determination of wheather or not a project is
worth . The process following
in making this determination is called “FEASIBILITY STUDY”.A
feasibility study is conducted
to select the best system that meets performance
requirements.Once it has been
determined that a project is feasible , the analyst can go ahead
and prepare the project
speacification which finalizes project requirements.
The feasibility of the system developed has been discussed in
the following points :
1. The system being developed in using VB.NET as a front end
tool & MS ACCESS
Server as a back end tool.
2. The developed system does not require any special trained
users since it
offers a very user friendly environment and online help.
3. Advanced security measures are taken in the hotel
management system to
prevent unathorized access ,malicious destruction of data .
4. Internet capabilities make it easy to provide access to
documents and
applications accros the internet from within the application. 5.
There is no direct cost since the developed system does not
require any
special hardware eg. Dedicated computer system.
S/W PROCESS DEVELOPMENT MODEL:1. Objectives of s/w designing :Identify different types of software, based on the usage
Show differences between design and coding.
Define concepts of structured programming.
Illustrate some basic design concepts.
See how to design for testability and maintainability.
Introduce some formal design notations.
1. Software design concept :The design concepts provide the software designer with a
foundation from which
more sophisticated methods can be applied. A set of fundamental
design concepts
has evolved.
They are:
1. Abstraction - Abstraction is the process or result of
generalization by reducing
the information content of a concept or an observable
phenomenon, typically in
order to retain only information which is relevant for a particular
purpose.
2. Refinement - It is the process of elaboration. A hierarchy is
developed by
decomposing a macroscopic statement of function in a stepwise
fashion until
programming language statements are reached. In each step, one
or several
instructions of a given program are decomposed into more
detailed instructions.
Abstraction and Refinement are complementary c
3. Modularity - Software architecture is divided into components
called modules.
4. Software Architecture - It refers to the overall structure of the
software and the
ways in which that structure provides conceptual integrity for a
system. A good
software architecture will yield a good return on investment with
respect to the
desired outcome of the project, e.g. in terms of performance,
quality, schedule
and cost.
5. Control Hierarchy - A program structure that represents the
organization of a
program component and implies a hierarchy of control. 6.
Structural Partitioning - The program structure can be divided
both horizontally
and vertically. Horizontal partitions define separate branches of
modular
hierarchy for each major program function. Vertical partitioning
suggests that
control and work should be distributed top down in the program
structure.
7. Data Structure - It is a representation of the logical relationship
among
individual elements of data.
8. Software Procedure - It focuses on the processing of each
modules individually
9. Information Hiding - Modules should be specified and designed
so that
information contained within a module is inaccessible to other
modules that
have no need for such information.
SOFTWARE PROJECT PLANNING :Project Planning is an aspect of Project Management that focuses
a lot on Project
Integration. The project plan reflects the current status of all
project activities and is used to
monitor and control the project.
Project Planning helps in : - Facilitating communication
- Monitoring/measuring the project progress, and
- Provides overall documentation of
assumptions/planning decisions
Typically Project Planning can include the following types of
project Planning: 1) Project Scope Definition and Scope Planning
2) Project Activity Definition and Activity Sequencing
3) Time, Effort and Resource Estimation
4) Risk Factors Identification
5) Cost Estimation and Budgeting
6) Organizational and Resource Planning
7) Schedule Development
8) Quality Planning
9) Risk Management Planning
10) Project Plan Development and Execution
11) Performance Reporting
12) Planning Change Management
13) Project Rollout Planning
OBJECTIVES OF PROJECT PLANNING :Objectives set the realistic targets to achieve during the project.
You should use best
practice in project management and set ‘SMART’ objectives that
are:
1- Specific Be clear about what will be achieved
2- Measurable Quantify results and measure when they have
been achieved
3- Achievable Ensure they can be achieved
4- Realistic Can be attained with within project resources
5- Timed Can be attained within a specified timescale.
ACTIVITIES OF PROJECT PLANNING :The input to the planning activity is the requirement specification
& the output
is the project plan ie. , planning activities are:1. Cost estimation
2. Schedule &milestones
3. Staffing personnel plan
4. S/W quality assurance plans (SQA)
5. Configuration management plans
6. Project monitoring plans
7. Risk management
Flow chart:
A flowchart is a type of diagram that represents an algorithm or
process,
showing the steps as boxes of various kinds, and their order by
connecting these with arrows. This diagrammatic representation
can
give a step-by-step solution to a given problem. Process
operations are
represented in these boxes, and arrows connecting them
represent flow
of control. Data flows are not typically represented in a flowchart,
in
contrast with data flow diagrams; rather, they are implied by the
sequencing of operations. Flowcharts are used in analyzing,
designing,
documenting or managing a process or program in various fields.
A typical definition of "Flow Chart" usually reads something like...
A flow chart is a graphical or symbolic representation of a
process. Each
step in the process is represented by a different symbol and
contains a
short description of the process step. The flow chart symbols are
linked
together with arrows showing the process flow direction.
Different flow chart symbols have different meanings. The most
common
flow chart symbols are:
1. Terminator: An oval flow chart shape indicating the start or end
of
the process.
2. Process: A rectangular flow chart shape indicating a normal
process
flow step.
3. Decision: A diamond flow chart shape indication a branch in
the
process flow.
4. Connector: A small, labeled, circular flow chart shape used to
indicate a jump in the process flow.
5. Data: A parallelogram that indicates data input or output (I/O)
for a
process.
6. Document: used to indicate a document or report (see image
in
sample flow chart below).
Software development life cycle (SDLC) :The Systems development life cycle (SDLC), or Software
development
process in systems engineering, information systems and
software engineering,
is a process of creating or altering information systems, and the
models
and methodologies that people use to develop these systems. In
software
engineering, the SDLC concept underpins many kinds of software
development
methodologies. These methodologies form the framework for
planning and
controlling the creation of an information system: the software
development
process.
The SDLC is a process used by a systems analyst to develop an
information system,
training, and user (stakeholder) ownership. Any SDLC should
result in a high quality
system that meets or exceeds customer expectations, reaches
completion within
time and cost estimates, works effectively and efficiently in the
current and
planned Information Technology infrastructure, and is inexpensive
to maintain and
cost-effective to enhance. Computer systems are complex and
often (especially with
the recent rise of service-oriented architecture) link multiple
traditional systems
potentially supplied by different software vendors. To manage this
level of
complexity, a number of SDLC models or methodologies have
been created, such as
"waterfall"; "spiral; "Agile software development"; "rapid
prototyping";
"incremental"; and "synchronize and stabilize".
system requirements:
• 500MHz or faster 32-bit or 64-bit processor
• 256MB of RAM
• 2GB available hard disk space (32-bit) or 20GB (64-bit)
• 1024x768 resolution monitor
• Windows XP with Service Pack 3, Windows Vista with SP1,
Windows Server
2003 R2 with MXXML 6.0, Windows Server 2008 (32-bit or 64-bit),
Windows
DATA FLOW DIAGRAM (DFD) :A data flow diagram (DFD) is a graphical representation of the
"flow" of data through
an information system, modeling its process aspects. Often they
are a preliminary step
used to create an overview of the system which can later be
elaborated.
A DFD shows what kinds of data will be input to and output from
the system, where the
data will come from and go to, and where the data will be stored.
It does not show
information about the timing of processes, or information about
whether processes will
operate in sequence or in parallel (which is shown on a flowchart.
Data flow diagrams were proposed by Larry Constantine, the
original
developer of structured design, based on Martin and Estrin's
"Data flow
graph" model of computation.Data flow diagrams are one of the
three
essential perspectives of the structured-systems analysis and
design method SSADM. The sponsor of a project and the end
users will need to be
briefed and consulted throughout all stages of a system's
evolution. With a
data flow diagram, users are able to visualize how the system will
operate,
what the system will accomplish, and how the system will be
implemented.
The old system's dataflow diagrams can be drawn up and
compared with the
new system's data flow diagrams to draw comparisons to
implement a more
efficient system. Data flow diagrams can be used to provide the
end user with
a physical idea of where the data they input ultimately has an
effect upon the
structure of the whole system from order.
