Srs Smart City Edit
Srs Smart City Edit
Srs Smart City Edit
SMART CITY
SOFTWARE REQUIREMENT
SPECIFICATION (DEPARTMENT OF SWE)
BY :
SAGAR VIRMANI
(1201310080)
KISHAN PADARIYA
(1201310122)
Page 1
INDEX
S. No.
Content
Page No.
1.
Introduction
3-6
1.1
Purpose
1.2
Scope
1.3
1.4
References
1.5
Technologies
1.6
Overview
2.
Overall Description
2.1
Product Perspective
2.2
Software Interface
2.3
Hardware Interface
2.4
Communication Interface
2.5
Product Function
2.6
User Characteristics
2.7
Constraints
2.8
Architecture Design
2.9
10
2.10
Class Diagram
13
2.11
Entity-Relation Diagram
16
2.11
Database design
19
2.12
22
6-23
3.
Specific Requirements
3.1
Use-Case Reports
23
3.2
Supplementary Requirements
49
Page 2
23-49
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.
If you are desirous to give 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 new traveler how would you structure
this information and also try and make some money by
changing people for at least 4 services you may offer.
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 the entire customer from one central
location.
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.
Page 3
1.3
Page 4
Page 5
1.4
References
1.5
Technologies
J2EE:(JSP, JAXP, Java Beans) Application
Architecture
JAVA: Application architecture.
WASCE: (Web sphere 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.
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.1
Page 6
Product Perspective
2.2
Software Interface
Development End:
Front End: Web Browser
Back End: WSAD (J2EE, Java Bean, HTML), DB2, OS,
Web Server.
2.3
Page 7
Hardware Interface
CLIENT SIDE
Internet explorer
6.0
Processor
RAM
Disk space
Pentium II at
500MHz
64 MB
1GB
Pentium III at
1GHz
512
MB
2 GB
Pentium III at
1GHz
512
MB
1 GB(excluding
data size)
SERVER SIDE
WEB SPHERE
APPLICATION
SERVER V5.0
DB2 V8.1
2.4
Communication Interface
Client on Internet will be using HTTP/HTTPS
protocol.
Client on Intranet will be using TCP/IP protocol.
2.5
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 are
maintained by the system.
Page 8
2.6
User Characteristics
Every user should be comfortable of working with
computer and net browsing.
2.7
Constraints
2.8
Page 9
Architecture Design
2.9
Page 10
Page 11
(A) 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: updating of the information on
system will be done.
(B) 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:
services will be done.
management
of
paid
Page 12
of
(E) Customer
Person/Company who is facilitated by the system.
Page 13
Access
information:
Customer
information on website for his usage.
will
access
2.10
Class Diagram
(A) Administrator
Page 14
Page 15
Page 16
(E) Report
Page 17
2.11
Entity-Relation Diagram
(A) Administrator
Page 18
(E) Report
2.12
Page 20
Database Design
(A) Customer
S.
No.
1.
Field Name
Customer ID
2.
Name
3.
User Name
4.
Password
5.
6.
Fathers
Name
Street
7.
City
8.
District
9.
State
10.
Contact No.
11.
E-Mail id
12.
D.O.B.
13.
Profession
Data
Type
Varchar(2
0)
Varchar(5
0)
Varchar(2
0)
Varchar(2
0)
Varchar(5
0)
Varchar(5
0)
Varchar(4
0)
Varchar(4
0)
Varchar(4
0)
BIGINT
Key
Description
Varchar(7
0)
Date
Varchar(3
0)
Profession
customer
of
the
(B) Manager
S.
No.
1.
Field Name
Manager ID
Page 21
Data
Type
Varchar(2
Key
Description
Primar
0)
2.
Name
3.
User Name
4.
Password
5.
Address
6.
Contact No.
7.
E-Mail ID
Varchar(2
0)
Varchar(2
0)
Varchar(2
0)
Varchar(5
0)
BIGINT
y,
manager
Foreign
Foreign Name of the manager
User
name
of
the
customer
Password
of
the
customer
Address of the manager
Contact
no.
of
the
manager
Mail id of the manager
Varchar(7
0)
(C) Employee
S.
No.
1.
Field Name
Employee ID
2.
Name
3.
User Name
4.
Password
5.
Address
6.
Contact No.
7.
E-Mail ID
8.
Specification
Page 22
Data
Type
Varchar(2
0)
Varchar(2
0)
Varchar(2
0)
Varchar(2
0)
Varchar(5
0)
BIGINT
Varchar(7
0)
Varchar(5
0)
Key
Description
(D) Account
S.
No.
1.
Field Name
Account No.
2.
Account ID
4.
Type
5.
Balance
6.
User name
7.
Password
Data
Type
Varchar(3
0)
Varchar(2
0)
Varchar(2
0)
Double
Varchar(5
0)
Varchar(4
0)
Key
Description
Account no of the user
(E) Palace
S.
No.
1.
Field Name
Palace ID
2.
Name
3.
City
4.
District
5.
State
6.
Type
Data
Type
Varchar(1
0)
Varchar(5
0)
Varchar(4
0)
Varchar(4
0)
Varchar(4
0)
Varchar(2
0)
Key
Primar
y
Description
Unique Id of the palace
Name of the palace
City of the palace
District of the palace
State of the palace
Type of the palace
(F) City
S.
Field Name
Page 23
Data
Key
Description
No.
1.
City ID
2.
Name
3.
Description
Type
Varchar(2
0)
Varchar(3
0)
Varchar(9
00)
(G) Service
S.
No.
1.
Field Name
Service ID
2.
Name
2.
Description
3.
Price
4.
5.
Duration
Facility
Data
Type
Varchar(2
0)
Varchar(1
00)
Varchar(5
00)
Integer
Key
Description
Unique id for the service
Name of the service
Description
of
the
service
Total cost about the
service
Duration of the service
Facility provide by the
service
Integer
Varchar(5
00)
(H) Agreement
S.
No.
1.
Field Name
SLA ID
2.
Customer ID
3.
Service ID
4.
Description
5.
Rule
Page 24
Data
Type
Varchar(2
0)
Varchar(2
0)
Varchar(2
0)
Varchar(5
00)
Varchar(5
Key
Description
Foreign Unique
User
id
of
agreement
Customer
id
with
agreement
Service id for type of
service
Description
of
the
agreement
Rule of the agreement
7.
Terms &
Conditions
Total amount
00)
Varchar(2
00)
BIGINT
8.
Issue Date
Date
9.
End Date
Date
Days
Integer
6.
10.
(I) Receipt
S.
No.
1.
Receipt No.
2.
Customer ID
3.
4.
5.
Receipt Date
Receipt Time
Service
Name
City Name
6.
7.
8.
9.
10.
Field Name
Service Start
Date
Service End
Date
Total Amount
Pay Amount
Page 25
Data
Type
Varchar(2
0)
Varchar(5
0)
Date
Time
Varchar(1
00)
Varchar(3
0)
Date
Date
BIGINT
BIGINT
Key
Description
Receipt No.
Customer id for give
receipt
Generate date of receipt
Generate receipt time
Name of service provide
Name of city
Start date of the service
agreement
End date of the service
agreement
Total amount of service
Pay amount for take
service
11.
Left Amount
BIGINT
(J) Report
S.
No.
1.
Field Name
Report No.
2.
3.
Date
Specification
4.
Service
Name
2.13
Data
Type
Integer
Key
Primar
y
Date
Varchar(20
0)
Varchar(10
0)
Description
Unique no of the report
Date of the report
Specification
of
the
reports
Name of the service of
which
report
is
generated
3. SPECIFIC REQUIREMENTS
3.1 Use-Case Reports
Objective
Smart City is a full-service communications
provider across the nation and one of the world's
largest communications providers to convention
centers and hospitality venues. Smart City is a full
Page 26
(B)
(C)
(D)
(E)
Account Manager
Help Manager
User
Support Manager
(A) 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: updating of the information on
system will be done.
Page 28
Page 29
Page 30
Page 31
Page 32
Page 33
Page 34
Page 35
Name of use-case:
details
Name of use-case:
details
Description: previously
details are entered
payment
transaction
Make changes
Save new details
Update customer account
Entry of this editing event has been logged
Select customer
Select service
Select receipt no.
Select receivables details
Give acknowledgment
Update customer account
Entry of this Acknowledgment event has been logged
Alternate flow of events:
If the receivables details are not there then system
reports an error and ask for recheck.
Page 40
Page 41
(D) User
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
Page 42
Page 43
Page 44
Select service
See the details
Give receivable information
Account updated
Page 47
Page 50
Page 51
Page 52
Page 53