RLPV

SMART CITY
Software Requirements Specification Version1.1

(Lect. CSE Dept.) Lokesh Patidar Vinod Panwar Rahul Sharma

Team Members:
Prinesh Farkya

Mr. Roopesh Kumar

Team Guide:

Mandsaur Institute of Technology, Mandsaur (Madhya Pradesh)

College Name:

Smart City Smart City Team Name: RLPV

Date 31/12/2010

Version 1.0

Revision History
Synopsis

Version: 1.0 Date: 31/12/2010

Description

Author RLPV

CreativeMITians MIT Mandsaur 2009

Smart City Smart City Team Name: RLPV

Version: 1.0 Date: 31/12/2010

Table of Contents
1. Introduction 1.1 Purpose 1.2 Scope 1.3 Definitions, Acronyms and Abbreviations 1.4 References 1.5 Technologies 1.6 Overview 2. Overall Description 2.01 Product Perspective 2.02 Software Interface 2.03 Hardware Interface 2.04 Communication Interface 2.05 User Characteristics 2.06 Constraints 2.07 Use-Case Model Survey 2.08 Architecture Diagram 2.09 E-R Diagram 2.10 Database Design 2.11 Assumptions and Dependencies 3. Specific Requirements 3.01 Use-Case Reports 3.02 Supplementary Requirements

CreativeMITians MIT Mandsaur 2009

Software Requirements Specification 1. Introduction 1.1 Purpose:

The purpose of this project is to develop an Smart city environment that provides person to access any information about the city via the internet. Smart City will continue to evolve as the nations leading provider of event technology services, meeting the ever changing needs of our customers. Through our strategic partnerships with the worlds most innovative technology companies, Smart City will test and implement new products and services for the technology leaders of today and tomorrow. For the convention industry, Smart City will keep providing the golden standard of technology providers. Each and every convention center, hotel and event facility that offers Smart City services will be providing their customers the latest and greatest technology over the industrys most reliable networks with one of the best trained, most versatile workforces in the country.

1.2 Scope:
Basic Features: All information about the city, online. Easy access for user who want the any news of city for business purpose. The tourist will visit city online and find the tourist plase in the city easily. Validate the registration of voters as well as candidates. The business man have facility to advertise our product online. Candidates can run their election campaign via forum or chat rooms. Maintain all the details of user whos subscribe the sms alerts in our mobile. Alert the citizen or user of any government notice or any other news on the date by sending sms. SMS based inquiry for real-time services.

Optional Features: Secure Socket Layer (SSL) connectivity for secure access of confidential data.

1.3 Definitions, Acronyms and Abbreviations:

User: A User is a aurthorised person who can get th sevices of the smart city through sms on mobile by paid some money. Businessman: A businessman is a aurthorised person who can chnge our product information and database any time. HTML: Hypertext Markup Language is a markup language used to design static web pages. JavaScript: Client side script language for interactive designing of web pages. JDBC: Java Database Connectivity. SSL: Secure Socket Layer. XML: Extensible Markup Language is a widely used system for defining data formats. XML provides a very rich system to define complex documents and data structures. AJAX: It is an acronym for Asynchronous JavaScript and XML. It's a method to utilize the abilities of JavaScript, the Document Object Model, and XML to create interactivity on the web. EJB: Enterprise Java Beans. It is architecture for the development and deployment of transactional, distributed object applications-based, server side software components. J2EE: Java 2 Enterprise Edition is a programming platform part of the Java Platformfor developing and running distributed multitier architecture Java applications, based largely on modular software components running on an application server. DB2: DB2 Database is the database management system that delivers a flexible and cost-effective database platform to build robust on
5

RLPV MIT Mandsaur 2010

demand business applications. It also uses pureXML technology to store data. WAS: WebSphere Application Server is an application server that runs business applications and supports the J2EE and web services standards. RSA: Rational Software Architect is a designer toolkit which is designed to develop more complex project by providing fully dynamic services. RAD: Rational Application Developer is a developer tool which is designed to develop multitier application using Java technologies. HTTP: Hypertext Transfer Protocol is a transaction oriented client/server protocol between web browser & a Web Server. HTTPS: Secure Hypertext Transfer Protocol is a HTTP over SSL (secure socket layer). TCP/IP: Transmission Control Protocol/Internet Protocol, the suite of communication protocols used to connect hosts on the Internet. CDMA: Code Division Multiple Access - a generic term for a type of digital mobile telephony technology which supports a number of mobile connections. GSM: Stands for Global System for Mobiles and is the international standard for wireless technology. GSM allows users to utilize one phone and one number in many countries throughout the world.

1.4 References:
IEEE SRS Format. Beginning Database Design - Gavin Powell (Wrox Publisher). Mastering UML with Rational Rose - Wendy Boggs, Michael Boggs. jQuery Cookbook - John Resig. Problem Definition (Provided by IBM). E-Books (Provided by IBM).

RLPV MIT Mandsaur 2010

1.5 Technologies:
UML. J ava J 2E E XML Ajax Web 2.0 (XHTML, CSS, JavaScript ) jQuery (Cross Browser JavaScript Library) DB2 pureXML Google Data Visualization API

1.6 Overview:
Overall Description: It will describe major components of the system, interconnection and external interfaces. Specific Requirements: It will describe the functions of actors, their role in the system and constraints.

RLPV MIT Mandsaur 2010

2. Overall Description
Describe the general factors that affect the product and its requirements.

2.1 Product Perspective:

HTTP/HTTPS

HTML Client (User or businessman)

Mobile Client (User) GSM or CDMA Phone

WebSphere Application Server & SMS Server

IBM DB2

Client Side

SMS

Application Server

Database Server

The web pages (XHTML/JSP) are provides the user interface to the User/businessman/visitor in a web browser. Communication between client and server is provided through HTTP/HTTPS protocols. The Mobile Client is a GSM or CDMA phone used to send and receive SMS for new news of smart city on the mobile phone. This communication is provided using AT commands. At the server side web server is for EJB, Servlets, JavaBeans, and database server is for storing the information.

RLPV MIT Mandsaur 2010

2.2 Software Interface:

Client on Internet Client on Intranet : Web Browser, Windows Operating System. : Client Software, Web Browser, Windows Operating System. : Any mobile phone having Send and Receive SMS functionality. : Web Sphere Application Server, Windows Operating System. : DB2 : RAD (J2EE, Java, Java Bean, Servlets, HTML), DB2, Operating System (Windows), Web Server. \

Client on Mobile

Web Server

Data Base Server Development End

2.3 Hardware Interface:

Client Side Software Internet Explorer 7 .0 Processor Intel Pentium IV At 1 GHz Intel Pentium IV At 2.6 GHz Intel Pentium IV At 2.6 GHz RAM 512 M B 1 GB 1 GB Disk Space 2 GB 2 GB

Server Side

WebSphere Application Server 7 .0 DB2 V9.7

2 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. Client on Mobile phone will be using AT Commands and SMS protocol.

RLPV MIT Mandsaur 2010

2.05 User Characteristics:

Every user should be comfortable of working with computer and net browsing and mobile phone. He must have basic knowledge of English too.

2.06 Constraints:
Graphical User Interface (GUI) is only in English. Login name and password is used for identification of user of the system and
there is no facility for visitors. There is no maintainability of back up so availability will get affected. Only Indian citizen can cast their vote to the electoral candidates. Election Commission Officer would insure the integrity of the system because he will be admin of the system. Limited to HTTP/HTTPS.

RLPV MIT Mandsaur 2010

10

2.07 Use - Case Model Survey:

Visitor User

View/Update_User_Profile

Active/deactive_sms_service View_any_news_of_city

Visit_the_website

Find the businessman Go_for_registration Visit_The_website View_News

Business_Man

View/Update profile

Change_our_Product_details

Find_the_user

Sale_our_product

2.08 Architecture Diagram:

Application Layer
Login_UI Registration_UI Business_UI

Business Layer
Login Registration

Database Layer
User

Receipt_id Email_UI

Receipt

Business

Registration Description

Report_UI SMS_UI News

Email

Description Mail

Report

SMS News type

SMS_OUTBOUND Description

SMS_INBOUND

Report

2.09 Database Design: Entity Relationship Model

Find/view
Local_address Parmanent_address Busineemen _id password Address First_name

User_id

User_password User_password

Receipt _id

Receipt date

Farm_name

Business_Man

Name Last_name

Paid User

Paid

Receipt

Contact_number Business _description

Receipt amount Take User_id Service_id

Mobile_number

Office_number

Service_id

Service name

Services

Provide

Service
News date News_type

Status

Begining_date

Salary

News

Service_amt

News_description

News_Image

Database Schema:User 1.User_id 2.User_password 3.User_Profile

Receipt 1.Receipt_id 2.Date 3.Amount 4.User_id

Service 1.Service_id 2.Service_name 3.Service_amount 4.decription

Services 1.User_id 2.Services_id 3.Begining_date 4.Status

News 1.Date_code 2.Type 3.News_image 4.Gvt_.Notice 5.Description

Business_man 1.Businessmen_ID 2.Farm_Name 3.Owned_by 4.Type 5.Description 6.Businessmen_password 7.Profile

2.10 Assumptions and Dependencies:

The end user should have a basic knowledge of English language. The end user should have a basic knowledge of computer usage and internet. The User and Business man should be able to scan and upload the required document and photos while applying for registration on the website.

RLPV MIT Mandsaur 2010

15

3. Specific Requirements
3.1) Paid_User :- The paid user are use the services of the website which is provide by subscribing the sms services.

Subscribe/Unsub scribe service

Use Services

View Profile

See any news about city

RLPV MIT Mandsaur 2010

16

Business Man:

Find the user

View Profile

Update product desc.

RLPV MIT Mandsaur 2010

17

Name of use case: View Business_man Description: View the list of Business men of all the constituencies of a particular city. Normal flow of events: Name of city will be selected. Query will be submitted. Result will be displayed (If one of the city will be selected then list of all the business men will be displayed with other details.) Alternate flow of events: None Post Condition: None

RLPV MIT Mandsaur 2010

18

Name of use case: Add Business men Description: To add new Business men to a city constituency. Normal flow of events: New login name, password and other details will be entered. Details will be saved. Post Condition: A login id is generated with its details.

RLPV MIT Mandsaur 2010

19

Name of use case: Update details of business men & their products. Description: To add update details of business men. Normal flow of events: Select the business men. Edit the profile and other details. Details will be saved. Alternate flow of events: A message appears if any error occurred. The administrator has to fill the required details again. Post Condition: Business men profile will be updated.

Businessmen login Invalid Valid Edit profile & other detail

Detail will be saved

End

RLPV MIT Mandsaur 2010

20

Name of use case: - Visitor Description: - To show Visitor function. Normal flow of events: -Visitor can visit the website and go for registration in website.

Visit Site

Visitor

Go for Registration

RLPV MIT Mandsaur 2010

21

Assumptions and Dependencies:

Name of use case: Login. Description: User login in account. Preconditions: User must be entering valid login ID and password. Normal flow of events: User enters Login ID and Password. If login ID and password is correct user successfully login in. Alternate flow of events: If login ID and password is incorrect, reenter ID and password. Post Condition: None.

RLPV MIT Mandsaur 2010

22

Supplementary Requirements
24 x 7 Availability - If the base is now the entire world, staying open 24 hours a day becomes critical. Because system can be an automated Process, so it can stay open for 24 hours a day. 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. Dynamic Website - 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. Integration with 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.

RLPV MIT Mandsaur 2010

23