Experiment-1

E-Ticketing
Question:

Do the following 7 exercises for E-Ticketing Project.

Task-1: Development of problem statement.

Task-2: Preperation of Software Requirement Specification Document, Design Document

and Testing Phase related documents.

Task-3: Preperation of Software Configuration Management and Risk Management related

documents.

Task-4: Study and usage of Design phase CASE tool.

Task-5: Performing the Design by using Design phase CASE tool.

Task-6: Develop test cases for unit testing and integration testing.

Task-7: Develop test cases for various white box and black box testing techniques.

Solution:

AIM:

To create an automated system to perform E-ticketing.

TASK-(I) PROBLEM STATEMENT

Our project is carried out to develop software for online Railway Reservation System. This
system has various options like reservation, cancellation and to view details about available
seats. Our project mainly simulates the role of a Railway ticket booking officer, in a
computerized way.

The reservation option enables a person to reserve for a ticket at their home itself. All he/ she
has to do is to just login and enter the required details. After this the reservation database is
updated with the person details, train name and also the source and destination place.

The cancellation option enables the passenger to cancel the tickets that has been already
booked by him/her.

The availability option prompts the person to enter train number, train name and date of
travel. After this the availability database is accessed and available positions are produced.
TASK-(II) SOFTWARE REQUIREMENT SPECIFICATION

2.0 INTRODUCTION

The manual system of ticket reservation takes more time and the number of reservations per
day is limited. To increase the efficiency of the process, we go for online ticket reservation
system. This system supports online ticket booking.

2.1 PURPOSE

If the entire process of reservation is done in a manual manner then it would takes several
months for reservation to reach the applicant. Considering the fact that the number of
passenger is increasing every year, an Automated System becomes essential to meet the
demand. So this system uses several programming and database techniques to elucidate the
work involved in this process. As this is a matter of National Security, the system has been
carefully verified and validated in order to satisfy it.

2.2 SCOPE

• The System provides an online interface to the user where they can fill in their personal
details and submit the necessary documents (may be by scanning).

• The authority concerned with the issue of railway can use this system to reduce his
workload and process the application in a speedy manner.

• Provide a communication platform between the passenger and the administrator.

• Passenger will come to know their status of application and the date in which they must
subject themselves for manual document verification.

2.3 DEFINITIONS, ACRONYMS AND THE ABBREVIATIONS

• Passenger – The person that who wishes to obtain the railway ticket.

• PNR – Passenger Name Records

• HTML - Markup Language used for creating web pages.

• J2EE – Java 2 Enterprise Edition is a programming platform java platform for developing
and running distributed java applications.

• HTTP - Hyper Text Transfer Protocol.

•TCP/IP – Transmission Control Protocol/Internet Protocol is the communication protocol

used to connect hosts on the Internet.

2.4 REFERENCES

IEEE Software Requirement Specification format.

2.5 TECHNOLOGIES TO BE USED

• HTML

• JSP

• Javascript

• Java

2.6 TOOLS TO BE USED

• Eclipse IDE (Integrated Development Environment)

• Rational Rose tool (for developing UML Patterns)

2.7 OVERVIEW

SRS includes two sections overall description and specific requirements –

Overall Description will describe major role of the system components and inter-
connections.

Specific Requirements will describe roles & functions of the actors.

2.8 OVERALL DESCRIPTION - PRODUCT PERSPECTIVE

This system tries to make the interface as simple as possible and at the same time not risking
the security of data stored in. This minimizes the time duration in which the user receives the
ticket.

2.9 SOFTWARE INTERFACE

• Front End Client - The passenger and System online interface is built using JSP and
HTML. The Administrators's local interface is built using Java.

 Web Server – Apache Tomcat Server (Oracle Corporation)

 Back End - Oracle 11g database

2.10 HARDWARE INTERFACE

The server is directly connected to the client systems. The client systems have access to the
database in the server.

2.11 SYSTEM FUNCTIONS

• Secure Registration of information by the Passengers.

• System can generate reports from the information and is the only authorized personnel to
add the eligible application information to the database.
• Display the requested pages to the user.

• Update the database after every successful process.

2.12 USER CHARACTERISTICS

• Passenger - They are the people who desire to obtain the ticket and submit the information
to the database.

2.13 CONSTRAINTS

• The passengers require a computer to submit their information.

• Although the security is given high importance, there is always a chance of intrusion in the
web world which requires constant monitoring.

• The user has to be careful while submitting the information. Much care is required.

2.14 ASSUMPTIONS AND DEPENDENCIES

• The Passengers must have basic knowledge of computers and English Language.

• The passengers may be required to scan the documents and send.

TASK-(III)

3.1 Software Configuration Management (SCM) Plan:

1. Introduction:

 Overview of the SCM Plan.

 Purpose and objectives of SCM for the e-ticketing system.

2. Configuration Identification:

 Naming conventions for components (e.g., modules, databases).

 Version control strategy (e.g., Git).

 Identification of configuration items.

3. Configuration Control:

 Procedures for controlling changes to the configuration.

 Change request process and forms.

 Change control board responsibilities.

4. Configuration Status Accounting:

 Procedures for recording and reporting the status of configuration items.

  Configuration item baseline definition.

5. Configuration Audits:

 Types of audits (e.g., functional, physical, code reviews).

 Audit schedules and responsibilities.

6. Release Management:

 Procedures for planning, scheduling, and controlling software releases.

 Version numbering and release notes.

7. Tools and Infrastructure:

 Description of SCM tools used.

 Integration with other development tools.

8. Responsibilities:

 Roles and responsibilities of team members involved in SCM.

 Training and onboarding procedures.

9. Documentation:

 Documentation standards for SCM processes and procedures.

 Maintenance of configuration management records.

3.2 Risk Management Plan:

1. Introduction:

 Purpose and objectives of the Risk Management Plan.

 Overview of the risk management process for the e-ticketing system.

2. Risk Identification:

 Techniques for identifying risks (e.g., brainstorming, risk workshops).

 Categories of risks (e.g., technical, operational, external).

3. Risk Assessment:

 Evaluation of the impact and likelihood of identified risks.

 Risk prioritization criteria.

4. Risk Mitigation:
  Strategies and actions for mitigating identified risks.

 Assignment of responsibilities for risk mitigation.

5. Risk Monitoring and Control:

 Procedures for ongoing monitoring of identified risks.

 Trigger points for implementing risk response plans.

6. Contingency Planning:

 Development of contingency plans for high-impact risks.

 Escalation procedures for severe risks.

7. Communication:

 Communication plan for reporting and updating stakeholders on risks.

 Escalation channels for reporting critical risks.

8. Documentation:

 Record-keeping procedures for documenting identified risks and their status.

 Regular review and update of the risk register.

9. Continuous Improvement:

 Procedures for learning from past risks and improving risk management processes.

 Feedback loops for continuous improvement.

Remember to involve relevant stakeholders in the creation and review of these documents,
and update them as needed throughout the project lifecycle. Additionally, the success of these
plans depends on regular reviews, assessments, and adjustments based on the evolving needs
of the project.

Task-4: Study and usage of Design phase CASE tool.

Unified Modeling Language (UML)

Unified Modeling Language (UML) is a general purpose modelling language. The main
aim of UML is to define a standard way to visualize the way a system has been designed.

It is quite similar to blueprints used in other fields of engineering.

UML is not a programming language, it is rather a visual language. We use UML diagrams
to portray the behavior and structure of a system.
UML helps software engineers, businessmen and system architects with modelling, design
and analysis.

The Object Management Group (OMG) adopted Unified Modelling Language as a standard
in 1997. Its been managed by OMG ever since. International Organization for
Standardization (ISO) published UML as an approved standard in 2005. UML has been
revised over the years and is reviewed periodically.

UML is linked with object oriented design and analysis. UML makes the use of elements
and forms associations between them to form diagrams. Diagrams in UML can be broadly
classified as:

1. Structural Diagrams – Capture static aspects or structure of a system. Structural

Diagrams include: Component Diagrams, Object Diagrams, Class Diagrams and
Deployment Diagrams.

2. Behavior Diagrams – Capture dynamic aspects or behavior of the system. Behavior

diagrams include: Use Case Diagrams, State Diagrams, Activity Diagrams and
Interaction Diagrams.

Basic Building blocks of UML:

1. Things

2. Relationships

3. Diagrams

Things in the UML:

1 Structural Things

2 Behavioral Things

3 Grouping Things

4 Annotational Things

Structual Things:

Static part of a model, representing elements that are either conceptual or physical.

1. classes

2. interfaces

3. collaborations

4. usecases
 5. Active classes

6. Components

7. Nodes

Class:

A class is a description of a set of objects that share the same attributes,

operations,relationships and semantics.

Class implements one or more interfaces

Representation of class:

Interface

A collection of operation that specify a service of a class or component.

Describes externally visible behavior of that element.

Attached to class or component that realizes the interface.

Collaboration

Defines an interaction, which have structural as well as behavioral dimensions.

A given class may participate in several collaborations.

Usecase

A description of set of sequence of action that a system performs that yields to observable
result of value to a particular actor.

It is realized by collaboration.

Active class

It is just like a class except that its objects represent elements whose behavior is concurrent
with other elements.

Component

A physical and replaceable part of a system that confirms to and provides the realization of a
set of interfaces.

Represents physical packaging of classes, interfaces and collaboration.

Node
A physical element that exists at run time and represents a computational resource, having
atleast some memory and, often processing capability.

A set of components may reside on a node & may also migrate from node to node.

Behavioral Things

Behavioral Things are dynamic parts of UML models.

These are the verbs of a model, representing behavior over time & space.

Two primary kinds of Behavioral Things:

Interaction − Interaction is defined as a behavior that consists of a group of messages

exchanged among elements to accomplish a specific task.

State machine − State machine is useful when the state of an object in its life cycle is
important. It defines the sequence of states an object goes through in response to events.
Events are external factors responsible for state change

Grouping Things:

Grouping things are organizational parts of a UML model.

These are the boxed into which a model can be decomposed.

There is one primary kind of Grouping.

Packages

Mechanism for organizing elements into groups.

A package is purely conceptual meaning that it exists only at development time.

Annotational Things

Annotational Things are explanatory parts of UML models.

These are the Comments you may apply to describe & remark about any element in a model.

There is one primary kind of annotational things.

Note:

A Symbol for rending Constraints and Comments attached to an element or a collection of

elements.

Relationships in the UML:

REFER CLASS NOTES

UML Diagrams

All the elements, relationships are used to make a complete UML diagram and the diagram
represents a system.

The visual effect of the UML diagram is the most important part of the entire process. All the
other elements are used to make it complete.

UML includes the following nine diagrams

 Class diagram

 Object diagram

 Use case diagram

 Sequence diagram

 Collaboration diagram

 Activity diagram
  Statechart diagram

 Deployment diagram

 Component diagram

Task-5: Performing the Design by using Design phase CASE tool.

USE-CASE DIAGRAM

The online ticket reservation system uses the following use cases:

1. Request for seat availability

2. makeReservation
3. Cancellation
4. Check status
5. Print ticket

ACTORS INVOLVED:

1) System
2) Passenger

USE-CASE NAME: REQUEST FOR SEAT AVAILABILITY

The passenger can view the train available in the database for deciding which
train ticket he wishes to reserve. The passenger can search the train information based on
journey date, train type and reservation type. The passenger can view the details of flights
such as, train number, source station, destination station, arrival time, departure time, fare
and number of seats available.

USE-CASE NAME: MAKERESERVATION

The user is allowed to reserve a ticket on train as he/she requires on the particular
date and time. The user has to provide details such as name, train number, date of travel,
source station, destination station, proof name and money transaction details.

USE-CASE NAME: PRINT TICKET

The user after booking a ticket can print a copy of the ticket reserved. The user
has to provide the details about ticket number for searching in the database and passenger
name for confirming passenger identity.

USE-CASE NAME: CANCEL TICKET

A passenger can decide to cancel a ticket after the ticket is booked. The passenger
has to provide details about ticket for searching and details about him for confirmation of
identity
USE-CASE NAME: CHECK STATUS
The passenger can view the status of the reserved tickets. So the passenger can
confirm his/her travel.
CLASS DIAGRAM:

The class diagram, also referred to as object modeling is the main static analysis
diagram. The main task of object modeling is to graphically show what each object will
do in the problem domain. The problem domain describes the structure and the
relationships among objects.
.
The online ticket reservation system makes use of the following classes:

1. ticketReservation
2. trainInfo
3. passengerInfo
4. seatAvailStatus

1. TICKETRESERVATION
It consists of twelve attributes and two operations. It records the details of every
ticket booked such as ticket number, passenger ID, source and destination station and etc.

2. TRAININFO
It stores the details of all the trains such as train number, train name, speed, source
and destination stations, etc.

3. PASSENGERINFO
It consists of seven attributes and three operations. This class is used to store
passenger details such as, passenger name, age, address and etc.

4. SEATAVAILSTATUS
This class is used to update the number of seats available for a particular train by
using updateStatus() operation.
INTERACTION DIAGRAM:

A sequence diagram represents the sequence and interactions of a given USE-

CASE or scenario. Sequence diagrams can capture most of the information about the
system. Most object to object interactions and operations are considered events and
events include signals, inputs, decisions, interrupts, transitions and actions to or from
users or external devices.

An event also is considered to be any action by an object that sends information.

The event line represents a message sent from one object to another, in which the “form”
object is requesting an operation be performed by the “to” object. The “to” object
performs the operation using a method that the class contains.

This sequence diagram describes the sequence of steps to show

• Passenger are used to login the form. And then its verify the username and
password.
• If the password and username are correct then applicants are used to login the
filling details.
• Passenger are used to selecting the train and book the tickets.
• Now the E-Ticketing DataBase verify the filling Details.
• And then the E-Ticketing DataBase displays the ticket information.
• Incase of any sudden change of the plan, the applicant can cancel the ticket.
ACTIVITY DIAGRAM

Activity diagrams are graphical representations of workflows of stepwise activities and

actions with support for choice, iteration and concurrency. In the Unified Modeling
Language, activity diagrams can be used to describe the business and operational step-by-
step workflows of components in a system. An activity diagram shows the overall flow of
control. An activity is shown as an rounded box containing the name of the operation.

This activity diagram describes the behaviour of the system.

• First state is login where the passenger login to the E-Ticketing system.
• The next state is filling details the passenger are used to fill the form.
• Then passenger used to selecting the flight.
• The passenger appears for book ticket and search details from E-Ticketing
DataBase.
DEPLOYMENT DIAGRAM

Deployment diagrams are used to visualize the topology of the physical

components of a system where the software components are deployed.

COMPONENT DIAGRAM

A component diagram is used to break down a large object-oriented system into the smaller
components, so as to make them more manageable. It models the physical view of a system
such as executables, files, libraries, etc. that resides within the node.

It visualizes the relationships as well as the organization between the components present in
the system. It helps in forming an executable system. A component is a single unit of the
system, which is replaceable and executable. The implementation details of a component are
hidden, and it necessitates an interface to execute a function.
COMPONENT DIAGRAM