Info Intellects

8/14/2019 Info Intellects

1/24

Tourism Management Solution Version:

Software Requirement Specification Date: 15-Oct-07

Authors: Archana Devi. K, Deepak Kakkar, Harish. R and Hemalatha. P

Info Intellects, 2007 Page 1 of 24

Info Intellects

Tourism Management Solution

Software Requirements Specification

Version 1.0

Team members

Archana Devi. K

Deepak Kakkar

Harish. RHemalatha. P

Project Guide

Ms. Ramya. R


2/24





Date Version Description Author

25-Sep-07 Use Case Diagram Archana Devi. K,

Deepak Kakkar

28-Sep-07 Introduction Harish. R

1-Oct-07 Use-Case Model Survey Deepak Kakkar

4-Oct-07 Architecture Diagram Archana Devi. K,

Deepak Kakkar

8-Oct-07 Use Case Reports Archana Devi. K,Deepak Kakkar

10-Oct-07 Database Design Archana Devi. K,

Hemalatha. P

12-Oct-07 Assumptions and Decencies Harish R, Hemalatha. P

13-Oct-07 Supplementary Requirements Deepak Kakkar

14-Oct-07 Supporting Information & Doubts Archana Devi. K


3/24





Table of Contents

1. Introduction

1.1. Purpose...4

1.2. Scope..4

1.3. Definitions, Acronyms and Abbreviations.4

1.4. Reference7

1.5. Technologies to be used.7

1.6. Overview7

2. Overall Description

2.1. Use-Case Model Survey.8

2.2. Architecture diagram & database design..10

2.3. Assumptions and Dependencies...13

3. Specific Requirements

3.1. Use-Case Reports...133.2. Supplementary Requirements.23

4. Supporting Information.23

5. Concerns / Queries / Doubts if any..24


4/24





Software Requirements Specification

1. Introduction

1.1. Purpose: Tourism Management Solution is an effective, user-interactive system that helps the users by providing a lot of self-service

options. This system reduces manual work and even decreases wastage of

time and the tension involved in choosing a tourist spot and maintaining

the bookings done by the user.

1.2. Scope:

Provide a user benefit aimed process, which facilitates a different

and more convenient portal for tourism in tamilnadu.

Provide complete details about various tourist attractions in a

state.

Provide an easy means to help the user to access various

information involved in tourism.

Provide additional packages about the tourist spots by which the

users can access the spots of a particular category only

Maintain the details of the registered customers, spots, hotels andtour booking.

Regulate the navigation of the user inside the system efficiently. Provide online booking facility to the user.

Provide a way through which the user can book theatre tickets,

view advertisements.

Special offers are given to the users according to their category of

registration.

Blogging facility is provided, where users can share their views

about this project.

Provide useful links to various hotel sites that enables user to bookhotel room easily.

1.3. Definitions, Acronyms and Abbreviations

1.3.1. Definitions:

DB2 Express-C: It provides a flexible, low-cost, high valuedatabase as the corner stone for their information on demand

applications.


5/24





DBMS: A software system that facilitates the creation andmaintenance and use of an electronic database.

HTTP: A protocol (utilizing TCP) to transfer hypertext requestsand information between servers and browsers.

J2EE: It is an Enterprise Application Development Specificationthat provides a platform fordeveloping, deploying and managing

applications. It includes Servlets, Java Server Page and Enterprise

Java Beans.

JAR: It is used for aggregating many files into one. It is generally

used to distribute Java classes and associated metadata.

JSP: JSP technology is one of the most powerful, easy to use, andfundamental tools in a Web site developer's toolbox. It combines

HTML and XML with Java servlet and JavaBeans technologies to

create a highly productive environment for developing and

deploying reliable, interactive, high-performance, platform-

independent Web sites.

SERVLETS: Servlets are programs that run on a web server

and build web pages dynamically.

SQL: Structured Query Language; used for managing andquerying databases.

TCP/IP: A protocol developed for the Internet to get data fromone network device to another. "TCP uses a retransmission

strategy to insure that data will not be lost in transmission".

Internet Protocol address; a sequence of numbers used

to identify a particular computer or domain name on the Internet

UML: It is a set of notations and conventions used to describeand model an application.

WAR: It could be a JAR file used to distribute a collection ofJavaServer Pages, servlets, Java classes, XML files, tag libraries

and static Web pages that together constitute a Web application.


6/24





WAS: It providescentralizedadministrationofallyourcomponentswithanadministrativeservertrackingallofadomainscontentsandactivitiesinanadministrativerepository.

WSAD: This is an easy-to-use environment that lets you buildcomplex, scalable, J2EE applications, application adapters, and

Web services with consistent quality in a fraction of the time. It

also provides configurations for rapid application development

with minimal hand coding.

XML: Extensible Markup Language; used for describing data ina structured text format

1.3.2. Acronyms:

DBMS: Data Base Management System

EJB: Enterprise Java Bean

ERD: Entity Relationship Diagram

HTML: Hyper Text Markup Language

HTTP: Hyper Text Transfer Protocol

IDE: Integrated Development Environment

IEEE: Institute of Electrical and Electronics Engineering

IP: Internet Protocol

J2EE: Java 2 Enterprise Edition

JAR: Java ARchive

JDK: Java Development Kit

JSP: Java Server Pages

JVM: Java Virtual Machine

SQL: Structured Query Language

TCP: Transfer Control Protocol

UI: User Interface

UML: Unified Modeling Language

WAS: Web sphere Application Server

WSAD: Web sphere Studio Application Developer

XML: eXtensive Markup Language

1.3.3. Abbreviations:


7/24





Cust: Customer

Admin: Administrator

DB/db: Database

1.4. Reference

IEEE SRS Format [Dt. 27.09.2007]

TGMC Sample Synopsis [Dt. 09.07.2007]

Use Case Specification V.6 [Dt. 07.01.2003]

1.5. Technologies to be used

J2EE

DB2 Express C Centralized Database

WSAD Designing and Development Tool [IDE]

WAS Application Server

Rational Rose UML Design Tool

1.6. Overview:

This Use Cases Specification document groups UML diagrams and texts

that provide a use-case view of requirements for the Tourism Management

Solution suite of tools, hereafter called the system.

Section 2 presents the objectives and contextual elements of the system. It

is a summary of elements contained in the Tourism Management Solution

document. It also provides a conceptual basis for the Software Architecture

document that will describe the decomposition of the system into subsystems,

classes and class utilities. The overview of the database management is also

provided.

Section 3 presents a set of use-case diagrams each containing several use

cases interacting with the different users of the system. Use cases are grouped in a

use-case diagram according to the roles of the main actors.

Section 4 presents another user view organized around conceptual details

containing index and table of figures.

Section 5 presents some end-user view of the functions of some software

components.


8/24





2. Overall Description

2.1. Use-Case Model Survey:

USE-CASE DIAGRAM


9/24





1. User Administrator: Responsible for managing the entire user details

and details about the tickets booking done by the user.

Maintain Ticket Details: Issues users with the required ticketreservation form and stores the details in the database.

Maintain User Details: Responsible for keeping record of all theuser details. He can create or delete the registered users.

2. Database Administrator: Responsible for managing the database byentering updating and deleting the details.

Maintain Images: Images are uploaded or removed form thedatabase

Maintain Spot Details: Spot details are uploaded and updated bydatabase administrator.

3. Business Administrator: Responsible for keeping all the records ofhotel details and maintains the recreation details.

Maintains Hotel Details: Hotels and their links are added, editedor removed from the database.

Maintains Recreation: Responsible for uploading or removingadvertisements, theatre details, shopping malls details etc

4. Business User: Person who is going to access the recreation detailsfrom the database. He can also request for business details for uploading

advertisements with the business administrator.

Access Recreation: Can give request to business administrator to

upload users request.

5. General User: Person who is going to see the details of a spot. He alsocan book his hotel room, book his traveling ticket or book his tour. He can

get the details about the usage of this software through the help option. He

can also sign up and become a registered user.

Book Hotel: Requests for booking hotel room.

Book Ticket: Requests for booking traveling ticket to the spot.

Book Tour: Select the type of tour the user wants from the set ofpackage given by the administrator.


10/24





Help: User gets details about using this application.

Select a Spot: Selects a spot to view its details.

Sign Up: Enters details to become a registered user. View the Spot: Views the spot details, location, and recreation.

6. Registered User: Person who logs into his account to use theadditional features provided to him by the administrator.

Login: Enters the logins page to enjoy the offers provided.

7. Database: It is used by the administrators to store various kinds of

details. The users use the database to access the details. If there is any dataloss during transaction the database will be able to recover all the datas

automatically.

Help: Stores and maintains the help files.

Offers: Provides the specified offers according to the category ofregistration.

User Authentication: To identify a registered user.

2.2. Architecture diagram & database design


11/24





ARCHITECTURE DIAGRAM

APPLICATION

LAYER

BUSINESS LAYER

DATA

LAYER

Centralized Database

Spot details ImagesUser detailsRecreation

History

Recorder

AuthorizationAdministration Tool Kit

Group

Manager

Detail

Manager

Comment

Search

Engine

Browser API

Data Access Ob ect Data Access Ob ect

Business object Business object Business object

Work Flow

Manager

J2EE Framework Web Service

JSP Servlets

INTERNET

Web Server [WAS]

Web Service InterfaceMetadata ServicesUI ComponentsWEB UI


12/24





Booking

Hotel details

User

Ticket details


13/24





2.3. Assumptions and Dependencies

The district details are already present in the database.

The details about the spot, hotel, food and all others are provided

manually into the database.

The administrator enters all the details.

The external links in the project is given manually.

3. Specific Requirements

3.1. Use-Case Reports:

User Administrator: Responsible for managing the entire user details

and details about the tickets booking done by the user.

Maintain Ticket Details: Issues users with the required ticket reservationform and stores the details in the database.


14/24





1. Name of the Use Case: maintain ticket details

2. Description:

Add tickets: Gets details from the transport corporation and providesthe booker with sufficient details.

Delete tickets: Gets details and deletes the tickets.

Update details: Updates the time changes to the db.Book tickets: The bookings done by the user are recorded and

reserved.Cancel tickets: Maintains a clear track to allow all the users to benefit

mutually.

3. Actors:

a. Primary Actor: User Administrator

b. Secondary Actor: None

4. Pre-Condition: The User Admin must be logged on to thedatabase.

5. Post-Condition:


15/24





a. Success End Condition: The ticket is added, deleted,updated, booked or cancelled.

b. Failure End Condition: Re-enter the details or cancel.

Maintain User Details: Responsible for keeping record of all the user details.He can create or delete the registered users.

1. Name of the Use Case: maintain user details

2. Description:

a. Add User: Gets details from the general user and provides him asecure user name and password.

b. Delete User: Gets details from the db and deletes the user

c. Update user details: Gets details from the register user and

updates the record in the db.

3. Actors:

a. Primary Actor: User Administrator

b. Secondary Actor: General User

4. Pre-Condition: The User Admin must be logged on to the database.

5. Post-Condition:

a. Success End Condition: User name and password isgenerated and the db is updated

b. Failure End Condition: Re-enter the details or cancel.

maintain user details

add user

delete user

update user detai ls


16/24





Database Administrator: Responsible for managing the databaseby entering updating and deleting the details.

Maintain Images: Images are uploaded or removed form the database

1. Name of the Use Case: maintain images2. Description:Upload Image: The images are added into the db.

Remove Image: The images are removed from the db

3. Actors:

a. Primary Actor: Database Administrator


4. Pre-Condition: The DB Admin must be logged onto the db.

5. Post-Condition:a. Success End Condition: The image is uploaded or

removed in the db.b. Failure End Condition: Re-load image or cancel.

Maintain Spot Details: Spot details are uploaded and updated by databaseadministrator.


17/24





1. Name of the Use Case: maintain spot details

2. Description:Add spot: The Spot details are added into the db.

Delete spot: The Spot details are removed from the db.

Update spot details: The spot details are changed in the db.

3. Actors:

a. Primary Actor: Database Administrator

b. Secondary Actor: None4. Pre-Condition: The DB Admin must be logged onto the db.

5. Post-Condition:

a. Success End Condition: The spot is added, deleted orupdated in the db.

b. Failure End Condition: Re-enter details or cancel.

Business Administrator: Responsible for keeping all the records of

hotel details and maintains the recreation details.

Maintains Hotel Details: Hotels and their links are added, edited orremoved from the database.


18/24





1. Name of the Use Case: maintain hotel details

2. Description:Add hotel: The hotel details are uploaded in the database.Remove hotel: The hotel details are removed from the database

Update hotel details: The hotel details are updated into the database

3. Actors:

a. Primary Actor: Business Administrator

b. Secondary Actor: Business user

4. Pre-Condition: Business Admin must be logged into the db.

5. Post-Condition:a. Success End Condition: Hotel details are added, deleted

or updatedb. Failure End Condition: Re-enter details or cancel.

Maintains Recreation: Responsible for uploading or removingadvertisements, theatre details, shopping malls details etc


19/24





1. Name of the Use Case: maintains recreation

2. Description:Add details: Adds the requests of the business user to the database.

Delete details: Deletes the details from the database.Update details:Updates the correct details to the db.

3. Actors:

a. Primary Actor: Business Administrator

b. Secondary Actor: Business User

4. Pre-Condition: Business Admin must be logged into the db.

5. Post-Condition:

a. Success End Condition: the details are either added,

deleted or updated to the db.b. Failure End Condition: Re-enters or cancels

Business User: Person who is going to access the recreation detailsfrom the database. He can also request for business details for uploading

advertisements with the business administrator.

Create Recreation: Gives request to business administrator to upload usersrequest.

1. Name of the Use Case: Create Recreation

2. Description: The Business user gives details about his business tothe business admin to add it into the project db.

3. Actors:

a. Primary Actor: Business user

b. Secondary Actor: Business Administrator

4. Pre-Condition: The5. Post-Condition: The requested operation is cancelled. The user

may re-enter details or cancel.a. Success End Condition: The business detail is added in

the db.b. Failure End Condition: Cancels or re-enters details.

Update Recreation: Gives request to business administrator to update users

request.


20/24





1. Name of the Use Case: Update Recreation

2. Description: The Business user may change or update his businessdetails.

3. Actors:a. Primary Actor: Business user

b. Secondary Actor: Business Administrator and Database.

4. Pre-Condition: The

5. Post-Condition: The requested operation is cancelled. The usermay re-enter details or cancel.

c. Success End Condition: The business detail is updated inthe db.

d. Failure End Condition: Cancels or re-enters details.

General User: Person who is going to see the details of a spot. He alsocan book his hotel room, book his traveling ticket or book his tour. He can

get the details about the usage of this software through the help option. He

can also sign up and become a registered user.

Booking: The general user can book his traveling ticket, hotel room for lodgingand boarding and book the type of tour he wants from the given set of packages.

1. Name of the Use Case: Book Hotel

2. Description: The user books his hotel rooms using this use case.


21/24





3. Actors:

a. Primary Actor: General user

b. Secondary Actor: Database

4. Pre-Condition: None

5. Post-Condition:

a. Success End Condition: The requested operation hasbeen performed.

b. Failure End Condition: User re-enters or cancel.

1. Name of the Use Case: Book Tickets.

2. Description: The user books his traveling ticket.

3. Actors:


b. Secondary Actor: User Administrator.


5. Post-Condition:

a. Success End Condition: Ticket has been registered forthat user.

b. Failure End Condition: Re-enters details or cancel.

1. Name of the Use Case: Book Tour

2. Description: The user can select the tour from the packagesprovided and book it using this use case.

3. Actors:

a. Primary Actor: General User.



5. Post-Condition:

a. Success End Condition: The user has booked the Tour.

b. Failure End Condition: Re-enters details or cancel.

Help: User gets details about using this application.

1. Name of the Use Case: Help

2. Description: The user can get all kind of details related with usingthis software.


22/24





3. Actors:

a. Primary Actor: General user.



5. Post-Condition:

a. Success End Condition: The user got the details forwhich he came.

b. Failure End Condition: Re-enter the detail or cancel.

Select a Spot: Selects a spot to view its details.

1. Name of the Use Case: Select a spot

2. Description: The user selects the spot to view its details.

3. Actors:




5. Post-Condition:

a. Success End Condition: The user has successfully

selected the spot.b. Failure End Condition: The spot name entered by theuser is invalid. Re-enters spot name or cancels.

Sign Up: Enters details to become a registered user.

1. Name of the Use Case: Sign up

2. Description: The General user gives his details to the database tobecome a registered user to enjoy the offers.

3. Actors:




5. Post-Condition:

a. Success End Condition: The general user has got a username and password.

b. Failure End Condition: The details given were wrong.The user re-enters details or cancel.


23/24





View the Spot: Views the spot details, location, and recreation.

1. Name of the Use Case: View the spot

2. Description: The general user views the required details about thespot.

3. Actors:



4. Pre-Condition: The spot name entered by the user must be valid.

5. Post-Condition:a. Success End Condition: The user has successfullyviewed the details.

b. Failure End Condition: None

Registered User: Person who logs into his account to use theadditional features provided to him by the administrator.

Login: Enters the logins page to enjoy the offers provided.

1. Name of the Use Case: Login

2. Description: The registered user enters his login id to access theoffers provided.

3. Actors:

a. Primary Actor: Registered user


4. Pre-Condition: The user must be a registered user.

5. Post-Condition:a. Success End Condition: The user successfully logged

into his account.

b. Failure End Condition: Re-enter details or cancel.

3.2. Supplementary Requirements

o System should work for 24 X 7.o The interaction should be made dynamic and more interactive


24/24




o Provide good performance to the client request

4. Supporting Information

Table of Figures

1. Use Case Diagram..8

2. Architecture Diagram.11

3. Database Design.12

4. Maintain User Details.14

5. Maintain Spot Details.16

6. Maintain User Details.14

7. Maintain Images.15

8. Maintain Hotel Details... 17

5. Concerns / Queries / Doubts if any:

The specification does not specify whether the booking is to be

intimated to the user or not.

The booking is only for the registered users or for the general usersalso.

Date post:	30-May-2018
Category:	Documents
Upload:	deepakkakkar
View:	219 times
Download:	0 times

Info Intellects

Documents