Sample SRS

Online National Polling Version 2.
0
Software Requirements Specification January 15, 2010
Azure Sky
Azure Sky
Online National Polling

Software Requirements Specification
Version 2.0
Team Guide:
Lecturer: Mr. Mohammad Sharif
Team Members:
Deepak
Lakkireddy Rahul Reddy
Shanmugam B.
Debyani Sen
Department: Computer Science Engineering
Azure Sky/ M.V.J.C.E/ Bangalore/ Karnataka, 2010 Page 1

Online National Polling Version 2.0
Azure Sky
Revision History
Date Version Description Author
September 26, 2009 1.0 Synopsis Azure Sky
January 15, 2010 2.0 Synopsis Azure Sky

Azure Sky
Table of Contents
Description Page
1.0 Introduction ------------------------------------------------------- 5
1.1 Purpose ------------------------------------------------------- 5
1.2 Scope ------------------------------------------------------- 5
1.3 Definition, Acronyms, and Abbreviations ---------------- 7
1.4 References ------------------------------------------------------- 9
1.5 Technologies to be used --------------------------------------- 9
1.6 Overview ------------------------------------------------------- 10
2.0 Overall Description ----------------------------------------------- 11
2.1 Product Perspective --------------------------------------- 11
2.2 Software Interface ----------------------------------------------- 11
2.3 Hardware Interface --------------------------------------- 11
2.4 Product Function ----------------------------------------------- 12
2.5 User Characteristics --------------------------------------- 13
2.6 Constraints ------------------------------------------------------- 13
2.7 Architecture Design --------------------------------------- 14
2.8 Use Case Model Description -------------------------------- 15

Azure Sky
2.9 Class Diagram ----------------------------------------------- 16
2.10 Sequence Diagram s --------------------------------------- 17
2.11 Database Design ----------------------------------------------- 22
2.11.1 ER Diagram --------------------------------------- 22
2.11.2 Schema ----------------------------------------------- 23
2.12 Assumptions and Dependencies ------------------------ 24
3.0 Specific Requirements ----------------------------------------------- 25
3.1 Use Case Reports ----------------------------------------------- 25
3.1.1 ECO ------------------------------------------------------- 25
3.1.2 FO ------------------------------------------------------- 40
3.1.3 Candidate ----------------------------------------------- 43
3.1.4 Common General Public ------------------------------- 46
3.2 Supplementary Requirements ------------------------------- 50

Azure Sky
Software Requirements Specification
1.0 Introduction:
1.1 Purpose:
Online National Polling allows the common General Public to vote

online or through their current manual voting systems to vote for their
favorite Candidate. In this way, 100% participation in voting can be
achieved in our democracy, and hence creates a new era of computer
automation. Furthermore, it is one of the solutions sought in union
with the ongoing current manual voting system by preserving its ease
of service.
1.2 Scope: The Scope of the Online National Polling includes:
Creation of an Administrator account for the Election

Commissioner Officer (ECO), who in turn controls the election
voting system.
Assignment of the date for the day of the election for all states.
Creation of accounts for the Field Officers (FO) by the Election

Commissioner Officer, who manage the verification and
correctness of the photos and profiles of the common General
Public.
Creation of accounts for the Candidates by the Election

Commissioner Officer, who in turn campaign online and solve
the predicaments of their campaign through the use of Forums.

Azure Sky
Management of Candidate details, as well as their party

information, along with their party symbol.
Creation of accounts for the common General Public by

themselves, who in turn may visit their favorite Candidates
campaigning online.
Viewing and editing of all the details of the Field Officer,

Candidate, and common General Public in a single online
system.
Management of both the Online Voting System votes as well as

through the Electronic Voting Machine (EVMs) public votes.
Generation of results for an election as well as the number of

votes won by each Candidate.
Interactions of the common General Public with Candidates

through the use of Forums.
Generation of PDF based Reports based on the current Election.
Uploading of Videos by the Candidates to Campaign Online.

Hence, it provides an Online Video Support Web Services that
are similar to many services, such as YouTube™.
Support of Three Languages to give a more User-Friendly Look

and Feel.
Support of E-mail Facility to automate the Communication

more efficiently and effectively among different Users.

Azure Sky
1.3 Definitions, Acronyms, and Abbreviations:
ECO (Election Commissioner Officer): The administrator who

manages the whole Election Polling processes, such as assign date
of voting, assign Field Officers (FO), Candidates, etc.
EVM (Electronic Voting Machine): It is an old legacy system, in

which voting is done through manual votes.
FO (Field Officer): An officer assigned by the ECO to verify,

edit, and delete the profiles of the common General Public.
Candidate: A representative chosen by the common General

Public to represent them. During an election, the Candidates
compete against each other through campaigns to gain the peoples’
votes.
Common General Public: These are all the people eligible (19
years of more) enough to vote in an election for their favorite
Candidate.
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.
J2EE (Java 2 Enterprise Edition): It is a programming platform,

belonging to the Java platform, which is used for developing and
running distributed java applications.
WASCE (WebSphere Application Server Community

Edition): It is an application server that runs and supports the
J2EE and the web service applications.

Azure Sky
WSAD (WebSphere Studio Application Developer: It is a

designer toolkit which is designed to develop more complex
projects by providing a complete dynamic web service.
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.
RAD 7.0: IBM Rational Application Developer for WebSphere

Software (RAD) is an integrated development environment (IDE),
made by IBM's Rational Software division, for visually designing,
constructing, testing, and deploying Web services, portals, and
Java Enterprise Edition (JEE) applications.
Linux (Fedora 10): An Open Source Operating System that

provides much of the powerful features of UNIX with a Graphical
User Interface. Fedora 10 is the name of the Linux Operating
System.

Azure Sky
1.4 References:
IEEE SRS Format.
Problem Definition (provided by IBM).
Michael R. Blaha, James R.Rumbaugh, Object-Oriented

Modeling and Design with UML, Pearson Education, 2nd
Edition, 2005.
1.5 Technologies to be used:
J2EE: (Servlet, JSP, JAXP, Java Beans) 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: 3 Languages – Hindi, Kannada, and English

Azure Sky
1.6 Overview: The SRS will include two sections, namely:
Overall Description: This section will describe major

components of the system, interconnections, and external
interfaces.
Specific Requirements: This section will describe the

functions of actors, their roles in the system and the constraints
faced by the system.

Azure Sky
2.0 Overall Description:
2.1 Product Perspective:
The all clients will access the resources and uses the product
functionality through means of web pages (HTTP) which will
be displayed in web browser at the client machine.
Result and the report generated by the system will be in the

XML format which may be processed at client software.
Product using a DB2 database at the back end, WASCE server

at server machine.
2.2 Software Interface:
Front End Client: Web Browser (best view in Mozilla

Firefox), Operating System (Linux & Windows).
Web Server: WASCE, Operating System (Linux &

Windows).
Data Base Server: DB2 (IBM), Operating System (Linux &

Windows).
Back End: WSAD (J2EE, Java, Java Beans, Servlets, HTML).

Azure Sky
2.3 Hardware Interface:
Client Side:
ü Pentium II at 500 MHz Processor.
ü 64 MB of RAM.
ü 1 GB of Hard Disk.
Server Side:
ü WebSphere Application Server Community

Edition version 2.1.
ü IBM DB2 version 9.1.
ü Pentium IV at 2.6 GHz Processor.
ü 2GB of Hard Disk.
2.4 Product Functions: The Product has the following functions:
It manages the Candidate profiles and their party symbols.
It maintains the online votes given by the common General

Public.
It maintains the vote information from the EVMs.

Azure Sky
It evaluates the result of each Candidate and displays the entire

results of the Election.
It maintains all the profiles of ECO, FO, Candidates, and the

common General Public.
2.5 User Characteristics:
He/ she must have the minimum basic knowledge of the

computer, such as using the keyboard, using the mouse, accessing the
Internet, etc.
2.6 Constraints:
Verification of the common General Public by the FO is

done manually (because he/she has to check the physical
presence of the Voter).
Limited of HTTP/HTTPS
The states of India are already defined as per the

government of India and hence new states can not be
created.

Azure Sky
2.7 Architecture Design:

Azure Sky
2.8 Use Case Model Description:

Azure Sky
2.9 Class Diagram:

Azure Sky
2.10 Sequence Diagrams:
2.9.1 Set Election Date:

Azure Sky
2.9.2 Registration of Field Officer:

Azure Sky
2.9.3 Signup of General Public and their Profile Verification:

Azure Sky
2.9.4 Creation of Candidate:

Azure Sky
2.9.5 Vote For Candidate:

Azure Sky
2.10 Database Design:
2.10.1 Schema Diagram:

Azure Sky
2.10.2 E-R Diagram:

Azure Sky
2.11 Assumptions and Dependencies:
The End Users should know the fruitful language of English.
ECO is already created in the system.

Azure Sky
3. Specific Requirements:
3.1 Use Case Reports:
3.1.1: ECO (Election Commissioner Officer):
ECO is responsible for the assignment of the date of election,

creation of accounts for eligible Candidates, and creation of
accounts for Field Officers in all the respective constituencies.
Name of the Use Case: Set the election date.
Description: The ECO must assign the date of

election for each state by grouping
them accordingly.
Actors: Election Commissioner Officer.
Pre-condition: Election Commissioner Officer

already knows all the constraints of
setting the election dates state-wise.
Normal flow of events:
ü Display a page to set the election date if the

election date is not already set.
ü Give the dates on which the election is to be held

in each state.

Azure Sky
ü Select the states and group them to their respective

dates.
ü All the dates and the states, to which the dates are
assigned, are checked for validation.
ü Finally, the election dates for all the states are set.
Post-condition: The election dates are assigned for

each state.
Exception: All the states are not selected.

Azure Sky
Name of the Use Case: Create Field Officer (FO).
Description: The account of a Field Officer is

created by the Election Commissioner
Officer for each constituency of the
state.
Pre-condition: The Field Officer profile should

already be available to the ECO.
There can be only 1 Field Officer per
constituency.
ü The ECO will select the “Register New Field

Officer” option.
ü The ECO will enter all the details of the

corresponding Field Officer.
ü The ECO selects the constituency and the state to

which the corresponding Field Officer belongs to.
ü The details are verified. If errors are found, they

are displayed.
ü Finally, the Field Officer account is created.
Post-condition: The Field Officer ID is created as well

as his/ her account.
Exception: Two Field Officers can not be

selected for one state.

Azure Sky

Azure Sky
Name of the Use Case: View/ Edit/ Remove Field

Officer Profile.
Description: The Election Commissioner Officer

can view the detailed profiles of the
Field Officers. The Field Officers
details can also be searched by their
Field Officer ID or by selecting the
constituencies in a state.
Pre-condition: The Field Officer should already

exist.
ü The ECO will select the “Edit/ View Field Officer”

option.
ü Select the way to search the Field Officer details.

Either search him/ her by ID, or view all the Field
Officers.
ü View the displayed profile. Select either “Edit” or

“Delete” option to edit or delete a Field Officer,
respectively.
Post-condition: None.
Exception: The Field Officer account does not

exist.

Azure Sky

Azure Sky
Name of the Use Case: Create Candidate.
Description: The account of a Candidate and his

party is created by the Election
Commissioner Officer. Also, a new
party can be created for that
Candidate if required. Furthermore,
their new party symbol can also be
uploaded.
Pre-condition: The Candidate should have the

minimum eligibility defined by the
government of India to stand his place
in the election. Also, a Field Officer
must already be assigned to the
constituency to which the Candidate
belongs. Furthermore, his/her party
must already be created before by the
ECO.
ü The ECO will select the “Create Party” option to

create the Candidate’s Party first by uploading
their Party details and their Party Symbol.
ü The ECO will select the “Register New Candidate”

option.
ü The ECO will enter all the details of the

corresponding Candidate.
ü The ECO selects the constituency to which the

Candidate belongs as well as his/her Party.

Azure Sky
ü All the details are verified. If there are errors, they

are displayed, accordingly.
Post-condition: The Candidate ID is created. The

Candidate account is also created.
Exception: None.

Azure Sky
Name of the Use Case: View/ Edit/ Remove

Candidate Profile.
Description: The ECO can view the detailed

profiles of the Candidates. The
Candidate details can also be searched
by their Candidate ID or by selecting
their constituency.
Pre-condition: The Candidate should already exist.
ü The ECO will select the “Edit/ View Candidate”

option.
ü Select the way of search, namely: “search by ID”

or “View all the Candidates.”
ü Select the way to search the Candidate details.

Either search him/ her by ID, or view all the
Candidates.
ü View the displayed profile. Select either “Edit” or

“Delete” option to edit or delete a Candidate
profile, respectively.
Exception: The Candidate account does not exist.

Azure Sky

Azure Sky
Name of the Use Case: Open/ Close Registration

Line.
Description: The ECO can open/ close the

registration line for the Field Officer,
Candidate, and the common General
Public.
Pre-condition: This should be done before the date of

Election.
ü The ECO will select the “Open/ Close Registration

Line” option.
Post-condition: All the registration lines are closed.
Exception: None.

Azure Sky
Name of the Use Case: Open/ Close Voting

Line.
Description: The ECO can open/ close the voting

line for the common General Public.
Pre-condition: This should be done on the date of

Election.
ü The ECO will select the “Open/ Close Voting

Line” option.
Post-condition: All the voting lines are closed.
Exception: None.

Azure Sky
Name of the Use Case: Add vote from the

EVMs.
Description: The ECO can upload the XML file to

the database which is generated from
the manual EVMs. This result in
XML format will be combined with
the online votes.
Pre-condition: The online voting should be

completed.
ü The ECO will select the “Upload Results from

EVMs” option.

Azure Sky
ü Select the XML file generated form the EVMs.
Post-condition: The result will be displayed online

depending on the corresponding
candidates.
Exception: Improper XML file format.
Name of the Use Case: Announce Result.
Description: The ECO can upload the XML file to

the database which is generated from

Azure Sky
the manual EVMs. These results are

combined with the online votes to
generate the total, final results.
Pre-condition: The voting lines must be closed.
ü The ECO will select the “Announce Result”

option.
Post-condition: The result will be displayed online

depending on the corresponding
candidates.
Exception: Improper XML file format.

Azure Sky
3.1.2: FO (Field Officer):
The Field Officer views the details uploaded by the common

General Public. He/ she will verify the profile and the photos
provided by the people by visiting their house. He/she does this
by checking their presence in their residential address.
Name of the Use Case: Verify the common

General Public details.

Azure Sky
Description: The FO will certify the details

uploaded by the corresponding
General Public. If there is some
inaccuracy in the profile provided,
he/she will consult the General Public
to give the correct information.
Actors: Field Officer.
Pre-condition: The Field Officer should already have

the profiles of the common General
Public to check and verify.
ü The FO will select the “Verify General Public”

option.
ü The common General Public, who are not yet

verified, will be displayed.
ü The FO will verify their profile, if there is any

inaccuracy, by modifying and correcting the
profile.
Post-condition: The common General Public is

eligible for vote and a computer-
generated Voter-ID is assigned to
each common General Public.
Exception: Inaccuracy in common General Public

Details.

Azure Sky
Name of the Use Case: Manual Registration of

the common General Public.
Description: The FO can do the registration of the

common General Public who want to
vote manually through EVMs.
He/she also generates their Voter-ID
card.
Actors: Field Officer.
Pre-condition: None.
ü The FO will select the “Add General Public”

option.
Azure Sky
Post-condition: The computer-generated Voter-ID

should be printed.
Exception: None.
3.1.3 Candidate:
The Candidate and his party can campaign online through

Forums. The Candidate can also reply to the queries asked by
the common General Public.

Azure Sky
Name of the Use Case: Campaign Online.
Description: The Candidate can provide the link to

their campaign websites. He/ she can
write speeches to be displayed to the
General Public in Forums. He/ she
can also answer queries provided by
the common General Public through
the use of Forums.
Actors: Candidate.
Pre-condition: The Candidate should be registered by

the Election Commissioner Officer.
ü The Candidate will select the “Forum” option to

campaign online.
ü The Candidate will make topics on his

campaigning and he/ she can provide his/ her
speech to the common General Public by the use
of Forums.
ü The Candidate gives the links to their campaigning

websites.
Exception: The Candidate might give a broken

link.

Azure Sky

Azure Sky
3.1.4: Common General Public:
These are the people who will vote for their favorite Candidate
during the Election. They can vote through online or manually
through EVMs.
Name of the Use Case: Register for Voter-ID.
Description: The common General Public can

register online. They have to enter
their details and upload their photos
for verification by the Field Officer.
Actors: Common General Public.
Pre-condition: He/ she should be eligible (19 years)

to vote.
ü The common General Public will select the “Sign

Up” option on the website’s main page.
ü The common General Public will enter their details

and upload their photos.
Post-condition: To be verified by the Field Officer.
Exception: Inaccuracy in details provided.

Azure Sky

Azure Sky
Name of the Use Case: Vote to their favorite

Candidate.
Description: The common General Public can

enjoy their favorite Candidate
campaigns, and vote to their favorite
Candidates during the date of
election.
Actors: Common General Public.
Pre-condition: He/ she must already be verified by

the Field Officer.
ü The common General Public should select the

“Vote” option.
ü The common General Public will select the

Candidate from a common list of Candidates, who
are belonging to their own constituency and their
own parties.
Exception: None.

Azure Sky

Azure Sky
3.2 Supplementary Requirements:
Have hours of operation that are 24 x 7: The server system has

to be ON for a 24hrs day, because this election polling system has
to be available every time. System will remain inaccessible to
users at 2:00 to 4:00 am for backup and maintenance purpose.
Provide efficiency and the ability to scale the server: The

server has to provide a good performance during the peak hour,
because on the day of vote nearly 10 million people are going to
access the website.
Provide the session maintaining capability: The server should

provide functionality to maintain the session of an each client.
Provide huge data storage : Nearly 50 million people are going to
be register their details online, so database should have enough
disk space to store their details.

Sample SRS

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Sample SRS

Hochgeladen von

Copyright:

Verfügbare Formate

Online National Polling Version 2.

Online National Polling

Lecturer: Mr. Mohammad Sharif

Lakkireddy Rahul Reddy

Department: Computer Science Engineering

Azure Sky/ M.V.J.C.E/ Bangalore/ Karnataka, 2010 Page 1

September 26, 2009 1.0 Synopsis Azure Sky

January 15, 2010 2.0 Synopsis Azure Sky

Azure Sky/ M.V.J.C.E/ Bangalore/ Karnataka, 2010 Page 2

1.0 Introduction ------------------------------------------------------- 5

1.1 Purpose ------------------------------------------------------- 5

1.2 Scope ------------------------------------------------------- 5

1.3 Definition, Acronyms, and Abbreviations ---------------- 7

1.4 References ------------------------------------------------------- 9

1.5 Technologies to be used --------------------------------------- 9

1.6 Overview ------------------------------------------------------- 10

2.0 Overall Description ----------------------------------------------- 11

2.1 Product Perspective --------------------------------------- 11

2.2 Software Interface ----------------------------------------------- 11

2.3 Hardware Interface --------------------------------------- 11

2.4 Product Function ----------------------------------------------- 12

2.5 User Characteristics --------------------------------------- 13

2.6 Constraints ------------------------------------------------------- 13

2.7 Architecture Design --------------------------------------- 14

2.8 Use Case Model Description -------------------------------- 15

Azure Sky/ M.V.J.C.E/ Bangalore/ Karnataka, 2010 Page 3

2.9 Class Diagram ----------------------------------------------- 16

2.10 Sequence Diagram s --------------------------------------- 17

2.11 Database Design ----------------------------------------------- 22

2.11.1 ER Diagram --------------------------------------- 22

2.11.2 Schema ----------------------------------------------- 23

2.12 Assumptions and Dependencies ------------------------ 24

3.0 Specific Requirements ----------------------------------------------- 25

3.1 Use Case Reports ----------------------------------------------- 25

3.1.1 ECO ------------------------------------------------------- 25

3.1.3 Candidate ----------------------------------------------- 43

3.1.4 Common General Public ------------------------------- 46

3.2 Supplementary Requirements ------------------------------- 50

Azure Sky/ M.V.J.C.E/ Bangalore/ Karnataka, 2010 Page 4

Software Requirements Specification

Online National Polling allows the common General Public to vote

1.2 Scope: The Scope of the Online National Polling includes:

Creation of an Administrator account for the Election

Creation of accounts for the Field Officers (FO) by the Election

Creation of accounts for the Candidates by the Election

Azure Sky/ M.V.J.C.E/ Bangalore/ Karnataka, 2010 Page 5

Management of Candidate details, as well as their party

Creation of accounts for the common General Public by

Viewing and editing of all the details of the Field Officer,

Management of both the Online Voting System votes as well as

Generation of results for an election as well as the number of

Interactions of the common General Public with Candidates

Generation of PDF based Reports based on the current Election.

Uploading of Videos by the Candidates to Campaign Online.

Support of Three Languages to give a more User-Friendly Look

Support of E-mail Facility to automate the Communication

Azure Sky/ M.V.J.C.E/ Bangalore/ Karnataka, 2010 Page 6

1.3 Definitions, Acronyms, and Abbreviations:

ECO (Election Commissioner Officer): The administrator who

EVM (Electronic Voting Machine): It is an old legacy system, in

FO (Field Officer): An officer assigned by the ECO to verify,

Candidate: A representative chosen by the common General

HTML (Hyper Text Markup Language): It is used to create