c

c
SOFTWARE REQUIREMENT
SPECIFICATIONS

FOR

RAILWAY RESERVATION SYSTEM

SUBMITTED TO:

Mrs. ANKITA BANSAL

Professor of
Udhna Academy College of Computer Application & I.T.

VEER NARMAD SOUTH UNIVERSITY, SURAT

SUBMITTED BY:

Unnati .R. Birade

Kanisha .A. Kabrawala

Roll no:

07
26
c
c
c
c
c
c
c
c
c
c
c

< <






c
c
c
c
c
c
c

 

c
A study or a project of this volume can never be an
outcome or a single person. We our indebted to our
subject teacher ’
 

 for being the epitome
of guidance during the entire project.

We are also thankful to our parents for their

encouragement. Without their help this project would not
have seen the light of day.

We are happy to present a vote of thanks to them for

their sincere advice and co-operation that they have lent
us unconditionally.

< <






c
c
c

CERTIFICATE

ñhis is to certify that the above declaration made by

 
    and  
  is true to the
best of my knowledge and belief.

Date: - 4th October, 2010

Place: -SURAñ

Prof. Ankita Bansal

Professor,
Udhna Academy College of Comp. Appl. & I.T.

c
c
c
c
c
c
c
c
< <






c
c
c
< <
c

c
c
c

<c

I. OPERATING SYSTEM:
Window XP

II. PROCESSOR:
1. PENTIUM (ANY) OR AMD
ATHALON (3800+- 4200+ DUAL
CORE)

III. MOTHERBOARD:
1.845 OR 915,995 FOR PENTIUM
0R MSI K9MM-V VIA
K8M800+8237R PLUS CHIPSET
FOR AMD ATHALON
IV. RAM: 512MB+

V. Hard disk:
Sata 40 GB or above

VI. CD/DVD r/w multi drive combo

VII. FLOPPY DRIVE 1.44 MB

VIII. MONITOR 14.1 or 15 -17 inch

IX. Key board and mouse

X. Printer

<
c

<
c

coffice XPc

< <






c
c
c

 c<
c

< <
 c

c
c

< <






c
c
c
ADVANTAGES OF RAILWAY
RESERVATION SYSTEM
c
cccccccc©ow one can easily plan the journey comfortably as
the process is efficient and fast with being easy to access.
Reservations can be made through the Indian railways site
or at the ample reservation centers all over the country.
Also now there are authorized agencies which provide
reservation facility on behalf of India railways and without
waiting in long line one can easily book a ticket. ñhe
booking is done through an Eñicket issue which has a P©R
number of which one has to take a print and just have to
show at the station.
It not only provides reservation but cancellation can
also be done through this system at ease and one can use
a credit card to complete the process. ñhis being a big step
in terms of improvement in the railway system it is widely
accepted across the country.

PROPOSED SYSTEM
one cannot afford to rely on the fallible
cccccccccccccccccñoday
human beings of be really wants to stand against today͛s
merciless competition where not to wise saying ͞to err is
human͟ no longer valid, it͛s outdated to rationalize your
mistake. So, to keep pace with time, to bring about the
best result without malfunctioning and greater efficiency
so to replace the unending heaps of flies with a much
sophisticated hard disk of the computer. One has to use
the data management software. Software has been an
< <






c
c
c
ascent in atomization various organizations. Many
software products working are now in markets, which
have helped in making the organizations work easier and
efficiently. Data management initially had to maintain a lot
of ledgers and a lot of paper work has to be done but now
software product on this organization has made their work
faster and easier. ©ow only this software has to be loaded
on the computer and work can be done.
ñhis prevents a lot of time and money. ñhe work
becomes fully automated and any information regarding
the organization can be obtained by clicking the button.
Moreover, now it͛s an age of computers of and
automating such an organization gives the better look.

SYSTEM DEVELOPMENT LIFE CYCLE

systems development life cycle is a
ccccccccccccccccccccccccccccccccñhe
project management technique that divides complex
projects into smaller, more easily managed segments or
phases. Segmenting projects allows managers to verify the
successful completion of project phases before allocating
resources to subsequent phases. Software development
projects typically include initiation, planning, design,
development, testing, implementation, and maintenance
phases.
However, the phases may be divided differently depending
on the organization involved. For example, initial project
activities might be designated as request, requirements-
definition, and planning phases, or initiation, concept-
development, and planning phases. End users of the
< <






c
c
c
system under development should be involved in
reviewing the output of each phase to ensure the system
is being built to deliver the needed functionality.

PHASES OF SYSTEM DEVELOPMENT

LIFE CYCLE

Initiation Phase

ñhe Initiation Phase begins when a business sponsor

identifies a need or an opportunity.
ñhe purpose of the Initiation Phase is to:

< <






c
c
c
ëc Identify and validate an opportunity to improve
business accomplishments of the organization or a
deficiency related to a business need.
ëc Identify significant assumptions and constraints on
solutions to that need.
ëc Recommend the exploration of alternative concepts
and methods to satisfy the need including
questioning the need for technology, i.e., will a
change in the business process offer a solution?
ëc Assure executive business and executive technical
sponsorship.
ñhe Sponsor designates a Project Manager and
the business need is documented in a Concept
Proposal. ñhe Concept Proposal includes information
about the business process and the relationship to
the Agency/Organization Infrastructure and the
Strategic Plan. A successful Concept Proposal results
in a Project Management Charter which outlines the
authority of the project manager to begin the project.
Careful oversight is required to ensure projects
support strategic business objectives and resources are
effectively implemented into an organization's enterprise
architecture. ñhe initiation phase begins when an
opportunity to add, improve, or correct a system is
identified and formally requested through the
presentation of a business case. ñhe business case should,
at a minimum, describe a proposal͛s purpose, identify
expected benefits, and explain how the proposed system
supports one of the organization͛s business strategies. ñhe
< <






c
c
c
business case should also identify alternative solutions and
detail as many informational, functional, and network
requirements as possible.

ccSystem Concept
Development Phase
c
c
ñhe System Concept Development Phase begins after
a business need or opportunity is validated by the
Agency/Organization Program Leadership and the
Agency/Organization CIO.
ñhe purpose of the System Concept Development Phase is
to:
ëc Determine the feasibility and appropriateness of the
alternatives
ëc Identify system interfacesc
ëc Identify basic functional and data requirements to
satisfy the business need.
ëc Establish system boundaries identify goals,
objectives, critical success factors, and performance
measures.
ëc Evaluate costs and benefits of alternative approaches
to satisfy the basic functional requirements.
ëc Assess project risks.
ëc Identify and initiate risk mitigation actions, and
ëc Develop high-level technical architecture, process
models, data models, and a concept of operations.
< <






c
c
c
ñhis phase explores potential technical solutions
within the context of the business need. It may
include several trade-off decisions such as the
decision to use COñS software products as opposed
to developing custom software or reusing software
components, or the decision to use an incremental
delivery versus a complete, onetime deveployment.
Construction of executable prototypes is encouraged
to evaluate technology to support the business
process.
ñhe System Boundary Document serves as
an important reference document to support the
Information ñechnology Project Request (IñPR)
process. ñhe IñPR must be approved by the State CIO
before the project can move forward.
c
c
c
c
c
c
c

< <






c
c
c

PICTORIAL
REPRESENTATION OF
SDLC:-
c
c
c
c

Requirements Analysis Phase

ñhis phase formally defines the detailed functional
user requirements using high-level requirements identified
in the Initiation, System Concept, and Planning phases. It
also delineates the requirements in terms of data, system
performance, security, and maintainability requirements
for the system. ñhe requirements are defined in this phase
to a level of detail sufficient for systems design to proceed.
ñhey need to be measurable, testable, and relate to the
< <






c
c
c
business need or opportunity identified in the Initiation
Phase. ñhe requirements that will be used to determine
acceptance of the system are captured in the ñest and
Evaluation Master Plan.
c
ñhe purposes of this phase are to:
ëc Further define and refine the functional and data
requirements and document them in the
Requirements Document,
ëc Complete business process reengineering of the
functions to be supported (i.e., verify what
information drives the business process, what
information is generated, who generates it, where
does the information go, and who processes it),
ëc Develop detailed data and process models (system
inputs, outputs, and the process.
ëc Develop the test and evaluation requirements that
will be used to determine acceptable system
performance.

ccDesign Phase
ñhe design phase involves converting the
informational, functional, and network requirements
identified during the initiation and planning phases into
unified design specifications that developers use to script
programs during the development phase. Program designs
are constructed in various ways. Using a top-down
approach, designers first identify and link major program

< <






c
c
c
components and interfaces, then expand design layouts as
they identify and link smaller subsystems and connections.
Using a bottom-up approach, designers first identify and
link minor program components and interfaces, then
expand design layouts as they identify and link larger
systems and connections.
Contemporary design techniques often use
prototyping tools that build mock-up designs of items such
as application screens, database layouts, and system
architectures. End users, designers, developers, database
managers, and network administrators should review and
refine the prototyped designs in an iterative process until
they agree on an acceptable design. Audit, security, and
quality assurance personnel should be involved in the
review and approval process.
During this phase, the system is designed to satisfy
the functional requirements identified in the previous
phase. Since problems in the design phase could be very
expensive to solve in the later stage of the software
development, a variety of elements are considered in the
design to mitigate risk. ñhese include:

ëc Identifying potential risks and defining mitigating

design features.
ëc Performing a security risk assessment.
ëc Developing a conversion plan to migrate current data
to the new system.
ëc Determining the operating environment.

< <






c
c
c
ëc Defining major subsystems and their inputs and
outputs.
ëc Allocating processes to resources.
ëc Preparing detailed logic specifications for each
software module.
ñhe result is a draft System Design Document which
captures the preliminary design for the system. Everything
requiring user input or approval is documented and
reviewed by the user. Once these documents have been
approved by the Agency CIO and Business Sponsor, the
final System Design Document is created to serve as the
Critical/Detailed Design for the system.
ñhis document receives a rigorous review by Agency
technical and functional representatives to ensure that it
satisfies the business requirements. Concurrent with the
development of the system design, the Agency Project
Manager begins development of the Implementation Plan,
Operations and Maintenance Manual, and the ñraining
Plan.

Development Phase
ñhe development phase involves converting
design specifications into executable programs. Effective
development standards include requirements that
programmers and other project participants discuss design
specifications before programming begins. ñhe procedures
< <






c
c
c
help ensure programmers clearly understand program
designs and functional requirements.
Programmers use various techniques to develop
computer programs. ñhe large transaction-oriented
programs associated with financial institutions have
traditionally been developed using procedural
programming techniques. Procedural programming
involves the line-by-line scripting of logical instructions
that are combined to form a program
Effective completion of the previous stages is a key
factor in the success of the Development phase.
ñhe Development phase consists of:
ëc ñranslating the detailed requirements and design into
system components.
ëc ñesting individual elements (units) for usability.
ëc Preparing for integration and testing of the Iñ system.

c Integration and Test Phase

ccccccccSubsystem integration, system, security, and user
acceptance testing is conducted during the integration and
test phase. ñhe user, with those responsible for quality
assurance, validates that the functional requirements, as
defined in the functional requirements document, are
satisfied by the developed or modified system. OIñ
Security staff assesses the system security and issue a
security certification and accreditation prior to
installation/implementation. Multiple levels of testing are
performed, including:
< <






c
c
c
ëc ñesting at the development facility by the contractor
and possibly supported by end users.
ëc ñesting as a deployed system with end users working
together with contract personnel.
ëc Operational testing by the end user alone performing
all functions.
Requirements are traced throughout testing,
a final Independent Verification & Validation evaluation is
performed and all documentation is reviewed and
accepted prior to acceptance of the system.

ccccc Implementation Phase

ñhis phase is initiated after the system has been
tested and accepted by the user. In this phase, the system
is installed to support the intended business functions.
System performance is compared to performance
objectives established during the planning phase.
Implementation includes user notification, user training,
installation of hardware, installation of software onto
production computers, and integration of the system into
daily work processes. ñhis phase continues until the
system is operating in production in accordance with the
defined user requirements.

c
c

< <






c
c
c

cccccc Operations and Maintenance

Phase:
ñhe system operation is ongoing. ñhe system is
monitored for continued performance in accordance with
user requirements and needed system modifications are
incorporated. Operations continue as long as the system
can be effectively adapted to respond to the organization͛s
needs. When modifications or changes are identified, the
system may reenter the planning phase. ñhe purpose of
this phase is to:
ëc Operate, maintain, and enhance the system.
ëc Certify that the system can process sensitive
information.
ëc Conduct periodic assessments of the system to
ensure the functional requirements continue to be
satisfied.
ëc Determine when the system needs to be modernized,
replaced, or retired.

< <






c
c
c
SOFTWARE REQUIREMENT
SPECIFICATION
c
1. INTRODUCTION
c


cc


c 
 c
 c

c   c 
c c c c

cc  c c 
c
c
c
2. OVERALL DESCRIPTION



c 
c
c


c 
c
c



c c  c



c c



cc



c

 c
c
3. USER CLASS AND CHARACTERISTICS
c
4. OPERATING ENVIRONMENT
c
5. SOFTWARE CONSTRAINTS

6. USER DOCUMENTATION

7. EXTERNAL INTERFACE REQUIREMENTS



cc 
c


c c 
c


c c 
c
c
8. OTHER NON-FUNCTIONAL REQUIREMENTS



c
c c


c c c  c

< <






c
c
c

RAILWAY RESERVATION SYSTEMc

c
c
1. INTRODUCTION:
• • c

:
ccccc c cñhe purpose of this source is to describe the railway
reservation system which provides the train timing details, reservation,
billing and cancellation.
c
•  c 
c  c
´c Main headings: Bold
´c ©ot applicable
c
• c cccc
cccccñhe different types of readers are:
´c Customers
´c Developers
´c Management people.
c
• 

ccc
 c 
c
cccccIt consists of
´c ñrain details
´c Reservation form
´c Billing
´c Cancellation.
c
2. OVERALL DESCRIPTION:

 • c
 c

  c

It enables us to maintain the railway train details like their timings,
number of seat available and reservation billing and cancelling the tickets.
c
  c
 c c
It tells the short note about the product.
Ñ Ñ
cc
c
ccccccccccccccccccccccCustomers may view the train timing at a date their name
and number of tickets.
Ñ Ñ Ñ c
 c
< <






c
c
c
After checking the number of seats available the
customers reserve the tickets.
Ñ Ñ  c c
After reserving the required amount of tickets, the
customer paid the amount.
Ñ Ñ  c  c
cccc cccccccc cccccccccIf the customers want to cancel the ticket, then half of the
amount paid by the customer will be refunded to him.

 cc cc   c
´c nowledgeable user
´c ©o voice user
´c Expert user
c
 c
c 
c
ñhe OS types are
´c Windows ©ñ
´c Windows XP
´c Windows 98
´c Linux

 cc c

Designing -> Rational Rose
Developing -> Visual Basic
c
è cc 
c
´c USER MA©UAL:
Manual helps to understand the product details about
how to work.
´c ñUñORIALS:
For beginners use.
c
7. EXTERNAL INTERFACE REQUIREMENTS:

º • cc c

ccccceyboard and Mouse.
c
º  cc c

< <






c
c
c
´c Printer
´c ©ormal PC
c
º  cc c
´c Front end -> Visual Basic
´c Back end -> MS-Access
c
8. OTHER NON-FUNCTIONAL REQUIREMENTS:

 • c

 c
c
It is available during all 24 hours.
c
  cc
cc
´c Reliable
´c Available
´c Secure

c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c

< <






c
c
c
DATA FLOW DIAGRAM

Data Flow Diagram (DFD) is used widely for modeling

the requirement. ñhey have been used for many years
prior to the advent of computer. DFDs show the flow of
data through the system. ñhe system may be a company,
an organization, a set of procedural, a computer hardware
system, a software system, or any combination of the
preceding.

  

< <






c
c
c
:: CONTEXT DIAGRAM::
ñhe context diagram shows the interaction
between the external entities and the system. Here we
don͛t deal with the internal sub processes of the
system.
c

c
c
c
c
c
c
c
c

< <






c
c
c
LEVEL-1 DATA FLOW DIAGRAM:-
Here the internal sub processes of the system
and their interaction with the external entities is shown.

c
c

< <






c
c
c
Testing
c
Software ñesting is an empirical investigation
conducted to provide stakeholders with information about
the quality of the product or service under test, with
respect to the context in which it is intended to operate.
Software ñesting also provides an objective,
independent view of the software to allow the business to
appreciate and understand the risks at implementation of
the software. ñest techniques include, but are not limited
to, the process of executing a program or application with
the intent of finding software bugs. It can also be stated as
the process of validating and verifying that a software
program/application/product meets the business and
technical requirements that guided its design and
development, so that it works as expected and can be
implemented with the same characteristics.
Software testing, depending on the testing method
employed, can be implemented at any time in the
development process, however the most test effort is
employed after the requirements have been defined and
coding process has been completed.
c

Testing methods

Software testing methods are traditionally divided

into black box testing and white box testing. ñhese two
approaches are used to describe the point of view that a
test engineer takes when designing test cases.

< <






c
c
c
Black box testing
c
ccccccccccccccccccccccBlack
box testing treats the software as a "black
box," without any knowledge of internal implementation.
Black box testing methods include: equivalence
partitioning, boundary value analysis, all-pairs testing, fuzz
testing, model-based testing, traceability matrix,
exploratory testing and specification-based testing.
c
Specification-based testing
c
Specification-based testing aims to test the
functionality of software according to the applicable
requirements.[16] ñhus, the tester inputs data into, and
only sees the output from, the test object. ñhis level of
testing usually requires thorough test cases to be provided
to the tester, who then can simply verify that for a given
input, the output value (or behavior), either "is" or "is not"
the same as the expected value specified in the test case.
Specification-based testing is necessary, but it is
insufficient to guard against certain risks.

Advantages and Disadvantages

ccccccccccccccccccñhe black box tester has no "bonds" with
the code, and a tester's perception is very simple: a code
Æ
have bugs. Using the principle, "Ask and you shall
receive," black box testers find bugs where programmers
don't.  on the other hand, black box testing has been
said to be "like a walk in a dark labyrinth without a
flashlight," because the tester doesn't know how the
< <






c
c
c
software being tested was actually constructed. ñhat's why
there are situations when (1) a black box tester writes
many test cases to check something that can be tested by
only one test case, and/or (2) some parts of the back end
are not tested at all.
ñherefore, black box testing has the advantage of "an
unaffiliated opinion," on the one hand, and the
disadvantage of "blind exploring," on the other.
c
White box testing
ccccccccccccWhite box testing, by contrast to black box
testing, is when the tester has access to the internal data
structures and algorithms (and the code that implement
these)
ñypes of white box testing:-
ñhe following types of white box testing exist:
ëc Api testing - ñesting of the applicationcusing Public
and Private APIs.c
ëc Code coverage - creating tests to satisfy some criteria
of code coverage. For example, the test designer can
create tests to cause all statements in the program to
be executed at least once.
ëc Fault injection methods.
ëc Mutation testing methods.
ëc Static testing - White box testing includes all static
testing.

< <






c
c
c
Code completeness evaluation
cccccccccccWhite box testing methods can also be used to
evaluate the completeness of a test suite that was created
with black box testing methods. ñhis allows the software
team to examine parts of a system that are rarely tested
and ensures that the most important function points have
been tested.c
ñwo common forms of code coverage are:
ëc ¦  
 , which reports on functions
executed
ëc And
 Æ
 , which reports on the
number of lines executed to complete the test. ñhey
both return a coverage metric, measured as a
percentage

THANK YOU«..

< <






c