SWAMI KESHWANAND INSTITUTE OF TECHNOLOGY MANAGEMENT

AND GRAMOTHAN

STOP GLOBAL WARMING

SOFTWARE REQUIREMENT SPECIFICATION

TEAM

THE PROTAGONISTS

TEAM MEMBERS

VAIBHAV SHARMA

SORAV VERMA

SAKSHAM CHOUDHARY

SHOBHIT SHARMA

PROJECT GUIDE
INDEXES AND TABLES:

1 INTRODUCTION

1.1 Purpose
1.2 Scope
1.3 Abbreviations
1.4 References
1.5 Technologies
2 OVERALL DESCRIPTION
2.1 Project perspective
2.2 Software interface
2.3 Hardware interface
2.4 Communication interface
2.5 Project functions
2.6 User characteristics
2.7 Constraints
2.8 Use case model survey
2.9 Architecture diagram
2.10 Database design
2.11 Assumptions and dependencies
3 SPECIFIC REQUIREMENTS
3.1 Use case reports
3.2 Supplementary requirements
 1 INTRODUCTION
1.1 OBJECTIVE/VISION
This is a social website for encouraging people to abstain from various
pollution causatives. It works on the principles of health promotion and
strengthening the society. It not only makes the users aware of the
diseases caused but also how to prevent them. It encourage, conduct
and participate in investigations and research relating to problems of
water, land and air pollution and its prevention, control and abatement
thereof.

1.2 FUNCTIONAL REQUIREMENTS

i.To shed light on the various inspiring stories of those who have
contributed against pollution. Group members will have
opportunities to run various anti-pollution awareness programmers
in public places, colleges, etc. 
ii. It should spread awareness about the ways (direct, indirect etc)
in which a person can help to overcome pollution. 
iii. To evolve efficient methods of disposal of sewage and trade
effluent on land.
iv. To monitor the generation, transportation, treatment, storage
and disposal of hazardous wastes. 
v. To facilitate members to interact with people, conduct counseling
and clear doubts via discussion forums/chat/mail.
vi. Secure registration and profile management facilities for
registered members and government and non government
agencies. 
vii. A regular news-letter should be sent to registered users to
spread awareness.
viii. To collaborate with Central Pollution Control Board in organizing
the training of persons engaged or to be engaged in programmers
relating to prevention, control or abatement of water/air pollution
and to organize mass education programmed relating thereto.
ix. To identify and monitor the isolated storage of hazardous
chemicals.
x. Basic and advance admin facilities like add/update members,
back up/recovery of data, generating various reports, etc.
1.3 NON FUNCTIONAL REQUIREMENTS
i. Secure access of confidential data (user’s details). SSL can be used.
ii. 24 X 7 availability
iii. Better component design to get better performance at peak time
iv. Flexible service based architecture will be highly desirable for future
extension.

1.4 TECHNOLOGIES USED

i. UML
ii. JAVA
iii. XML
iv. e-FORMS
v. AJAX
vi. WEB 2.0
vii. WEB SERVICES
viii. SOA

1.5 TOOLS TO BE USED

i. ROSE/RSA/WEB SPHERE MODELLER
ii. ECLIPSE/RAD/LOTUS FORM DESIGNER/PORTLET FACTORY
iii. WEB SPHERE PORTAL/WAS/WAS CE/WPS
iv. DB2-EXPRESS ‘C’ OR DB2 UDB
v. TIVOLI CDP/TSM/TIVOLI DIRECTORY SERVER
vi. PREFERRED OS LINUX

1.6 USERS OF THE SYSTEM/ SCOPE

i. Anonymous users.
ii. Group members(registered users)
iii. Government or non government agencies, doctors( physicians and
counselors).
iv. Site administrators
1.7 OVERVIEW
SRS will include 2 sections:
i. Overall Description will describe major components of the system,
interconnection and external interfaces.
ii. Specific requirements will describe the functions of actors, their role
in the system and constraints.

OVERALL DESCRIPTION
1. The web pages(XHTML/JSP) are present to provide user interfaces on
customer client side. Communications between customer and server is
provided through HTTP/HTTPS protocols.
2. The client software is to provide the user interface on system user client
side and for this TCP/IP protocols is used.
3. On the server side web server is for EJB and database server is for storing
the information.

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).
Database server: DB2, operating system (any).
Development end: WSAD( J2EE, Java, Java beans, Servlets, HTML), DB2,
OS(Windows), web server.

HARDWARE INTERFACE

CLIENT SIDE

PROCESSOR RAM DISK SPACE

INTERNET PENTIUM II AT 64MB 1GB

EXPLORER 6.0 500 MHz

SERVER SIDE

WEB SPHERE PENTIUM III AT 1 512 MB 2 GB

APPLICATION GHz
SERVER V5.0

DB2V8.1 PENTIUM III AT 1 512 MB 1GB( EXCLUDING

GHz DATA SIZE)
 COMMUNICATION INTERFACE
i. Client on internet will be using HTTP/HTTPS protocol.
ii. Client on intranet will be using TCP/IP protocol.

USER CHARACTERISTICS
It is required that each user is comfortable with the concerned
operating system and has knowledge of English too.

CONSTRAINTS:
i. GUI is only in English
ii. This system is working for a single server
iii. Limited to HTTP/HTTPS

USE CASE ANALYSIS

Read
News

Use some resources

Anonymous user

Membership request
Member Change
Account

Login /
Logout
Terminate
Account

Administrator or

Use resources

Account
Reactivate
Feedback & Manage members
Account
Contact

1. Anonymous User:
i. Read: He can read the information available and can access all the textual resources
available on the website
ii. Use Resources: He can download the matter available on the website and use them
with the help of tools locally available on the client machine.
iii. Membership Request: He can send the membership request to the administrator
and can get reports.

2. Member:
i. Login: A member can login or log out of his personal account using his
unique id and password.
ii. Change: He can change the personal information provided to the website.
iii. Terminate: He can terminate his membership anytime. A notification will be
sent to the administrator on account of that.
iv. Use resources: he can further use the resources with more authority and
rights.
v. Feedback: He can send the feedback to the administrator regarding any
experience or difficulty he has faces in accessing the resources over the
website.
vi. View own details: Any member can view his/her own details after logging in.
 vii. View group homepage/information: A member can view the group home
page and check for all the updates available there.

3. Administrator :
i. Account: The administrator has the highest authority amongst all the actors
that exist. He gets the notifications regarding any new activity that happens
over the website.
ii. Manage members: Administrator has the rights to approve or disapprove
any membership request. He can keep a closed watch over all the member’s
activities.
iii. Administrator login: he can personally login and approve of the changes that
are pending his approval.
iv. Manage groups: He can manage groups also, besides managing the
individual accounts. He can control the matter that is being posted there.
v. View logs: He can view the complete log information of the people who
have accessed the website in certain duration of time. He can build other
statistics based on the requirements.
vi. View all details: He can view all details about individual members, their
email ids, addresses etc.

4. Government/Non Government Organizations:

i. Account: They can maintain their individual accounts and can control
activities over their corresponding groups.
ii. Manage members: they can communicate with the administrators
regarding the controlling of individual members over the group and
websites.
iii. Counseling: They can spread awareness amongst individuals by
communicating with them individually or collectively.
DATABASE DESIGN
SPECIFIC REQUIREMENTS:
USE CASE DIAGRAMS:
USE CASE-2
USE CASE-3
USE CASE-4
USE CASE-5
USE CASE-6
USE CASE-7
USE CASE-8
USE CASE-9
USE CASE-10
USE CASE-11
USE CASE-12
SUPPLEMENTARY REQUIREMENTS:
1. 24 X 7 X 365 AVAILABLITY: Because system can be an automated
process, it can stay open for 24 hours a day. System is required to
be available 24 X 7, so UPS support must be on the server site for
at least 8 hours in case of any power failure.
2. Make the existing website more dynamic in nature: Many early
web implementations consisted of static html pages. This
becomes very difficult to manage if the number of pages becomes
too large. An effective system should be largely dynamic taking
advantage of technology that automates this process rather than
relying on manual processes.
3. Provide good performance and ability to scale the server: The
Web application server should provide good performance and
ability to manage performance with techniques, such as support
for caching, clustering and load balancing.
4. Providing session management capability: Web application
developers should not valuable time worrying about how to
maintain sessions within the application. The Web application
Server should provide these services.