Software Requirements

Specification
For

<smart city>
Version 1.0 approved

A .UPENDER O7E01A0563

K.NITHIN REDDY 07E01A0552

K.SANTHOSH REDDY 07E01A05A8>

<Nizam Institute of Engineering and Technology>

<Date: 13-08-2010>
Table of Contents
Table of Contents.........................................................................................................................iin
Revision History.............................................................................................................................ii
1. Introduction..............................................................................................................................1
1.1 Purpose...........................................................................................................................................1
1.2 Document Conventions...................................................................................................................1
1.3 Intended Audience and Reading Suggestions.................................................................................1
1.4 Project Scope..................................................................................................................................1
1.5 References......................................................................................................................................1
2. Overall Description..................................................................................................................2
2.1 Product Perspective.........................................................................................................................2
2.2 Product Features.............................................................................................................................2
2.3 User Classes and Characteristics.....................................................................................................2
2.4 Operating Environment...................................................................................................................2
2.5 Design and Implementation Constraints.........................................................................................2
2.6 User Documentation.......................................................................................................................2
2.7 Assumptions and Dependencies......................................................................................................3
3. System Features.......................................................................................................................3
3.1 System Feature 1.............................................................................................................................3
3.2 System Feature 2 (and so on)..........................................................................................................4
4. External Interface Requirements...........................................................................................4
4.1 User Interfaces................................................................................................................................4
4.2 Hardware Interfaces........................................................................................................................4
4.3 Software Interfaces.........................................................................................................................4
4.4 Communications Interfaces.............................................................................................................4
5. Other Nonfunctional Requirements.......................................................................................5
5.1 Performance Requirements.............................................................................................................5
5.2 Safety Requirements.......................................................................................................................5
5.3 Security Requirements....................................................................................................................5
5.4 Software Quality Attributes............................................................................................................5
6. Other Requirements................................................................................................................5
Appendix A: Glossary....................................................................................................................5
Appendix B: Analysis Models.......................................................................................................6
Appendix C: Issues List.................................................................................................................6

Revision History
Name Date Reason For Changes Version
1. Introduction
1.1 Purpose

The system aims at showcasing city information in terms of unique business, places to
see, things to do, providing transport/cab information and lodging accommodation at a guest
house.

1.2 Document Conventions

The document is uniformly sprawled by the following typographical conventions that

were intentionally used to elucidate the SRS:
Styles and Formatting:
 Aligned At : Left of the page
 Text Font : Times New Roman, 12
 Heading Font : Times New Roman (Bold), 18
 Sub-heading Font : Times New Roman (Bold), 14
 Bullet Style : Vital Category Classifications
 Text Line Spacing : 1.5
 Margins :Top(1 inch )
Left (1.5 inch)
Right (1 inch)
Bottom (1 inch)

1.3 Intended Audience and Reading Suggestions

Intended for Project Managers, Developers, End users and Quality Assurance
engineers. Suggested reading the document would be overall document description,
Product based information gathering followed by Infrastructure requirement
1.4 Project Scope

 Covers the requirements of a tourist or businessmen visiting the city.

 Information at the click of a button.
 Provide transportation services in the form of cabs
 Provide lodging/guest house information.

1.5 References

 www.tgmc.in
 www.cuil.com
 www.pcmag.com
 www. compuware.com

2. Overall Description
2.1 Product Perspective

Tourism becomes the important income of most of the states in India. This Product
explores the specialties of Andhra Pradesh. It provides helpful information such as nearest
hospitals, Police Stations, Tourist Places along with the image and road map, etc… Easy way of
booking and cancellation of Guest house for stay is included. Transportation facilities in terms of
call taxi are provided where the tourist or the business man can book for cab in advance.
• Tourism information only as static data available
• Information is scattered and available across different sites and hence tourist has
to visit websites on a probability.
• Lodging and cab service information have to be communicated with different
vendors.
2.2 Product Features

Tourism becomes the important income of most of the states in India. This Product
explores the specialties of Andhra Pradesh. It provides helpful information such as nearest
hospitals, Police Stations, Tourist Places along with the image and road map, etc… Easy way of
booking and cancellation of Guest house for stay is included. Transportation facilities in terms of
call taxi are provided where the tourist or the business man can book for cab in advance.

2.3 User Classes and Characteristics

 Administrator

Software is used by any site admin, who maintains the tourist places, Police
stations and Hospital Information, Guest House booking, and Cab Service booking and
cancellation. The business man / tourist to view the places, and book for cab and Guest
House. Cab Service. Guest Administrator to view the Guest House bookings and
cancellations, Cab Service Admin to view the Cab Service Booing and cancellations.

2.4 Operating Environment

The product is user friendly and its accessibility from the server is easy. The application
is reliable and ensures safe communication of data between the user and the server. As it is
developed in .Net it is highly interoperable with OS that have provided support for .Net runtime.
The system requires less maintenance as it is hosted on the ISP.

Software Requirements:

System : Windows 2000 or Higher

 Platform : .Net
Scripting : ASP.Net
Code Behind : C# (C Sharp)
Backend : Ms-Access/SQL Server

Hardware Requirements:
Processor : P IV
RAM : 512 MB
Hard Disk : 40 GB
Monitor : VGA Color (256)

2.5 Design and Implementation Constraints

The Unified Modeling Language (UML) is used to specify, visualize, modify, construct and
document the artifacts of an object-oriented software intensive system under development. UML
offers a standard way to visualize a system's architectural blueprints, including elements such as:

 actors
 business processes
 (logical) components
 activities
 programming language statements
 database schemas, and
 reusable software components.

UML combines techniques from data modeling (entity relationship diagrams), business modeling
(work flows), object modeling, and component modeling. It can be used with all processes,
throughout the software development life cycle, and across different implementation
technologies.UML has synthesized the notations of the Booch method, the Object-modeling
technique (OMT) and Object-oriented software engineering (OOSE) by fusing them into a
single, common and widely usable modeling language. UML aims to be a standard modeling
language which can model concurrent and distributed systems. UML is a de facto industry
standard, and is evolving under the auspices of the Object Management Group (OMG).

2.6 User Documentation

The application is reliable and ensures its functioning from the client and maintains
tourist places, guest house booking/cancellation, cab booking/cancellation

2.7 Assumptions and Dependencies

• Tourism information only as static data available

• Information is scattered and available across different sites and hence tourist has
to visit websites on a probability.
• Lodging and cab service information have to be communicated with different
vendors.

3. System Features
3.1 Customer Information Maintenance
3.1.1 Description and Priority
The module allows the administrator to maintain places of interest to the
tourist/business people. Each new place is associated with an id that is then used by
the seeker or administrator to reference the place. Image of the important place is
associated for every tourist place. And a road map is attached with the place for the
business people to reach the place when they come by their own transportation.

3.1.2 Stimulus/Response Sequences

Tourism becomes the important income of most of the states in India. This Product
explores the specialties of Andhra Pradesh. It provides helpful information such as nearest
hospitals, Police Stations, Tourist Places along with the image and road map, etc… Easy way of
booking and cancellation of Guest house for stay is included. Transportation facilities in terms of
call taxi are provided where the tourist or the business man can book for cab in advance.

3.1.3 Functional Requirements

1. Login and Security.
The module restricts the usage of certain modules only to authorized users. The system defines
users with permissions to access the application. A database is maintained to keep track of users

2. Tourist/Business Place Record Maintenance

The module allows the administrator to maintain places of interest to the tourist/business
people. Each new place is associated with an id that is then used by the seeker or
administrator to reference the place. Image of the important place is associated for every
tourist place. And a road map is attached with the place for the business people to reach
the place when they come by their own transportation.

3. Information Explore

It is important for any public, who is not aware of the infrastructure of the city, to have
the information about the nearest hospitals and police stations. That will reduce the
burden when some body falls in sick, or any theft happened.

4. Booking and Cancellation

This site facilitates the registered customers (tourist/Business people) to book the guest
house online. And they can avail the facility of Cab booking too online
 5. Reports
6. The module generates reports on Bookings, cancellations, various tourist places, hospitals
etc.

1.1 Tracking
3.2.1 Description and Priority

It is important for any public, who is not aware of the infrastructure of the city, to have
the information about the nearest hospitals and police stations. That will reduce the
burden when some body falls in sick, or any theft happened.

3.2.2 Stimulus/Response Sequences

The module allows the administrator to maintain places of interest to the tourist/business people.
Each new place is associated with an id that is then used by the seeker or administrator to
reference the place. Image of the important place is associated for every tourist place. And a road
map is attached with the place for the business people to reach the place when they come by their
own transportation

3.2.3 Functional Requirements

The feature is provided by installing the web server IIS that listens to incoming request from remote clients using
dedicated port number. These are configured by the website administrator. Exception handling is provided in ord
isolate abnormal Conditions. Validations of numeric and non-numeric inputs are done at the time of data submiss
the end user.
4. External Interface Requirements
1.2 User Interfaces

The application has to be provided with key board shortcuts and a facility to use
the mouse to trigger the required actions .they act as shortcuts and provide an easy
navigation within the software .Output data to the user including error messages and
exceptions are displayed through dynamic HTML

Interface between the Software and its users:

The product is user friendly and its accessibility is from the clients.
1. Screen formats
Screen formats are required to be created with following features:-
a) Must be user friendly
b) Mandatory fields must be indicated by an astriek (*).
c) Form elements should suggest default values and valid input range should be mentioned
wherever it’s required.
2. Web page or window layouts
Each screen should have-
a) Menu driven facility
b) Uniformity
c) Consistency

1.3 Hardware Interfaces

1.4 Software Interfaces

1.5 Communications Interfaces

2. Other Nonfunctional Requirements

2.1 Performance Requirements

Less network congestion, shortest route to reach the server would enhance the speed of the
application.A RDBMS can be preferred to enhance security,shared access and store larger
volume of data.

2.2 Safety Requirements

No harm is expected from the use of the product either to the OS or any data that resides on .
2.3 Security Requirements

The product is protected from un-authorized users from using it. The system allows only
registered users to work on the application. The users are the manager training and the employee
of the organization.

2.4 Software Quality Attributes

The product is user friendly and its accessibility from the server is easy. The application is
reliable and ensures safe communication of data between the user and the server. As it is
developed in .Net it is highly interoperable with OS that have provided support for .Net runtime.
The system requires less maintenance as it is hosted on the ISP.

3. Other Requirements
Define any other requirements not covered elsewhere in the SRS. This might include database
requirements, internationalization requirements, legal requirements, reuse objectives for the
project, and so on. Add any new sections that are pertinent to the project.>

Appendix A: Glossary
<Define all the terms necessary to properly interpret the SRS, including acronyms and
abbreviations. You may wish to build a separate glossary that spans multiple projects or the
entire organization, and just include terms specific to a single project in each SRS.>

Appendix B: Analysis Models

<Optionally, include any pertinent analysis models, such as data flow diagrams, class diagrams,
state-transition diagrams, or entity-relationship diagrams.>

Appendix C: Issues List

< This is a dynamic list of the open requirements issues that remain to be resolved, including
TBDs, pending decisions, information that is needed, conflicts awaiting resolution, and the like.>