RAILWAY RESERVATION SYSTEM
Ex No:
IDENTITY A SOFTWARE THAT NEEDED TO BE
Date: DEVELOPED
Aim:
To write a needed to be developed for the railway reservation system.
Procedure:
Step1: Start->IBM software development platform->IBM relational software
architect->IBM
Step2: Select workspace->ok
Step3: File->new->project->UML project->next->give a project name->next.
Step 4: From template select analysis model->finish.
Step 5: Then in project explore->right click-> Analysis model->add diagram
->activity diagram.
Step 6: Select activity diagram then in screen editor drag and trag. activity and
actor From pallet and draw the class model
Result:
Ex No:
SOFTWARE REQUIREMENT SPECIFICATION
Date:
Aim:
To write software requirement specification for railway reservation system.
Software Requirement Specification:
1. Introduction:
1.1 Purpose:
The main objective of this document is to illustrate the requirements of
the project railway reservation System. The document gives the detailed
description of both functional and non-functional requirements proposed by the
client. The document is developed after a number of consultants with the client
and considering the complete requirements specifications of the given project.
The final product of the team will be meeting the requirements if this document.
1.2 Project Scope:
Technology has transformed many aspects of life in the 21st century,
including the way many of us make train reservations. For example, to make
ticketing more convenient for travelers, an online reservation system helps us in
booking tickets from the comfort of our homes or offices. While this is
convenient for most people, it has made things particularly easier for people
residing in remote locations.
It includes the following features which help it easy to use, understand and
modify it:
Automation of Reservation Status.
No need to do paper work.
To save the environment by using paper free processing
To increase efficiency and accuracy of the software
Management of online database
Management of online payment
This software package can be readily used by non-programming personal
avoiding human handled chance of error.
This project is used by three types of users:
Railway Administrator
Authorized railway reservation counters
Simplified management of passengers
Can be used online
Online payment system
Human friendly interface
The various advantages of using the online reservation system are as follows:
1) Convenient – You can book or cancel your tickets sitting in the
comfort of your home or office.
2) Saves Time and Effort - You can save the time needed to travel to the
railway reservation office and waiting in the queue for your turn.
3) Towards a greener planet – Instead of printing your ticket you can also
choose to travel with the soft copy of your booked ticket in your laptop or even
on your mobile Freight Revenue enhancement.
4) Passenger Revenue enhancement. Improved & optimized service
1) Convenient – You can book
or cancel your tickets sitting in
the comfort of your
home or office.
2) Saves Time and Effort -
You can save the time needed
to travel to the railway
reservation office and waiting
in the queue for your turn.
3) Towards a greener planet –
Instead of printing your ticket
you can also choose
to travel with the soft copy of
your booked ticket in your
laptop or even on your
mobile Freight Revenue
enhancement.
4) Passenger Revenue
enhancement. Improved &
optimized service.
1.4 Overview
The
1) Convenient – You can book
or cancel your tickets sitting in
the comfort of your
home or office.
2) Saves Time and Effort -
You can save the time needed
to travel to the railway
reservation office and waiting
in the queue for your turn.
3) Towards a greener planet –
Instead of printing your ticket
you can also choose
to travel with the soft copy of
your booked ticket in your
laptop or even on your
mobile Freight Revenue
enhancement.
4) Passenger Revenue
enhancement. Improved &
optimized service.
1.4 Overview
The
1.3 Overview:
Overview The sections of this document provide a general description,
including characteristics of the users of this project, the product’s hardware, the
functional design, data requirements design and constraints and assumptions
made while designing or development of a Railway Reservation System. It also
gives the user’s viewpoint of the product. Section 3 gives the detail of all type
of specific design of this product. It also includes the external, internal design
requirements and gives detailed description of functional design.
The sections of this document provide a general description, including
characteristics
of the users of this project, the product’s hardware, the functional
design, data
requirements design and constraints and assumptions made while
designing or
development of a Railway Reservation System. It also gives the user’s
viewpoint of
the product. Section 3 gives the detail of all type of specific design of this
product. It
also includes the external, internal design requirements and gives detailed
description
of functional design. However, Section 4 of this Document is of
completely
supporting information, same is the case with Last Section (Appendices). In
Other
words, below are the details of all the sections respectively:
2. General Description:
2.1 product perspective:
It enables us to maintain the railway train details like their timings,
number of seat available, reservation billing and cancelling the tickets
2.2 Functionality
The database should be act as an main role of the e-ticketing system it can
be booking the ticket in easy way.
2.3 Usability
The User interface makes the Credit Card Processing System to be
efficient.
2.4 Performance
It is of the capacities about which it can perform function for many users at
the same times efficiently that are without any error occurrence.
2.5 Reliability
The system should be able to process the user for their corresponding
request.
2.6 User Interfaces:
The system will give an assistance (clarification) link from each showed
HTML page to disclose how to utilize that page. The Web page of RRS will
allow total route, train choice, ticket reservation and ticket/train data queries
using input devices be it keyboard, mouse or touch screen in Smart-phones.
SOFTWARE INTERFACE
• Front End Client - The student and Controller online interface is built
using JSP and HTML The Exam Controller's local interface is built using Java.
• Web Server - Glassfish application server (SQL Corporation).
• Back End - SQL database.
HARDWARE INTERFACE
The server is directly connected to the client systems. The client systems
have access to the database in the server
Result:
Thus the SRS for railway reservation system has been written.
Ex No: IDENTIFYING USECASE AND DEVELOPED
Date: USECASE MODELS
Aim:
To identify the use case for railway reservation system.
Use case modelling description:
Use Case diagrams identify the functionality provided by the system (use
cases), the users who interact with the system (actors), and the association
between the users and the functionality. Use Cases are used in the Analysis
phase of software development to articulate the high-level requirements of the
system.
The primary goals of Use Case diagrams include:
• Providing a high-level view of what the system does.
• Identifying the users ("actors") of the system.
• Determining areas needing human-computer interfaces.
Use case diagram:
The functionality of a system can be described in a number of different use-
cases, each of which represents a specific flow of events in a system. It is a
graph of actors, a set of use-cases enclosed in a boundary, communication,
associations between the actors and the use-cases, and generalization among the
use-cases.
The passenger can view the status of the reserved tickets. So the passenger
can confirm his/her travel.
Basic Elements:
Actor
Actor is something with behavior, and is depicted using a stick figure.
Actors are not limited to humans. If a system communicates with another
application, the that application can also be considered an actor.
Use case
A Use case describes a sequence of actions that provide something of
measurable value to an actor. A use case is the functionality provided by the
system.
Association
Associations are used to link Actors with Use cases, and indicate that an
actor participate in the use case in some form. Associations are depicted by a
line connecting the actor and the use case.
USE CASE DIAGARM FOR RAILWAY RESERVATION SYSTEM
Result:
Thus the use case is identified and model was developed.
Ex No:
CLASS DIAGRAM
Date:
Aim:
To draw the class diagram for railway reservation system.
Class diagram:
A class diagram in the Unified Modeling Language (UML) is a type of
static structure diagram that describes the structure of a system by showing the
system's classes, their attributes and operations.
A Class diagram in the UML gives an overview of the system by showing
its classes and the relationships among them. Class diagrams are static-they
display what interacts but not what happens when they do interact.
Basic Elements
1) Class
A class is a set of objects that share a common structure and common
behavior. It’s represented by a rectangle divided into three parts: class name,
attributes and operations
2) Relationships
Relationships between classes are the connecting links. Relationships
between classes are generally represented in class diagrams by a line or an
arrow joining the two classes.
a) Dependency
If A depends on B then this is shown by a dashed arrow between
A and B.
3) Association
There is an association between two classes if an instance of one class
must know about the other in order to perform its work. An association
between A and B shown by a line joining two classes.
4) Aggregation
Aggregation is the association in which one class belongs to the
collection. If B aggregates A, then A is the part of B.
5) Generalization
Generalization is an inheritance link indicating one class is a super class
of the other. A generalization has a triangle pointing to the super class .An
inheritance relationship is indicated in the UML by an arrow with a triangular
arrow head pointing towards to the general.
Class diagram:
The online ticket reservation system makes use of the following classes:
1.Clerk
2.Railway system
3.Passenger
4.Train
5.Ticket
6.Payment
Result:
Thus the class diagram for railway reservation system is created and drawn.
Ex No:
SEQUENCE DIAGRAM AND COLLABORATION
Date: DIAGRAM
Aim:
To draw the sequence diagram and to draw a collaboration diagram.
Developing UML interaction diagram:
Introduction to UML interaction diagram
Interaction diagram describes how group of objects are collaborated with
each other.
Two types of Interaction diagrams
1) sequence diagram
2) COLLABORATION DIAGRAM
SEQUENCE DIAGRAM
Sequence diagram document the interactions between classes to achieve a
result, such as a use case. Because UML is designed for object-oriented
programming. These communications between classes are known as
messages. The sequence diagram lists objects horizontally, and time
vertically, and models these messages overtime.
Basic Elements
1) object
An object has state, behavior, an identity object interact through there links
to other objects .the pictorial representation for an object is a class with pre
fixed by the object name and semicolon.
