Scribd
Upload
24 views8 pages

Sen Doc Final

The document describes requirements for an online voting system. It outlines system functions like voter registration and casting votes. It also covers non-functional requirements such as security, performance and safety.

Uploaded by

geet.more15
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
24 views8 pages

Sen Doc Final

The document describes requirements for an online voting system. It outlines system functions like voter registration and casting votes. It also covers non-functional requirements such as security, performance and safety.

Uploaded by

geet.more15
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 8

SOFTWARE ENGINEERING

TOPIC: ONLINE VOTING SYSTEM

1. SOFTWARE REQUIREMENT SPECIFICATION

1. Introduction
1.1 Purpose

Online Voting System is a system which enables all citizens to cast their
vote online. The purpose is to increase the voting percentage across
the country, as in the present system people have to visit the booth to
cast their vote and those people who live out of their home town are
not able to cast vote during the elections. So due to this the voting
percentage across the country is very less. Through this software those
people who live out of their home town will also be able to cast their
votes as this system is online.

1.2 Intended Audience and Reading Suggestions

The intended audience of this document is the potential end user. The
document may also serve as a reference guide to the developers of the
system.

1.3 Product Scope

The software produced will be an online voting system.


The main objective of this software is to increase the overall
voting %.
It will maintain the database of all the eligible citizens and
candidates.
It will manage all the account details of the voters such as citizen
name, date of birth, their constituency area, region, state, login id
and password of the voter from one central location.

1.4 References

1. IEEE Standards Description: 830-1998


2. Writing Effective Use Cases - Alistair Cockburn ( 1998 )
3. Software Engineering –Robert Pressman
4. Database System Concepts-North

2. Overall Description
2.1 Product Perspective

The software product is a standalone system and not apart of a larger


system. The system will be made up of two parts, one running visible
directly to the administrator on the server machine and the other visible
to the end users, in this case the voters, through web pages. The two
users of the system, namely the voters and the admin interact with the
system in different ways. The admin configures the whole system
according to its needs on the server where the system is running. The
voters cast their votes using the web interface provided. These votes are
accepted by the system on the server.

2.2 Product Functions

On the Admin side, the system can be used to create/update/delete the


election details (posts, candidates, electoral rolls etc ). The Admin should
be able to specify the different attributes it wants for posts/candidates of
a particular election instance and voters.
From the voters perspective, the system is used to help them cast their
votes and after the elections are over, allow them to view the results,
which are automatically posted on the same site after the election
duration is over.

2.3 User Classes and Characteristics

The users can be divided into two main classes:

– The Admin: They manage the entire Voting System Software and
Conduct the Elections. They act as the Election Authority.

– The Voters: The voters should have a basic knowledge of how to use a
web browser and navigate through web pages. The voters should be
aware that they have to keep their user-id and password confidential.
2.4 Operating Environment

The server should have Java installed on the machine, along with Java’s
packages. The election server runs on a http server, that is ”jsp”
enabled. The browsers through which the voters access the server
should have minimal support for cookies andencrypted transactions.

2.5 Design and Implementation Constraints

 GUI is only in English.


 This system is working for single server.
 Limited to HTTP/HTTPS.
 User should have basic knowledge of computer.

2.6 Assumptions and Dependencies

 The end user should have a basic knowledge of English and


computer usage.

 Administrator is created in the system already.

 The voting results will be managed and calculated by the


admin.

 Roles and tasks are predefined.

3. External Interface Requirements


3.1 User Interfaces

 Voters: The citizens of the country who are eligible for casting
vote.

Register for Online Voting System – Those who already have


voter id, they will register themselves for online voting system and
they will use their voter id as their user name and separate
password will be used for secure authentication.
Cast vote – The citizens will cast their votes for their favorite
candidates online through a secure system.

View own details – The voters will view their own details which
they filled up at the time of their registration.

3.2 Hardware Interfaces

There are no hardware interfaces to this software system. The only


interfaces are through a computer system.

3.3 Software Interfaces

The poll server runs on http server that is enabled to handle server
pages (eg. Apache Tomcat for support jsp). It uses a relational database
to keep track of the polls, which it connects through standard database
connectivity interfaces. In order to run the setup software, the
environment needs to have a JVM running on it

4. System Features

5. Other Nonfunctional Requirements


5.1 Performance Requirements

The software is expected to have reasonably short response time. It


should be able to log-in and feed the voter with new pages on request
with a response time of the order of a few seconds.

5.2 Safety Requirements

 In order to prevent data loss in case of system failure, the result of


votes that were polled till then have to be saved in the database,
for the system to resume the counting process on reboot.
 The EA should set up his system time appropriately for the
election process to start at the correct time.
 In case the EA detects any security lapse in the system, he should
able to shut down the server and close all connections
immediately while preserving the already polled votes.
 The system should be capable of gracefully recovering from earlier
crashes and continuing the voting process.

5.3 Security Requirements

 The system should provide basic security features like password


authentication and encrypted transactions.
 All the passwords generated and communicated to the users
should be stored in the server only in an encrypted form for login
management to prevent misuse.
 Serial attacks should be avoided by maintaining a minimum time
gap between successive invalid log-in attempts.
2. CLASS DIAGRAM

3. ENTITY RELATIONSHIP DIAGRAM


4. SEQUENCE DIAGRAM

A. SEQUENCE DIAGRAM FOR ADMIN:

B. SEQUENCE DIAGRAM FOR USER:


5. USE-CASE DIAGRAM

You might also like