8/4/2019 GSPMSRS-Ver 3 (2)

1/17

8/4/2019 GSPMSRS-Ver 3 (2)

2/17

Table of Contents

1. Introduction ................................................................................................................................. 3

1.1. Purpose: ................................................................................................................................................ 4

1.2. Scope: ..................................................................................................................................................... 4

1.3. Definitions:........................................................................................................................................... 4

1.4. References:........................................................................................................................................... 5

1.5. Overview: .............................................................................................................................................. 5

2. Overall Description .................................................................................................................... 6

2.1. Product Perspective: ........................................................................................................................ 6 2.1.1. System Interface: ........................................................................................................................................ 7

2.1.2. User Interface .............................................................................................................................................. 8

2.1.3. Hardware Interface ................................................................................................................................ 10

2.1.4. Software Interface: ................................................................................................................................. 10

2.1.5. Communication Interface: ................................................................................................................... 10

2.2 Product Functions: ........................................................................................................................... 10

2.3 User characteristics: ........................................................................................................................ 10

2.4 Constraints: ......................................................................................................................................... 11

2.5 Assumption and dependencies: .................................................................................................. 11

3. Specific Requirements ............................................................................................................ 12

3.1 External Interface ............................................................................................................................. 12

3.2 Functional Requirements: ............................................................................................................. 13

3.3. Design Constraints: ......................................................................................................................... 17

4. Future Extensions ..................................................................................................................... 17

4.1. Defect Logging: ................................................................................................................................. 17

8/4/2019 GSPMSRS-Ver 3 (2)

3/17

Versions Changes Made

2.0 Design Constraints Regional Language Support

3.0 Future Extensions

8/4/2019 GSPMSRS-Ver 3 (2)

4/17

1. Introduction

1.1. Purpose:

This software requirement specification document describes the functional and non-

functional requirements of the online voting system using face recognition. The intended

audience for the SRS includes the developers, testers and stakeholders.

1.2. Scope:

The voter turnout in 2009 Lok Sabha Elections in India was 59.7%. People are

reluctant to travel to polling booths and cast their vote because of lack of time, longer queues

in polling booths and the distance they need to travel. This system will take care of all these

issues and people can vote from their homes by just few clicks. If one has an Internet

connection along with webcam attached to his PC/Laptop then he will be able to cast his vote

online.

1.3. Definitions:

1.3.1. Unregistered Users:

They will not have username/password given by Election Commission of India. They

are not qualified to vote through online voting system. As they dont have valid

username or password, they cannot proceed to any other page from the login page.

1.3.2. Registered users:

The registered users will have the username/password provided by Election

commission of India.

1.3.3. Support Admin:

The Support Admin is the one who inserts and validates the physical form of records

of the voters with the database.

8/4/2019 GSPMSRS-Ver 3 (2)

5/17

5

1.3.4. Admin:

The Admin is the one who maintains and validates overall database operations. Theadmin also takes care of all the necessary safety checks for the database.

1.3.5. Super Admin:

The Super Admin is the one who monitors the overall operations of the entire voting

system. He also monitors the activities of Support admin and admin.

1.3.6. Constituency Election Officer:

The Election constituency Officer is the one who can view the voting results of

his/her constituency.

1.3.7. State Election Officer:

The State election officer is the one who can view the voting results of his/her

respective state.

1.3.8. Election Officer:

The Election officer is the one who can view overall national voting results.

1.4. References:

IEEE Recommended Practice for Software Requirements Specification Std. 830

1998

Managing Global Software Projects Gopalaswamy Ramesh

1.5. Overview:

Section 2 contains overall description of the software system. This section explains the

various interfaces, functionalities of the system and also the requirements of the users. It also

contains the functionality of the product, user characteristics, constraints, assumptions and

dependencies.

8/4/2019 GSPMSRS-Ver 3 (2)

6/17

6

Section 3 contains specific requirements based on Functionality. This section explains the

detailed system features and functional requirements and external interfaces.

2. Overall Description

2.1. Product Perspective:

The election department collects the data of people in the physical form. The physical form

of data collected is added into the database. Once a particular user is added into the databaseincluding the image of the person an username and password is automatically generated.

Username will be of 12 characters and will follow a specific pattern to identify the users

easily. The generated username and password will be sent to the voters. Once the voters

receive the username and password they can login into the system and check for their account

details. If they found any discrepancy or they need any clarification they can submit tickets to

the support admin. On the day of voting the users will pass two stages of validation. The first

stage is the authentication of username and password. Then the second stage of verification is

the face recognition. The image that is captured using the webcam of the voter is verified

with the image present in the database. As the comparison is one-to- one comparison it wont

take much of time. After both the stages a voter can cast his/her vote. The election officer can

view the results of the vote cast through online.

8/4/2019 GSPMSRS-Ver 3 (2)

7/17

7

2.1.1. System Interface:

OnlineVotingSystem

Voter

Support Admin

Admin

SuperAdmin

ConstituencyElectionOfficer

StateElectionOfficer

ElectionOfficer

8/4/2019 GSPMSRS-Ver 3 (2)

8/17

8

2.1.2. User Interface

Types of users:

1. Unregistered voters

2. Registered voters

3. Support Admins

4. Admins

5. Super Admins

6. Constituency Election Officer

7. State Election Officer

8. Chief Election Officer

1.1. Registered users:

The Registered users have following modules

i) View their profile page.

ii)

Submit/Support tickets to support admin {in case of anydiscrepancy in their profile such as constituency, name, etc}.

iii) Voting page during specific polling time allocated for the voters.

1.2. Support Admin:

Modules for admin are

i) Add a voter

ii) Add/Edit constituency.iii) Add/Edit candidate details

iv) Edit the voter details.

v) Respond to the support tickets received from the voters.

vi) Send/Receive messages with the Admin.

vii) Send/Receive messages with the Super Admin.

8/4/2019 GSPMSRS-Ver 3 (2)

9/17

9

1.3. Admin:

Modules for Admin includes

i) Send/Receive messages with the Support Admin.

ii) Send/Receive messages with the Super Admin.

1.4. Super Admin:

The Super Admin modules are

i) Send/Receive messages with Support Admin.

ii) Send/Receive messages with Admin.

iii) Send/Receive messages with Constituency Election Officer.

iv) Monitors the work done by Support Admin and Admin.

1.5. Constituency Election Officer:

The modules for the Election Officer are

i) Send/Receive messages with Super Admin.

ii) Send/Receive messages with state election officer.

iii) View the voting results for each constituency.

iv) Statistics of online voting system.

1.6. State Election Officer:

The modules for State Election Officer includes

i) Send/ Receive messages with Constituency Election Officer.

ii)

View his/her respective state results.iii) Send/Receive messages from Election officer.

iv) Statistics of online voting system.

1.7. Election Officer:

The modules for election officer includes

i) Send/Receive messages with State Election Officer.

8/4/2019 GSPMSRS-Ver 3 (2)

10/17

10

ii) View overall statistics of the online voting system.

iii) View overall results

2.1.3. Hardware Interface

Webcam attached to the PC/Laptop of voters with minimum 2.0 Megapixel.

2.1.4. Software Interface:

The web application should access the Matlab software for face recognition

and the application also should access the database.

2.1.5. Communication Interface:

i) Internet Protocol (IP) with Transmission Control Protocol (TCP)

ii) Hypertext Transfer Protocol (HTTP) for client-server model

2.2 Product Functions:

1. Voting in the polls through Internet.

2. Viewing results of votes cast through Internet

3. Adding/Updating the voter info into the database

4. Communication between different users of the system.

2.3 User characteristics:

Registered Voters:

1. Should know the basics of usage of Internet.

2. Should have proficiency in English

Support Admin:

1. Should know the basics of usage of Internet.

2. Should have proficiency in English.

http://wiki/Transmission_Control_Protocolhttp://wiki/Hypertext_Transfer_Protocolhttp://wiki/Hypertext_Transfer_Protocolhttp://wiki/Transmission_Control_Protocol

8/4/2019 GSPMSRS-Ver 3 (2)

11/17

11

3. Should be well versed in typing.

Super Admin:

1. Should know the basics of usage of Internet.

2. Should have proficiency in English.

3. Should have people management skills.

2.4 Constraints:

1. Need proper lightings in the users environment for facial recognition to

work.

2. Minimum Internet connection speed of 128 kbps is required for voting to

take place.

3. Users face should not have any major changes compared to the

photograph they submitted to the election department.

4. Large amount of bandwidth and database space is required.

5. Voters need to use any of the following browsers. Internet Explorer 6.0 or above

Mozilla Firefox 3.0 or above Safari 4.0 or above

2.5 Assumption and dependencies:

Since the voting system is going to be online, the minimum requirement for the online

system would be having Internet browsers. The assumption and dependencies would

be as follows.

i) Persons trying to vote online are having webcam attached to their PC/Laptop.

ii) Webcam is of minimum 2 Megapixel.

iii) The physical data collected by election department doesnt have a ny major errors.

iv) Users need to remember their username and password.

v) Technical people have to be present at all public polling system to help people at

the time of voting.

8/4/2019 GSPMSRS-Ver 3 (2)

12/17

12

vi) The server should be responsive at the time of voting.

vii) Users will be allowed to vote only during the mentioned time interval.

3. Specific Requirements

3.1 External Interface

Login Page:

Input:Username: 12 characters (alpha numeric)

Password: 6 characters

Process: Validating with data present in database.

Output: Profile page of the user (if both username and password are correct)

Same login page (if username or password is wrong)

Face Recognition:

Input: Face of the user captured through web cam.

Process: Verifying with image present in the database.

Output: Voting page if verification succeeds.

Voting:

Input: Selecting one candidate (by clicking one radio button)

Process: Saving the details in the database.

Output: Success page showing the confirmation of vote.

Results:

Input: Selecting the particular constituency or state through drop down box.

Process: Fetching the information from the database.

Output: Result page showing necessary info.

8/4/2019 GSPMSRS-Ver 3 (2)

13/17

13

3.2 Functional Requirements:

Use case 1: Login

Primary Actor: Registered Voters, Support Admin, Admin, Super Admin,Constituency Election Officer, State Election Officer, Election Officer

Scenario:

The Primary actors will login into the system using the username and

password they have.

The username and password are validated with the data in the database. If both the username and password are correct they will be logged in and

based on their user roles the target page will be differing.

If the entered username or password is wrong then the page will contain a

message asking them to enter their username and password.

Afte r 5 invalid login attempts the users account will be temporarily blocked

for 2 hours.

Use case 2: Add User details

Primary Actor: Support AdminScenario:

Election department will have all the records in the physical form and the job

of support admin is to add those user details into the database.

After clicking the add user button the page will ask for various user details

like Name, Age, Gender, Address, Ward, Constituency, District, State.

The username and password will be automatically generated after adding an

user. After adding the details the support admin can save all the details by clicking

the save button.

By clicking the confirm button the action will be committed.

Use case 3: Edit User details

Primary Actor: Support Admin

8/4/2019 GSPMSRS-Ver 3 (2)

14/17

14

Scenario:

If there is any discrepancy in the user data the support admin can edit those details.

After editing the details the support admin can save all the details by clicking thesave button.

By confirming the action will be committed.

Use case 4: Add/edit constituency:

Primary Actor: Support Admin

Scenario:

Support admin can add/edit a constituency in the database according to the needs

of the election department. The save button needs to be clicked.

After clicking the confirm button the action will be committed.

Use case 5: Add/edit candidates details:

Primary Actor: Support Admin

Scenario:

Support admin can add/edit the candidates along with party symbols who are

going to contest in the elections.

Support Admin needs to choose the necessary constituency and add those details.

The action has to be saved.

Once the confirm button is clicked the action will be performed.

Use case 6: Face recognition

Primary Actor: Registered Voters

Scenario:

On the day of voting a registered user after logging into the website after

username, password validation the user will come to face recognition page.

8/4/2019 GSPMSRS-Ver 3 (2)

15/17

15

Here the system automatically detects the webcam and asks user to click the

capture button.

The user can see the preview of the webcam and will click the capture button. The system will take 3 snaps of the face. The captured face is verified with the image present in the database for the

particular face.

Use case 7: Voting

Primary Actor: Registered Voters

Scenario:

On the day of voting a registered user after validation of two stages he/she will

be come to the voting page.

The list of candidates contesting in the users constituency with their party

name and symbol will be available.

The user can vote for any candidate by clicking the radio button of the

subsequent candidate.

After clicking the radio button the user will submit his vote and by clickingthe confirm button the users vote will be saved in the database.

Use case 8: Support tickets

Primary Actor: Registered User, Support Admin

Scenario:

If the registered voters find any discrepancy in their account details or they

have any clarification regarding the system they can submit support tickets

The registered user can create a ticket, which will have a unique number and

will be assigned to any one of the support admin.

Support admin after receiving the ticket has to respond to the registered voters

within 3 days.

Use case 9: Send/Receive Message

8/4/2019 GSPMSRS-Ver 3 (2)

16/17

16

Primary Actor: Support Admin, Super Admin, Admin, Constituency Election

Officer, State Election Officer, Election Officer

Scenario:

The above-mentioned primary actor can send/receive message. Support Admin can send/receive message with Super Admin and Admin. Admin can send/receive message with Support Admin and Super Admin. Super Admin can send/receive message with support admin, admin and

constituency election officer.

Constituency election officer can send/receive message with super admin and

state election officer.

State election officer can send/receive message with constituency election

officer and election officer.

Election officer can send/receive message with state election officer.

Use Case 10: Monitor Activities

Primary Actor: Super Admin

Scenario:

Super admin can monitor all the work done by support admin.

Use case 11: View Results:

Primary Actor: Constituency election officer, State election officer, Election Officer

Scenario:

Constituency election officer can view the results of constituency he/she

belongs to.

State election officer can view the results of the all the constituencies of the

state he/she belongs to.

Election officer can view the results all the constituencies in the country.

8/4/2019 GSPMSRS-Ver 3 (2)

17/17

17

3.3. Design Constraints:

The database should be of very large size to store voters information.

Enormous amount of Server space is needed during the polls.

4. Future Extensions

Support for the Regional languages. Implementation of Forgot Password option for the user.

4.1. Defect Logging:

Date : 27t h August 2010

Number of Persons Attended: 9

Name of the person attended: Arun, Gnana Ragu, Praveen V, ShivaBala, Shiva NT,

Karthik, Venugopal, Praveen P, Veena.

Discussion on: Online Voting System software requirement specification document

review and constraints in the project.

Clarifications Sought For:

1. Design constraints

2. Regional Language support