Software Requirements SpecificationVersion 1.1

February 3, 2011

Web Accessible Alumni Database

U.Deepika

Submitted in partial fulfillmentOf the requirements ofCS2357 OOAD LAB

SRS 04/10/23

Table of Contents

Table of Contents...............................................................................................................................................iiTable of Figures.................................................................................................................................................iii1.0. Purpose..........................................................................................................................................................1

1.1. Introduction...................................................................................................................................................11.2. Scope.............................................................................................................................................................11.3. Glossary........................................................................................................................................................11.4. References.....................................................................................................................................................21.5. Document overview......................................................................................................................................2

2.0. Overall description.....................................................................................................................................32.1. System environment.....................................................................................................................................32.2. Functional requirements definitions.............................................................................................................32.3. Use cases.......................................................................................................................................................3

2.3.1. Use Case: Login.....................................................................................................................................42.3.2. Use Case: View Train Details................................................................................................................52.3.3. Use Case: Reserve Tickets.....................................................................................................................62.3.4. Use Case: Cancel tickets........................................................................................................................72.3.5. Use Case: Handle PNR No....................................................................................................................82.3.6. Use Case: Free Payment........................................................................................................................9

2.4. Non-functional requirements..........................................................................................................................113.0. Requirement specifications...................................................................................................................12

3.1. External interface specifications.................................................................................................................123.2. Functional Requirements............................................................................................................................12

3.2.1. Access Alumni Home Page.................................................................................................................123.2.2. Survey..................................................................................................................................................123.2.3. Create a new entry...............................................................................................................................133.2.4 Update an Entry....................................................................................................................................143.2.5. Search for an Alumni/E-mail an Alumni.............................................................................................15

3.3. Detailed non-functional requirements........................................................................................................173.4. System Evolution........................................................................................................................................18

4.0. Index.............................................................................................................................................................19

ii

SRS 04/10/23

Table of Figures

Figure 1 System Design...........................................................................................................................................4Figure 2 Passenger logs the Reservation System....................................................................................................6Figure 3 Passenger view train details......................................................................................................................7Figure 4 Passenger Reserve Tickets........................................................................................................................8Figure 5 Passenger cancels ticket............................................................................................................................9Figure 6 Reservation System handles PNR No.....................................................................................................10Figure 7 Free Payment for Railway Employee........................................................................................................4

iii

SRS 04/10/23

1.0. Purpose

1.1. Introduction

This Software Requirements Specification provides a complete description of all the

functions and specifications of the Jacksonville State University Computing and Information

Sciences (CIS) Web Accessible Alumni Database.

The expected audience of this document is the faculty of CIS, including the faculty who

will use this system, Dr. Dennis Martin and studio committee members, and the developer. It

will also server as a reference for Studio students.

1.2. Scope

The Jacksonville State University Computing and Information Sciences Web Accessible

Alumni Database (CISWAAD) is designed to run on the departmental server and to allow

alums to fill out a survey form, create a new database entry, update an existing database

entry, or contact another alum. The data will be held in an Access database on the

departmental server.

1.3. Glossary

Term DefinitionAlum Graduate of Jacksonville State University

undergraduate computer science programs.BDE Borland Database EngineCI Configuration ItemCIS Computing and Information SciencesEntry Alum stored in the Alum DatabaseHtml Hyper text markup languageIEEE Institute of Electrical and Electronic

EngineersQA Quality assuranceSCMP Software Configuration Management PlanSDD Software Design Document

1

SRS 04/10/23

SEI Software Engineering Institute, Pittsburgh, Pa

SQAP Software Quality Assurance PlanSRS Software Requirements SpecificationSurvey Form filled out and submitted by an Alum

using the CISWAAB.Tbd To be decidedTbn To be namedWeb Site A place on the world wide web

1.4. References

[IEEE] The applicable IEEE standards are published in “IEEE Standards Collection,” 2001 edition.

[Bruade] The principal source of textbook material is “Software Engineering: An Object-Oriented Perspective” by Eric J. Bruade (Wiley 2001).

[Reaves SPMP] “Software Project Management Plan Jacksonville State University Computing and Information Sciences Web Accessible Alumni Database.” Jacksonville State University, 2003.

1.5. Document overview

The remainder of this document is two chapters, the first providing a full description of

the project for the owners of the CIS. It lists all the functions performed by the system. The

final chapter concerns details of each of the system functions and actions in full for the

software developers’ assistance. These two sections are cross-referenced by topic; to increase

understanding by both groups involved.

2

SRS 04/10/23

2.0. Overall description

The Online Ticket Reservation System encompasses numerous files and information

from the Railway Database, as well as files on the reservation server system. This system

will be completely web-based. An Internet connection is necessary to access the system.

2.1. System environment

Figure 1 System Design

The Online Ticket Reservation System web site will be operated from any node. When an

paseenger login to the reservation system , it updates the information in to the database to the

server.Then reservation system server will display the information for reserving the tickets to

the pasenger through User Interface Screens.Passenger can enter the information such as

Passenger name, Sex, Age, Address, Class through he is going to travel, Train no, Train

name, Date of Journey and number of tickets to be booked.

2.2. Functional requirements definitions

Functional Requirements are those that refer to the functionality of the system, i.e.,

what services it will provide to the user. Nonfunctional (supplementary) requirements pertain

to other information needed to produce the correct system and are detailed separately.

2.3. Use cases

The system will consist of Login screen to authenticate the passenger whose

information is updated in the database. Before booking the ticket, the passenger should

check the availability of seats and train details for reserving the ticket. Once the ticket is

3

SRS 04/10/23

reserved a unique PNR No. will be provided. Passenger can cancel the ticket with the PNR

No. that is provided by railway database. PNR No. should be handled for reserving ticket,

cancelling ticket, and RAC (Reservation Against Cancellation). Before issuing ticket the

amount from customer has to be transferred to railway account.

2.3.1. Use Case: Login

Figure 2 Passenger logs the Reservation System

Brief DescriptionThe use case describes how passenger logs in to the Reservation System.

Initial step-by-step descriptionFor this use case to be initiated, the passenger must be connected to the Internet and

connected to the Railway database.

1. The Railway Reservation System requests the passenger to enter his/her user ID and password.

2. The Passenger enters his/her user ID and password.

3. The System validates the entered user ID and password and logs the passenger into the Railway Reservation System.

Use Case Name: LoginPriority EssentialTrigger Menu selectionScope Online Ticket Reservation SystemLevel User goal levelPrecondition NoneBasic Path 1. The Railway Reservation System

requests the passenger to enter his/her user ID and password.

4

SRS 04/10/23

2. The Passenger enters his/her user ID and password.

3. The System validates the entered user ID and password and logs the passenger into the Railway Reservation System

Alternate Path Invalid User ID/Password If, in the Basic flow, the passenger enters an invalid user ID and/or password, the system displays an error message. The passenger chooses to either return to the beginning of the basic flow or cancel the login, at which point the use case ends.

Postcondition If the use case was successful, the passenger is now logged into the reservation system. If not, the system state is unchanged.

Exception Path If the connection is terminated before the details is submitted, the fields are cleared and the server is returned to the wait state.

Special Requirement 1. Touch screen UI on a large flat panel monitor. Text must be visible from 1 meter.

2. Credit authorization response within 30 seconds 90% of the time.

3. Language internationalization on the text displayed.

2.3.2. Use Case: View Train Details

Figure 3 Passenger view train details

Brief Description:

Initial step-by-step description:

5

SRS 04/10/23

Use Case Name: LoginPriority EssentialTrigger Menu selectionScope Online Ticket Reservation SystemLevel User goal levelPrecondition NoneBasic PathAlternate PathPost conditionException PathSpecial Requirement

1.

2.3.3. Use Case: Reserve Tickets

Figure 4 Passenger Reserve Tickets

Brief Description:

Initial step-by-step description.

6

SRS 04/10/23

Use Case Name: LoginPriority EssentialTrigger Menu selectionScope Online Ticket Reservation SystemLevel User goal levelPrecondition NoneBasic PathAlternate PathPostconditionException PathSpecial Requirement

2.3.4. Use Case: Cancel Tickets

Figure 5 Passenger cancels ticket

Brief Description:

Initial step-by-step description:

Use Case Name: LoginPriority EssentialTrigger Menu selectionScope Online Ticket Reservation SystemLevel User goal levelPrecondition NoneBasic PathAlternate PathPostcondition

7

SRS 04/10/23

Exception PathSpecial Requirement

2.3.5. Use Case: Handle PNR No.

Figure 6 Reservation System handles PNR No.

Brief description: PNR No. should be handled for reserving tickets and cancelling tickets.

Initial step-by-step description: For this use case to be initiated, the passenger must be connected to the Internet and

connected to the Railway database.

1. Once the passenger viewed train details and he/she is satisfied with train details then he/she reserve tickets

2. After reserving the ticket, passenger will be provided with an unique PNR No.

3. Before issuing ticket the ticket the amount from customer account has to be transferred to railway account.

4. Passenger can cancel the ticket through the PNR No. issued and this will be handled by the Reservation System.

5. Reservation Against Cancellation facility is also provided.

Use Case Name: Handle PNR No.Priority EssentialTrigger Menu selectionScope Online Ticket Reservation SystemLevel User goal levelPrecondition NoneBasic Path 1. Once the passenger viewed train

8

SRS 04/10/23

details and he/she is satisfied with train details then he/she reserve tickets

2. After reserving the ticket, passenger will be provided with an unique PNR No.

3. Before issuing ticket the ticket the amount from customer account has to be transferred to railway account.

4. Passenger can cancel the ticket through the PNR No. issued and this will be handled by the Reservation System.

5. Reservation Against Cancellation facility is also provided.

Alternate Path Reservation System detects failure to communicate with credit card system service:

1. System restarts the service on the Reservation System node, and continues.

2. System detects that the service does not restart.

Postcondition If the PNR No. is properly handled by the Reservation System, the passenger can reserve or cancel tickets successfully

Exception Path If the connection is terminated, the fields are cleared and the Reservation System is returned to wait state.

Special Requirement 1. Touch screen UI on a large flat panel monitor. Text must be visible from 1 meter.

2. Credit authorization response within 30 seconds 90% of the time.

3. Language internationalization on the text displayed.

2.3.6. Use Case: Free Payment

9

SRS 04/10/23

Figure 7 Free Payment for Railway Employee

Brief description: Free payment of tickets for Railway Employee.Initial step-by-step description: For this use case to be initiated, the passenger must be connected to the Internet and

connected to the Railway database.

1. If the passenger is an Railway employee, then he can log with his/her user ID and password.

2. After viewing the train details, the passenger can reserve the tickets.

3. The tickets will be reserved as free of cost.

Use Case Name: Free PaymentPriority EssentialTrigger Menu selectionScope Online Ticket Reservation SystemLevel User goal levelPrecondition NoneBasic Path 1. If the passenger is an Railway

employee, then he can log with his/her user ID and password.

2. After viewing the train details, the passenger can reserve the tickets.

3. The tickets will be reserved as free of cost.

Alternate Path Passenger says they are eligible for a free payment, if he/she is an Railway Employee.

Postcondition If the use case was successful, then passenger Railway Employee) successfully have reserved tickets.

Exception Path If the connection is terminated, the fields are cleared and the Reservation System is returned to wait state.

Special Requirement 1. Touch screen UI on a large flat panel monitor. Text must be visible from 1

10

SRS 04/10/23

meter.

2. Credit authorization response within 30 seconds 90% of the time.

3. Language internationalization on the text displayed.

2.4. Non-functional requirements

There are requirements that are not functional in nature. Specifically, these are the

constraints the system must work within.

The web site must be compatible with both the Netscape and Internet Explorer web

browsers.

11

SRS 04/10/23

3.0. Requirement specifications

3.1. External interface specifications

None

3.2. Functional Requirements

3.3. Detailed non-functional requirements ( about logical structure of the data)

3.4. System Evolution

In the future this system will be update to allow students from the Computer Masters

Program to join. If time does not permit the search/e-mail section can be done, possibly by

another Master Studio student. A report generated by the system of the responses to the

survey could be another addition to the CISWAAD in the future.

12

SRS 04/10/23

4.0. Index

Audience, 1Borland Database Engine, 1, 3, 16Configuration Item, 1Customer, 3Database, i, 2, 3, 4, 6, 7, 8, 9, 10, 11, 12, 13, 16Developer, 1Function, 1, 2Institute of Electrical & Electronic Engineers, 1, 2Non-functional, 14Quality Assurance, 1, 2Server, 1, 3, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15Software Configuration Management Plan, 1Software Design Document, 1Software Engineering Institute, 2Software Project Management Plan, i, 2Software Quality Assurance Plan, 2Software Requirement Document, 2System, 1, 2, 3, 9, 15, 16Use Case, 3, 5, 6, 7, 8

13