SWAMI KESHVANAND INSTITUTE OF TECHNOLOGY

SMART CITY
SOFTWARE REQUIREMENT
SPECIFICATION

Team Name
Phenix

Team Members
Arpit Bhargava
Arpan Agarwal
Ashish Jangid
Aditi Mehta

Project Guide
Mr. Harpreet Singh Gill

Index & Tables

1) Introduction:
.........................................................................................................................3
1.1)
Purpose: .......................................................................................................................
........3
1.2)
Scope: ..........................................................................................................................
.........3
1.3)
Abbreviations: ..............................................................................................................
........3
1.4)
References: ..................................................................................................................
.........5
1.5)
Technologies: ...............................................................................................................
.........5

2) Overall
Description: ..................................................................................
..6
2.01) Product
Perspective: ........................................................................................................... 6
2.02) Software
Interface: ..............................................................................................................7
2.03) Hardware
Interface: ............................................................................................................7
2.04) Communication
Interface: ..................................................................................................7
2.05) Product
Function: ............................................................................................................... 7
2.06) User
Characteristics: ............................................................................................................
8
2.07)
Constraints: .................................................................................................................
...... .8
2.08) Use-Case Model
Survey: ......................................................................................................8
2.09) Architecture
diagram: .........................................................................................................10
2.10) Database
design: .................................................................................................................11

2.11) Assumptions and

Dependencies: ........................................................................................14

3) Specific Requirements:
............................................................................... 14
3.1) Use-Case
Reports: .................................................................................................................14
3.2) Supplementary
Requirements: ............................................................................................. 43

1)Introduction:
1.1)Purpose: Smart city provides a web-based platform
to a city for the
Quality it has like the business opportunities,hot tourist
destinations,a
Guide to an outsider about everything he wants, and
also charge money
From people for using some paid services.
1.2) Scope:

Create different system users and assign different

roles with
related permissions.

Manage all the account details such as user name,

company,
phone numbers , address , email addresses of all
the customer
from one central loaction .
Track all the customers and their contact details.
Maintain the services provided to the customer
through Service Level agreements.
Complete Map of the city with key markets and
places to see
Marked preferably usage of static map and live
map option.
Complete History of the city social, political.
Complete overview of the businesses in the city.
Secure registration of all users including a
personal profile only at the time of transaction
providence.
Complete Search/Site Map of the entire site for
easy access.

Start atleast 4 paid services like SMS alerts for

city news , market daily rates etc.

Local news, government notices, update

 Facilitate communication between user, experts

and general public through discussion
forums/chats/mails/polls
Local language support at user-interface and
database level.

1.3) Abbreviations:
SLA: SLA is a formal written agreement made
between two parties the service provider and the
service recipient.It defines the term the term of
engagement-the fundamental rules that will
govern the relationship.
Support transaction: Communication between
support manager and the customer regarding the
service provided, query and feedback.
Payment transaction: Transaction between
account manager and the customer for all the
services being used.
Personal details: Details of customer such as
username, company, Address, e-mail etc.
Contact details: Details of contact persons
associated with the customer.
HTML: Hypertext Markup Language is a markup
language used to Design static web pages.
EJB: Enterprise Java Beans.
J2EE: Java 2 Enterprise Edition is a programming
platform part of the java platform-for developing
and running distributed multi-tier architecture java

applications based largely on modular software

components.
DB2: DB2 Database is the database management
system that Delievers a flexible and cost effective
database platform to build Robust on demand
business applications.
WAS: Web sphere application server is an
application server that Runs business applications
and supports the J2EE and web services
Standards.
WSAD: Web sphere studio application developer
is a toolkit which is Designed for the creation of
the more complex projects,providing Fully dynamic
web application using EJBS.
HTTP: Hypertext Transfer Protocol is a transaction
oriented client/Server protocol between web
browser and web server.
HTTPS: Secure Hypertext Transfer Protocol is a
HTTP over SSL.
TCP/IP: Transmission Control Protocol/Internet
Protocol, the suite of Communication protocols
used to connect hosts on the Internet.TCP/IP uses
several protocol -two main ones being TCP and IP.

1.4) References:
IEEE SRS Format
Problem Definition (Provided by IBM)

 CT Arrington. Enterprise Java with UML. OMG

Press.
1.5) Technologies:
J2EE: Application Architecture
DB2: Database
WAS: Web Server
Rational: Design Tool

1.6) Overview: SRS will include two sections:

Overall Description will describe major components
of the system,
Interconnection and external interfaces.
Specific Requirements will describe the functions of
actors ,their role in System and constraints.

2) Overall Description:
Describe the general factors that affect the product and its
requirements.
2.01) Product Perspective:
HTML
CLIENT
(CUSTOMER)

HTTP/HTT
PS

|
|
WAS

CLIENT
CLIENT SIDE
SOFTWARE

APPLICATION

TCP/IP

DATABASE

(SYSTEM
USER)

SERVER

SERVER

The web pages (XHTML/JSP) are present to provide the

user interface on customer client side. Communication
between customer and server is provided through
HTTP/HTTPS protocolas.
The Client Software is to provide the user interface on
system user client side and for this TCP/IP protocols are
used.
On the server side web server is for EJB and database
server is for storing the information.

2.02) Software Interface:

Client on Internet: Web Browser, Operating System (any)
Client on Intranet: Client Software, Web Browser, Operating
System (any)
Web Server: WAS, Operating System (any)

DB2

Data Base Server: DB2, Operating System (any)

Development End: WSAD (J2EE, Java, Java Bean, Servlets,
HTML),
DB2, OS (Windows), Web Server.
2.03) Hardware Interface:

CLIENT SIDE
Processor
Internet
explorer 6.0

Pentium II at
500

RAM

Disk space

64 MB

1GB

MHZ
SERVER SIDE
WEBSPHERE
APPLICATION
SERVER V5.0

Pentium III at 512 MB

1

DB2 V8.1

Pentium III at 512 MB

1

2 GB

GHZ

GHZ

1
GB(excluding
data size)

2.04) Communication Interface:

Client on Internet will be using HTTP/HTTPS protocol.
Client on Intranet will be using TCP/IP protocol.

2.05) Product function:

 Track Account Level Data: In this module, receivables from

customer are
maintained.
Service Level Agreements: It contains the agreements of
providing the services provided for service and customer.
User Contact Information: It maintains all the details
(Personal, Official, Contact, and company of customer).
Track Support Transactions: Maintenance of transactions
related to the services provided to the customer.
Maintaining Logs: Activities of the System Users can be
tracked through the logs , which is maintained by the
system.

2.06) User Characteristics: Every user should be comfortable

of working with computer and net browsing.
2.07) Constraints:
GUI is only in English.
Login and password is used for identification of
customer and there is no facility for guest.
This system is working for single server.
There is no maintainability of back up so availability will
get effected.
Limited to HTTP/HTTPS.
2.08) Use Case Model Survey:

USE CASE DIAGRAM

1. Administrator: Responsible for managing system users,

viewing logs and managing standard groups of the system.
Manage System Users: The Administrator will create
different roles. The system users will be created and will be
assigned with the different roles. More than one task and
permissions can be granted or revoked from the system
users.
View Logs: Responsible for checking the logs of different
system user for auditing and maintaining the integrity of the
system.
Manage Standard Groups: Standard groups will be
created and updated by the administrator, which will be
visible to all the system users.
View All Details: View the customer details, payment
details, purchase details, daily service transaction details.
Update the system: updation of the information on system
will be done.

2. Support Manager: Responsible for managing and updating

paid services,providing information on website for access by
customer.
View All Details: View the customer details, payment
details, daily service transaction details.
Manage paid services: management of paid services will
be done
Updation paid services: updation of paid services will be
done .

 Provide information : information on website for access

purpose will be provided by support manager.
3. Account Manager: Manage all the payment details (of the
services used ).
Manage Payment Transaction: Store all the payment
transactions made by the customer and update the payment
information.
View All Details: View the customer details, payment
details, daily service transaction details.
4. Help Manager: Responsible for handling online help and
management of discussion forums etc.
Manage online help: management of online help will be
done.
Manage discussion forums: management of discussion
forums and chats etc will be done.
5. Customer: Person/ Company who is facilitated by the system.
View Own Details: Customer can view his personal details,
payment details, details about services provided and the
transaction details for the services.
Access information: Customer will access information on
website for his usage.
Access paid services: Customer will access the paid
services provided by the system like sms alerts.
Pay for paid services: Customer will pay for the paid
services which he has subscribed to.

2.10) Database design:

2.11) Assumptions and Dependencies:

The details related to the product, customer, payment and
service transaction provided manually.
Administrator is created in the system already.
Roles and tasks are predefined.

3) Specific Requirements:

3.1) Use-Case Reports:

i) Administrator: Responsible for managing system users,
viewing logs and managing standard groups of the system.
Manage System Users: The Administrator will create
different roles. The system users will be created and will be
assigned with the different roles. More than one task and
permissions can be granted or revoked from the system
users.
View Logs: Responsible for checking the logs of different
system user for auditing and maintaining the integrity of the
system.
Manage Standard Groups: Standard groups will be
created and updated by the administrator, which will be
visible to all the system users.
View All Details: View the customer details, payment
details, daily service transaction details.
Update information on system: update the information
on system for user access.

Name of use-case: View system users

Description: view the list of system users in a role and view
the details of roles, tasks, permissions assigned.
Pre-conditions:
Administrator has already logged in
System users have been already created & assigned
some rules,tasks & permissions
Post-condition: None
Normal flow of events:
Sytem user or role will be selected
Query will be submitted
Corresponding o/p will be generated

Alternate flow of events: None

Name of use-case: Create system users

Description: to create system users
Pre-conditions: Administrator has logged in
Post-condition: a login id is generated

Normal flow of events:

New login name, password, permissions, roles, tasks
will be entered
Save the details

Alternate flow of events:

A message appears for duplicate login name
Administrator has to fill details again

Name of use-case: update details of users

Description: to update the details of users

Pre-conditions:
Administrator has already logged in
System users have already been created
Post-condition: None
Normal flow of events:
Select username
Assign or revoke roles ,tasks , permission

Name of use-case: View logs

Description: To view activities of the system users
Pre-conditions:
Administrator has already logged in
System users have already been created
Post-condition: None
Normal flow of events:
Select username
Select date

Name of use-case: View all details

Description: To view customer details , payment details etc
Pre-conditions:
Administrator has logged in
Customer is already having account
Post-condition: None
Normal flow of events:
Select customer name
Select date

Name of use-case: Update information

Description: update information on system regarding

tourist destinations , business spots ,paid services etc
Pre-conditions: Administrator has logged in
Post-condition: System updated successfully
Normal flow of events:
Validate information
Select the system area to be updated
Save the information

ii.) Account Manager:

Responsible for management of payment transaction

 Management of payment transaction

View details
Receive payment
Acknowledgement for payment received

Name of use-case: Add payment transaction details

Description: All payment transaction details are entered
Pre-conditions: Account manager has logged in
Post-condition: None
Normal flow of events:
Select customer
Select service
Select bill no.
Enter details of recievables

 Save recievables details

Update account of customer
Entry of this adding details event has been logged

Alternate flow of events:

If the recievables will left to fill then system ask for
refilling all the blank details then save details &
update account of customer.

Name of use-case: Edit payment transaction details

Description: previously entered payment transaction

details are entered
Pre-conditions: Account manager has logged in
Post-condition: None
Normal flow of events:
Select customer
Select service
Select receipt no.
Select payment transaction no.
Make changes
Save new details
Update customer account
Entry of this editing event has been logged

Name of use-case: Acknowledgement for payment

received
Description: Acknowledgement for payment given by
customer
Pre-conditions: Account manager has logged in
Post-condition: None
Normal flow of events:
Select customer
Select service
Select receipt no.
Select receivables details
Give acknowledgment
Give acknowledgment
Update customer account
Entry of this acknowledgement event has been logged

Alternate flow of events:

If the recievables details are not there then system
reports an error and ask for recheck.

iii.) Help manager:

Description: responsible for management of online

help,discussion forums,chats etc.
Online help
Discussion forums

Name of use-case: Online help

Description: management of online help
Pre-conditions: help manager has logged in
Post-condition: System updated successfully
Normal flow of events:
Select area for updation
Make changes
Store changes
System help updated successfully

Name of use-case: manage discussion forums, chats etc

Description: management of discussion forums, chats etc.
Pre-condition: Help manager has already logged in
Post-condition: none
Normal flow of events:
Select customer for help
Ask for query
Answer query

iv.) User:
Description: user is the main person who will access the
system. He will access his own details, information on
website, he will access paid services and pay for them.
View own details
Access information on website
Access paid services
Pay for paid services

Name of use-case: View own details

Description: user will view his own details
Pre-condition: user has already logged in
Post-condition: None
Normal flow of events:
Select the detail
See the detail

Name of use-case: Access of information on website

Description: user will access information on website
Pre-condition: user has already logged in
Post-condition: none
Normal flow of events:
Select area to see
Access information in area

Name of use-case: Access paid services

Description: user will access the paid services
Pre-condition: user has already logged in
Normal flow of events:
Select the paid services area
Select the paid service to see
Access details of paid services

Name of use-case: pay for paid services

Description: user will pay for the paid services for which he
has subscribed
Pre-condition: user has already logged in
Post-condition: customer account updated successfully
Normal flow of events:
Select service
See the details
Give receivable information

 Account updated

v.) Support Manager:

Description: He is responsible for managing and
updating the paid
services. He is also responsible for providing information
for updation of
system.

View all details

Manage paid services
Update paid services
Provide information for access on website

Name of use-case: View all details

Description: support manager can view all details of
customers like customer name, payment details etc
Pre-condition: support manager has already logged
in.
Post-condition: none
Normal flow of events:
Select the customer name
Select and see the detail

Name of use-case: Create paid services

Description: Creation of paid services
Pre-condition: Support manager has already logged
in
Post-condition: paid services created successfully
Normal flow of events:
Create paid services
Paid services created successfully

Name of use-case: View paid services

Description: to view the paid services and their details
Pre-condition: Support Manager has already logged in
Post-condition: none
Normal flow of events:

 Select the service to view

View details of service

Name of use-case: update the paid service

Description: update paid services
Pre-condition: Support manager has already logged in
Post-condition: system updated successfully
Normal flow of events:
Create new paid service
Store the changes
System updated successfully
The log detail of this updation event has been saved

Name of use-case: provide information for access on

website
Description: Support manager will provide information for
access purpose
on Website.

Pre-condition: Support manager has already logged in

Post-condition: None
Normal flow of events:
Select the area for which information is to be updated
Provide information for area selected

3.2) Supplementary Requirements:

Have hours of operation that are 24 x 7 - Because
system can be an automated process, so it can stay open for
24 hours a day. If the base is now the entire world ,staying
open 24 hours a day becomes critical. System is required to
be available 24X7 so UPS support must be on server site for
at least 8 hours in case of power failure. System will remain
inaccessible to users at 2:00 to 4:00 am for backup and
maintenance purpose.
Reduce the cost of a sales transaction - To the extent
that one can automate the sales process through this
system, one can start to reduce the cost of that sales
transaction. This is particularly true of mundane sales
transactions where the customer knows what they want.
Make the existing Web site more dynamic in nature Many early Web implementations consisted of static HTML
pages. This becomes very difficult to manage if the number
of pages gets too large. An effective system should be
largely dynamic taking advantage of technology that
automates this process rather than relying on manual
processes. Application should serve dynamic user based
customized web pages to its clients from server.
Tie the existing Web site into existing enterprise
systems Any existing Web site that relies on the manual
duplication of data from another system is one that can be
improved. Most of the business data in the world today

exists in enterprise servers that can be connected to the

Web servers to make this process far more effective.
Provide good performance and the ability to scale the
server The Web Application Server should provide good
performance and the ability to manage performance with
techniques, such as support for caching, clustering, and load
balancing.
Providing session management capability - Web
application developers should not spend valuable time
worrying about how to maintain sessions within the
application. The Web Application Server should provide these
services.