Smart City Version 1.

0
Software Requirements Specification 27/02/2011
Automators

Automators

Smart City

Software Requirements Specification

Version 1.0

Team Guide: Kamal Sethi

Members: Prabhat Nagar

PriyankaAgrawal
PriyankaLokhande
Raksha Nagar

College Name: Acropolis Institute of Technology and Research

Department: Information Technology

State: Madhya Pradesh

 Smart City Version 1.0
Software Requirements Specification 27/02/2011
Automators

Table of Contents

1.0 Introduction
1.1 Purpose
1.2 Scope
1.3 Definition, Acronyms, and Abbreviations
1.4 References
1.5 Technologies to be used
1.6 Overview

2.0 Overall Description

2.1 Product Perspective
2.2 Software Interface
2.3 Hardware Interface
2.4 Product Function
2.5 User Characteristics
2.6 Constraints
2.7 Architecture Design
2.8 Use Case Model Description
2.9 Class Diagram ........................................................................
Sequence Diagrams ...............................................................
2.10 Database Design ....................................................................
2.11.1 ER Diagram ...............................................................
2.11.2 Schema ......................................................................
2.12 Assumptions and Dependencies

3.0 Specific Requirements

3.1 Use Case Reports
3.2 Supplementary Requirements

4.0 Supporting Information

5.0 Concerns/ Queries/ Doubts (if any)

 Smart City Version 1.0
Software Requirements Specification 27/02/2011
Automators

Software Requirements Specification

ANSI/IEEE SRS Standard 830-1984

1.0 Introduction:.

The Project ‘Smart City’ gives a web based platform to your city to be showcased for all it
has in terms of unique business, places to see, things to do, use local transport for a new
traveler etc. It also try and make some money by charging people for at least 4 services
that may be offered.

1.1 Purpose:.

The SRS provides an overview of the entire web application that involves different
functionalities to the different kind of the users of the site. The functionality includes all the
basic requirements /essentials in the city such as basic information, attractions of the city,
business and economy, tours and travels, essential helplines, education, art and culture,
chat services, discussion forums etc.
Thus, the users range over a wide variety of people of all age groups and service seekers.

 This Web Application provides facility to all the users seeking information of a particular
city.
 It saves time as it allows number of users to access a number of services at one
destination at once.
 Administrator has a privilege to create, modify and delete the records of information,
hence making the site a dynamic source of information.
 User can register, login with his specific id, and can see the results as well for the
particular interactive services.
 The user can activate various value added services also for particular usage.

1.2 Scope: The Scope of the ‘Smart City’ includes:

Present Scenario : There is as such no platform where all the city information can be
viewed together. The user has to switch to different sites to get different functionality or
services.

Proposed System : The currently developed system has all the features that support any
one looking for information of your city, tourists coming to your city, businessmen coming
to your city and people trying to get some help to do business remotely. Since, it provides
a variety of services hence it has many users also, giving a wide exposure to other users.
Each section in the site provides different functionality to the users.
 Smart City Version 1.0
Software Requirements Specification 27/02/2011
Automators

1.3 Definitions, Acronyms, and Abbreviations:

• HTML (Hyper Text Markup Language): It is used to create static web pages.

• JSP (Java Server Pages): It is used to create dynamic web content.

• J2SE (Java 2 Standard Edition): It is a programming platform, belonging to the Java

platform, which is used for developing and running distributed java applications and web based
application.

• WASCE (WebSphere Application Server Community Edition): It is an application server

that runs and supports the J2EE and the web service applications.

• DB2 (IBM Database 2): It is a database management system that provides a flexible and
efficient database platform to raise a strong "on demand" business applications.

• HTTP (Hyper Text Transfer Protocol): It is a transaction oriented client/ server protocol
between a web browser and a web server.

• XML (Extensible Markup Language): It is a markup language that was designed to

transport and store data.

• Ajax (Asynchronous Java Script and XML): It is a technique used in java script to create
dynamic web pages.

• Web 2.0: It is commonly associated with web applications which facilitate interactive
information sharing, interoperability, user-centered design and collaboration on the World Wide
Web.

DNS :

1.4 References:

This web application has been prepared on the basis of discussion with Team members,
faculty members and also taken information from following books & website.

1.4.1 Websites:
 Smart City Version 1.0
Software Requirements Specification 27/02/2011
Automators

www.google.co.in
www.indoreonline.com
www.virtualpune.com
www.pondyonline.com
www.abudhabi.com
www.informationcity.com
www.gurgaonsite.com

1.4.2 Books :
Software Engineering : A practitioner’s approach Ed. By Pressman, Roger

1.5 Technologies to be used:

• J2EE: (Servlet, JSP, JAXP) Application architecture.

• JAVA: Application architecture.

• WASCE: (WebSphere Application Server Community Edition) Web Server

• DB2: IBM Database.

• Ajax: Asynchronous Java Script and XML.

• XML: Extension Markup Language.

• Web 2.0: RSS Feed 2.0.

• RAD 7.0: Development tool.

• Localization: Language – English, Hindi

1.6 Overview:

The SRS will include two sections, namely: overall description and specific requirement.
The overall description describes all aspects of the system according to the user point of
view as well as the analyst and the development and deployment team. The specific
requirement section includes everything in terms of the basic needs of the systems, its
 Smart City Version 1.0
Software Requirements Specification 27/02/2011
Automators

dependence on other systems/ application and the conditions necessary to run the
application smoothly.

2.0 Overall Description:

The web site provides all the services under one roof ie. At one stop destination for all it
has like Information of the city, map of the city, directory and geography of the city,
attractions of the city, business in city, tour and travels, essentials in city, education, art
and culture, chat services and discussion forums etc.
The site can be surfed by as many as users at a time on a multiprocessing system with a
good performance. The site is estimated to achieve a 24X7 availability across the network
despite of the administrator’s fault recovery/updation. The synchronization amongst all the
users shall be maintained and shall not dim the performance of the site working. Since, the
site uses Mozy for backup and will have DNS fail over service enabled it does not suffers
serious faulty conditions. The site contains three sub-domains that helps backing up your
site.

2.1 Product Perspective:

The web application is an independent product which doesnot involves any other
application but at the same time can be used to contain in some other application. These
extension might require some extra overheads.

2.2 Software Interface:

Front End Client: .HTML, Web Browser, Windows XP/2000/Vista

Web Server: HTML, Windows XP/2000/Vista

Data Base Server: IBM DB2, Windows XP/2000/Vista

Back End: J2SE, Windows XP/2000/Vista

2.3 Hardware Interface:

Server Side:
 Operating System: Windows 9x/xp
 Processor: Pentium 3.0 GHz or higher
 RAM: 256 Mb or more
 Hard Drive: 10 GB or more
 Smart City Version 1.0
Software Requirements Specification 27/02/2011
Automators

Client side:
 Operating System: Windows 9x or above, MAC or UNIX.
 Processor: Pentium III or 2.0 GHz or higher.
 RAM: 256 Mb or more

2.4 Product Functions:.

The product broadly specifies functions under three categories as follows :

1. Information of the city
This includes History of the city(social as well as political), facts and figures, news with
temperature updates, classifieds, job career and matrimonial.
2. Geography
This contains map of the city, directory and geography of the city.
3. Attractions of the city
This includes information regarding restaurants, hotels, shopping, cinemas, nightlife,
exhibitions etc.
4. Business in city
Includes economy, yellow pages, real estate and new business opportunities.
5. Tour and travels
This includes places to visit and travel deals.
6. Essentials in city
Involves everything ranging from health, bank ATMs, flights, showrooms to all related
helpline and enquiry.
7. Education, art and culture
8. Chat and discussion forums.

2.5 User Characteristics:.

Since the site focuses on all the functionalities hence it has many different users or actors
seeking for information of city and its unique business, places to see, things to do,
students, surfers of city. It also gives platform to user who would like to place their views
on discussion forums or chat with the city people. Another important services like bank
ATMs, flights, showrooms and all related helpline and enquiries makes it useful for all
categories of user..

2.6 Constraints:

The following constraints/ design constraints can be faced by the proposed system :

 The extension of these application with the use of other technologies would be difficult.
 Smart City Version 1.0
Software Requirements Specification 27/02/2011
Automators

 The deployment of application on different operating systems would increase the

overhead.
 The design can still be made lucid to understand by the user.
 The application can be further extended for many different purposes but would require
reviewing of concepts of the project.
 The load of many simultaneous users on storage shall be problematic hence should be
controlled and taken care of.
 Too much reliance on other application like Mozy, DNS fault recovery services, maps
@ google, Google analytics may also generate some problem.

Unified Modeling Language

UML stands for Unified Modeling Language. It represents a unification of the concepts and
notations presented by the three amigos in their respective books1. The goal is for UML to
become a common language for creating models of object oriented computer software.
In its current form UML is comprised of two major components: a Meta-model and a
notation. In the future, some form of method or process may also be added to; or
associated with, UML.

The Meta-model
UML is unique in that it has a standard data representation. This representation is called
the metamodel. The meta-model is a description of UML in UML. It describes the objects,
attributes, and relationships necessary to represent the concepts of UML within a software
application.
This provides CASE manufacturers with a standard and unambiguous way to represent
UML
models. Hopefully it will allow for easy transport of UML models between tools. It may also
make it easier to write ancillary tools for browsing, summarizing, and modifying UML
models.
A deeper discussion of the metamodel is beyond the scope of this column. Interested
readers can learn more about it by downloading the UML documents from the rational web
site2.

The Notation
The UML notation is rich and full bodied. It is comprised of two major subdivisions. There is
a
notation for modeling the static elements of a design such as classes, attributes, and
relationships. There is also a notation for modeling the dynamic elements of a design such
as objects, messages, and finite state machines.

2.7 Architecture Design:

 Smart City Version 1.0
Software Requirements Specification 27/02/2011
Automators

As this is a batch processing-type system with inputs coming and output being produced,
the most natural style will be the pipe-and-filter style. We use this style for the architecture
of the system. The proposed architecture is shown below.

This architecture has three filter components – one to process the information provided
in File 1, the other to process the information provided in File 2, and the third to produce
the schedule. As the information produced by the first component is also used in the
processing of information from File 2 as well as for scheduling, the connections are set
accordingly. In this architecture, we do not require that the components be executed in
parallel. For ease of implementation, they may be executed in a sequential order,
particularly since
the file processing modules are not likely to consume much time – the main processing
time will be needed by the third component and that remains the same in parallel or serial
execution. Any (synchronous or asynchronous) method can be used to support the pipes.

2.8 Use Case Diagram :

An important part of the Unified Modeling Language (UML) is the facilities for drawing use
case
diagrams. Use cases are used during the analysis phase of a project to identify and
partition system functionality. They separate the system into actors and use cases. Actors
represent roles that can are played by users of the system. Those users can be humans,
other computers, pieces of hardware, or even other software systems. The only criterion is
that they must be external to the part of the system being partitioned into use cases. They
must supply stimuli to that part of
the system, and the must receive outputs from it. Use cases describe the behavior of the
system when one of these actors sends one particular stimulus. This behavior is
described textually. It describes the nature of the stimulus that triggers the use case; the
inputs from and outputs to other actors, and the behaviors that convert the inputs to the
outputs. The text of the use case also usually describes everything that can go wrong
during the course of the specified behavior, and what remedial action the system will take.
 Smart City Version 1.0
Software Requirements Specification 27/02/2011
Automators

2.9 Class Diagram:

The purpose of a class diagram is to depict the classes within a model. In an object
oriented application, classes have attributes (member variables), operations (member
functions) and relation-ships with other classes. The UML class diagram can depict all
these things quite easily. The fundamental element of the class diagram is an icon the
represents a class.

A class icon is simply a rectangle divided into three compartments. The topmost
compartment contains the name of the class. The middle compartment contains a list of
attributes (member variables), and the bottom compartment contains a list of operations
(member functions). In many diagrams, the bottom two compartments are omitted. Even
when they are present, they typically do not show every attribute and operations. The goal
is to show only those attributes and operations that are useful for the particular diagram.
This ability to abbreviate an icon is one of the hallmarks of UML. Each diagram has a
particular
purpose. That purpose may be to highlight on particular part of the system, or it may be to
illuminate the system in general. The class icons in such diagrams are abbreviated as
necessary. There is typically never a need to show every attribute and operation of a class
on any diagram.

Sequence Diagrams:

Collaboration diagrams allow the designer to specify the sequence of messages sent
between objects in a collaboration. The style of the diagram emphasizes the relationships
between the objects as opposed to the sequence of the messages. In this column we will
be discussing UML Sequence diagrams. Sequence diagrams contain the same information
as Collaboration diagrams, but emphasize the sequence of the messages instead of the
relationships between the objects.

2.10.1 Database Design:

2.10.2 ER Diagram:

Entity Relationship Diagrams (ERDs) illustrate the logical structure of databases.

Smart City Version 1.0
Software Requirements Specification 27/02/2011
Automators

An ER Diagram

Entity Relationship Diagram Notations

Peter Chen developed ERDs in 1976. Since then Charles Bachman and James Martin
have added some sligh refinements to the basic ERD principles.

Entity
An entity is an object or concept about which you want to store information.

Weak Entity
A weak entity is an entity that must defined by a foreign key relationship with another entity
as it cannot be uniquely identified by its own attributes alone.

Key attribute
A key attribute is the unique, distinguishing characteristic of the entity. For example, an
employee's social security number might be the employee's key attribute.

Multivalued attribute
A multivalued attribute can have more than one value. For example, an employee entity
can have multiple skill values.
Smart City Version 1.0
Software Requirements Specification 27/02/2011
Automators

Derived attribute
A derived attribute is based on another attribute. For example, an employee's monthly
salary is based on the employee's annual salary.

Relationships
Relationships illustrate how two entities share information in the database structure.
Learn how to draw relationships:
First, connect the two entities, then drop the relationship notation on the line.

Cardinality
Cardinality specifies how many instances of an entity relate to one instance of another
entity.
Ordinality is also closely linked to cardinality. While cardinality specifies the occurences of
a relationship, ordinality describes the relationship as either mandatory or optional. In other
words, cardinality specifies the maximum number of relationships and ordinality specifies
the absolute minimum number of relationships.

Recursive relationship
In some cases, entities can be self-linked. For example, employees can supervise other
employees.
 Smart City Version 1.0
Software Requirements Specification 27/02/2011
Automators

2.11 Assumptions and Dependencies:

Full working of the application is dependent on the availability of Internet connection.

• Assumptions:
In general it has been assumed that the user has complete knowledge of the system that
means user is not a naïve user. Any data entered by him/her will be valid. To make the
application as user friendly as possible but at the same time keeping in minds user
requirements.
 Server OS should be Windows NT/2000/XP.
 Client PC should be Windows 9X/NT/WorkStation or Windows 2000with latest service
pack.
• Dependencies:
The applications or algorithms on which it is dependent are assumed to work properly. It
depends that the one should follow the international standards for the generating the User
ID & should fill the related information in the proper format.

3.0 Specific Requirements

3.1 Use Case Reports:

3.2 Supplementary Requirements:

Functional Requirements :

i. Complete Map of the city with key markets and places to see marked – preferably usage
of static map and live Map option
ii. Complete History of the city – social, political
iii. Complete overview of the businesses in the city
iv. Secure registration of all users including a personal profile –only at the time of a
transaction providence
v. Complete Search/Site Map of the entire site for easy access
vi. Start atleast 4 paid services like SMS alerts for city news,market daily rates, advertises
etc.
vii. Local news, government notices, update
viii. Facilitate communication between user, experts andgeneral public through - Discussion
forum/chat/mail/polls
Smart City Version 1.0
Software Requirements Specification 27/02/2011
Automators

ix. Local language support at user-interface and database level.

User Interfaces
Application will be accessed through a Browser Interface. The interface would be viewed
best using 1024 x 768 and 800 x 600 pixels resolution setting. The software would be fully
compatible with Microsoft Internet Explorer for version 6 and above. Admin would not be
able to access any part of the application without logging on to the system.

Communication interfaces
The application demands at least a 256 kbps Cable Modem Broadband/ Digital Subscriber
Link (DSL)/ HST at the client side for communication with the server.

Performance Requirements
Some Performance requirements identified is listed below:
The software shall support use of multiple users at a time. As faster technology came onto
the scene and e-commerce and Internet adoption evolved, users were less tolerant of slow
Web site response times. If pages took more than eight seconds to download, chances
were good that users would direct their browsers elsewhere. Although the average site
response time was approximately 17 seconds in mid-2001, this "eight-second rule" was
something of a standard for Internet marketers, for whom such lost visitors represented lost
revenue.
The site can be surfed by as many as users at a time on a multiprocessing system. The site
is estimated to achieve a 24X7 availability across the network despite of the administrator’s
fault recovery/updation. The synchronization amongst all the users shall be maintained and
shall not dim the performance of the site working. Since, the site uses Mozy for backup and
will have DNS fail over service enabled it doesnot suffers serious faulty conditions. The site
contains three sub-domains that helps backing up your site. A minimum of 1024 Mb/1 Gb
web space will be allotted with unlimited database space. The database shall be able to
accommodate a minimum of 10,000 records of students.
All the performance requirement are verifiable.

Safety Requirements
The database may get crashed at any certain time due to virus or operating system failure.
Therefore, it is required to take the database backup. Since, the site uses Mozy for backup
and will have DNS fail over service enabled it doesnot suffers serious faulty conditions. The
site contains three sub-domains that helps backing up your site.

Security Requirements
Smart City Version 1.0
Software Requirements Specification 27/02/2011
Automators

Some of the factors that are identified to protect the software from accidental or malicious
access, use, modification, destruction, or disclosure are described below.
1 Keep specific log or history data sets
2  A ssign certain functions to different modules
3 Restrict communications between some areas of the program
4 Check data integrity for critical variables
5 I t will incorporate encryption techniques in the user/license authentication process.
Communication needs to be restricted when the application is validating the user or license.
(i.e., using https).

Software Quality Attributes

The Quality of the System is maintained in such a way so that it can be very user friendly to
all the users.
The software quality attributes are assumed as under:
1)Accurate and hence reliable.
2) Secured.
3) Fast speed.
4) Compatibility.
Smart City Version 1.0
Software Requirements Specification 27/02/2011
Automators