Table of Contents

PAGE NO.
EXPERIMENT NAME
from-to
Do the following 9 exercises for any two projects given in the list
of
sample

projects or any other projects:

1. Write the complete problem statement.

2. Write the Software Requirement Specification Document

3. Draw the entity relationship diagram
i
4. Draw the data flow diagrams
5. Draw the use case diagrams
6. Draw the activity diagrams for all use cases
7. Draw sequence diagrams for all use cases
8. Draw the collaboration diagram
9. Assign objects in sequence diagrams to classes and make class diagram

1. Railway reservation system

2. Library Management system

1 1
 SOFTWARE REQUIREMENT SPECIFICATION

IEEE Standard SRS Template

1. Introduction
Purpose
Scope
Definitions, acronyms & abbreviations
References
Overview

2. Overall description

Product perspective
System interfaces
User interfaces
Hardware interfaces
Software interfaces
Communications interfaces
Memory constraints
Operations
Site adaptation requirements
Product functions
User characteristics
Constraints
Assumptions and dependencies
Apportioning of requirements

3. Specific Requirements

External interface requirements

User interfaces
Hardware interfaces
Software interfaces
Communication interfaces
Specific requirements
Sequence diagrams
Classes for classification of specific requirements
Performance requirements
Design constraints
Software system attributes
Reliability
Availability
Security
Maintainability
Other requirements

4. Supporting information

Table of contents and index

Appendices

2 1
1
Ex. No. 1
Railway Reservation System

AIM:
To create an automated system to perform online Railway reservation

(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.

(II) SOFTWARE REQUIREMENT SPECIFICATION

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.

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
 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.

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.

REFERENCES
IEEE Software Requirement Specification format.

TECHNOLOGIES TO BE USED
• HTML
• JSP
• Javascript
• Java

TOOLS TO BE USED
• Eclipse IDE (Integrated Development Environment)
• Rational Rose tool (for developing UML Patterns)
OVERVIEW
SRS includes two sections overall description and specific requirements – Overall
Description will describe major role of the system components and inter-
connections.

3
 Specific Requirements will describe roles & functions of the actors.

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.

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

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

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.

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

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.

4
 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.

(III) 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

5
ENTITY RELATIONSHIP DIAGRAM

0-LEVEL DFD:

6
1-LEVEL DFD:

7
2-LEVEL DFD:

8
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.

9
USE-CASE NAME: CHECK STATUS

The passenger can view the status of the reserved tickets. So the passenger can
confirm his/her travel.

request for seat availability

<<include>>

print report
makeReservation

Passenger System

cancellation

check status

Fig.3.1 USE-CASE DIAGRAM FOR RAILWAY RESERVATION

1
(IV) 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.

Check seat availablity based on date/ train/reservation type

Yes
Is it valid
No data?

Show the error page Display the required train information

Fig.4.1 ACTIVITY DIAGRAM [Check Availability]

1
 Login(username
,password)

Check the data

Yes
with database

Is it valid user No

Yes
Display the cancellation page
Show error message to enter correct data

Select the passenger details

want to proceed

Perform amount transaction Yes

is it valid
No
Yes data?

Store & update the status Ask to enter correct data

Show the want to

Confirmation proceed
No

Print the
ticket No

Fig.4.2 ACTIVITY DIAGRAM [Ticket Reservation]

1
 request tocheck pnr status

Enterthe PNR number

Yes
Is valid PNR
No no?
Invalid PNR number Display the status

Fig.4. 3ACTIVITY DIAGRAM [Check Status]

1
 Login(username
,password)

Check the data

with database Yes

Is it valid user No

Yes
Display the
cancellation page Show error message to enter correct data

Select the
passenger details want to proceed

Yes

is it valid
No
Yes data?

Store & update the status Ask to enter correct data

Show the Confirmation want to proceed

No

No

Fig.4. 4ACTIVITY DIAGRAM [Ticket Cancellation]

1
(V) 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.

1
Fig.5.1 CLASS DIAGRAM FOR RAILWAY TICKETING

1
(VI) SEQUENCE 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.

1
: Passenger reserveTicket : cancelTicket : ticketReservation
: seatAvailStatus System
ticketReservation

Login(username,password)

Check given data

Registered user

Display the reservation page Enter the passenger details

Perform money transaction

Verify given details

Update status

Store the details

Updated successfully

Confirm & Display the ticket Print the ticket

request to cancel ticket
Display the cancellation page Select the passenger details

Verif given details

Update status
Store the details
Updated successfully

Ticket cancelled

Fig.6.1. SEQUENCE DIAGRAM

1
 7: Verifygiven details
1: Login(username,password)
5: Enter the passenger
details 6: Perform money
transaction 13: Print the
ticket reserveTicke
t:
ticketReservat

4: Display the reservation page 2: Checkgivendata

12: Confirm & Display the ticket
: Passenger
3: Registered user

System
14: request to cancel ticket 8: Update status
16: Select the passenger details 11:

9: Store the details

15: Display the cancellation page
19: Storethedetails
22: Ticket cancelled

17: Verify given details

10: Updated successfully
20: Updated successfully

18: Update status

cancelTicket :
ticketReservation : seatAvailStatus
21:

Fig.6.2 COLLABORATION DIAGRAM

RESULT:
Thus the system for Railway reservation system has been successfully
developed.

1
2
Ex No: 2
L IBRARY MANAGEMENT SYSTEM
AIM:

2
 To create a system to perform library management operation

(I)PROBLEM STATEMENT:

A library management lends books and magazines to member, who is registered in the
system.Also it handles the purchase of new titles for the Book Bank. Popular titles are brought
into multiple copies. Old books and magazines are removed when they are out or date or poor
in condition. A member can reserve a book or magazine that is not currently available in the
book bank, so that when it is returned or purchased by the book bank, that person is notified.
The book bank can easily create, replace and delete information about the tiles, members,
loans and reservations from the system.

(II)SOFTWARE

REQUIREMENTS

SPECIFICATION: 1.0

INTRODUCTION

Book Bank is the interface between the students and Librarian. It aims at improving
the efficiency in the Issue of books or magazines and reduce the complexities involved in
it to the maximum possible extent.

PURPOSE

If the entire process of 'Issue of Books or Magazines' is done in a manual manner then
it would take several months for the books or magazines to reach the applicant.
Considering the fact that the number of students for Book Bank 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. The
system has been carefully verified and validated in order to satisfy it.
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 books can use this system to reduce his workload and process the
application in a speedy manner.
DEFINITIONS, ACRONYMS AND THE ABBREVIATIONS

5. Librarian - Refers to the super user who is the Central Authority who
has been vested with the privilege to manage the entire system.□
6. Student - One who wishes to obtain the Books or Magazines.□
7. HTML - Markup Language used for creating web pages.□

2
 □ J2EE - Java 2 Enterprise Edition is a programming platform and it is the
□ part of the java platform for developing and running distributed java
□ HTTP H y p e r t e x t Transfer Protocol
□ TCP/IP - Transmission Control Protocol/Internet Protocol is
the communication protocol used to connect hosts on the
Internet.

REFERENCES

IEEE Software Requirement Specification format

TECHNOLOGIES TO BE USED

□ Visual Basic
□ Oracle 11g
TOOLS TO BE USED

□ Visual Basic Tools

□ Rational Rose tool (for developing UML Patterns)
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.

OVERALL DESCRIPTION:

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

PRODUCT PERSPECTIVE

The SRS acts as an interface between the 'Students' and the 'Librarian'. 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 books or magazines.
SOFTWARE INTERFACE

□ Front End Client - The Student and Librarian online interface is

built using Visual studio.
□ Back End - Oracle 11 g database

2
HARDWARE INTERFACE

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

□ Secure Registration of information by the Students.

□ Librarian can generate reports from the information and is the only authorized
personnel to add the eligible application information to the database.
USER CHARACTERISTICS

□ Student - They are the people who desire to obtain the books and submit the
information to the database.
□ Librarian - He has the certain privileges to add the books and to approval of
The reservation of books.
CONSTRAINTS

□ The Students 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 Students has to be careful while submitting the information. Much care
is required.

ASSUMPTIONS AND DEPENDENCIES

□ The Student and Librarian must have basic knowledge of computers and
English Language.
□ The Students may be required to scan the documents and send.

(III)USE-CASE DIAGRAM:
The book bank use cases are:
1. book_issue
2. book_return
3. book_order
4. book_entry

5. Search book_details

ACTORS
INVOLVED:

1. Student
2. Librarian
3. Vendor

2
USECASE NAME : SEARCH BOOK_DETAILS

The librarian initiates this use case when any member returns or request the book and checking
if the book is available.
Precondition: The librarian should enter all Book details.
Normal Flow: Build message for librarian who search the book.
Post Condition: Send message to respective member who reserved the book.

USECASE NAME : BOOK_ISSUE

Initiated by librarian when any member wants to borrow the desired book. If the book is
available, the book is issued.
Precondition: Member should be valid member of library.
Normal Flow: Selected book will be issued to the member.
Alternative Flow: If book is not available then reserved book use case should be initiate.
Post Condition: Update the catalogue.

USECASE NAME : BOOK_ORDER

Initiated by librarian when the requested book is not available in the library at that moment. The
book is reserved for the future and issued to the person when it is available.
Precondition: Initiated only when book is not available.
Normal Flow: It reserved the book if requested.
Post Condition : Mention the entry in catalogue for reservation.

USECASE NAME : BOOK_RETURN

Invoked by the librarian when a member returns the book.

Precondition: Member should be valid member of library.
Normal Flow: Librarian enters bookid and system checks for return date of the book.
Alternative Flow: System checks for return date and if it returned late fine message will be
displayed.
Post Condition: Check the status of reservation.

USECASE NAME : BOOK_ENTRY

The purchase book use-case when new books invoke it or magazines are added to the library.

2
 Precondition: Not available or more copies are required.
Normal Flow: Enter bookid,author information, publication
information, purchased
date, prize and number of copies.
Post Condition: Update the information in catalogue.

Entity relationship diagram:

2
2
Data Flow Diagrams:
DFD Level-0

DFD Level-1

2
DFD Level-2

2
Usecase diagram:

book_issu

stude
libraria

book_retur

book_entr

vendo
search

book_order

(IV) ACTIVITY DIAGRAM:

A c t i v i t y diagrams are graphical representations of workflows of stepwise activities
a n d
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.

shows
id card

request
for specific

is book
available? enquires
for

3
ACTIVITY DIAGRAM [BORROW BOOK]

3
 collects
quotation

no

if satisfied
with norms?

yes

place

discount & mode

of payment

takes

bill amt

ACTIVITY DIAGRAM [ ORDER BOOK]

3
ACTIVITY DIAGRAM [RETURN BOOK]

shows id
and

librarian
makes

on or
before n

pays

ye

librarian
approves

3
(V) CLASS DIAGRAM:

The class diagram, also referred to as object modeling is the main static analysis
d i a g ra m . The main task of object modeling is to graphically show what each
w i ll d o in
object the problem domain. The problem domain describes the structure and the
relationships
among objects.
The ATM system class diagram consists of four classes:
1. Student
2. Book
3. Issue
4. Return
5. Vendor
6. Details

1)STUDENT:

It consists of twelve attributes and three operations. The attributes are enrollno,
name,
D O B , fa t hername, address, dept name, batch and book limits. The operations of
c l as s a r e
this addStInfo(), deleteStInfo(), modifyStInfo().

2) BOOK:
It consists of ten attributes and four operations. This class is used to keep book
information such as author, title, vendor, price, etc

3)ISSUE:
It consists of eight attributes and two operations to maintain issue details such as, issue
date, accno of issued book, name of the student who borrowed book.

4)RETURN:
It consists of eight attributes and two operations to maintain issue details such as, issue
date, accno of issued book, name of the student who borrowed book.

5)STUDENTS:
The attributes of this class are name, dept ,year ,bcode no The o p e r a t i o n i s
d is p la y
students().

6)DETAIL:
The attributes of this class are book name, author, bcode no The operatio n s a r
d e l e te
details().

3
(VI) SEQUENCE DIAGRAM:

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

CASE
o r s c e n a rio . S equence diagrams can capture most of the information
s y s t e m . M os t
about the object to object interactions and operations are considered events and
events
include signals,
i n p u ts , d ecisions, interrupts, transitions and actions to or from users or external
d e v ic e s .
An event also is considered to be any action by an object that sends information.

The
e v e n t l i n e r e p r e s e n t s a message sent from one object to another, in which the
“ f o r m ” o bj e c t i s
requesting an operation be performed by the “to” object. The “to” object performs
the
operation using a method that the class contains.
It is also represented by the order in which things occur and how the objects in

3
 the
system send message to one another.

3
 : issue : return search DB
: student : librarian

1: request
book
2: check available book

3: check available
book

4: not avilable
5: not
avilable
6: not available

7: request for another

book
8: check
availability
9: check
availabilty

10: available
11:
avilable
12: avilable

13: provide student details

14: enter issue

data
15: update
issue

status 16: issue

17: updated update
successfully d
18: issue
book

19: request to return

book
20: enter the book
details
21: update
return

status 22: return

23: updated update
successfully d
24: book
returned

. SEQUENCE DIAGRAM FOR BOOK ISSUE & RETURN

3
 1: request book
7: request for another book
14: enter issue data
13:provide student details
19:request to return book
: issue
: librarian 17: updated successfully
6: not available
12: avilable
18: issue book 15: update issue status

: student 24: bookreturned

16: issue status updated

2: check available book 8: DB

check availability
23:updated successfully
5:not avilable
20: enter the book details
11:avilable
3: check available book
21:update return status
9: check availabilty

22: return status updated 4: notavilable

10: available

: return
search

COLLABORATION DIAGRAM FOR BOOK ISSUE & RETURN

RESULT:
Thus the system for Library management System has been successfully developed.

3
3