Election Automation System

Software Requirements Specification
Version 1.3

DOCUMENT RELEASE NOTICE

Document Details: Name ElectionAutomationSystem_ SRS Revision Details Action taken (Add/Del/Change) Preceding Page No. New Page No. Revision Description Version No. 1.3 Description SRS document for Election Automation System

This document and any revised pages are subject to document control. Please keep them up-to-date using the release notices from the distributor of the document.

Approved by: Authorized by:

Date: Date: I

and for those who may be required to maintain it. Acronyms and Abbreviations Abbreviation/Acronym EAS Description Election Automation System II . The document will enable them to understand all aspects of the system in detail. It will enable the Election Automation System to know that TCS has captured all the requirements. This document lays down the software requirements for the application that have been captured through a detailed study of the business work flow and functions. Intended Audience This document is intended for use by the designers of the system.PREFACE Purpose of this Document This document describes the System Requirements Specifications of the Election Automation System.

............................................................11 Update Voter Details….............................5 1........................ FUNCTIONAL REQUIREMENTS:...........................................1 Background.................................................................................... 25 3.............................................................2 3...........1 2....................................10 2...................................................................... USER INTERFACE SPECIFICATIONS........... OTHER REQUIREMENTS..............................13 2..................8 1.1 3..............26 Main Menu.............26 4.......................................................5 2.................5 Hardware and Software Platform...........2 Scope......15 Remove Nominee …...........................17 View Voter Details….................................................11 2...................................6 Application Security....18 Add Booth ….........4 2...............................................2 Performance Requirements..........................................10 Add Voter …............................................................................................2 2....................................................6 2..........................................................................9 Cancel Nomination…......... INTRODUCTION...................................... Constraints and Overriding Priorities.......................................................................................................................................................9 2....................7 2............................................................................................................................................................................................................................................................................................................................26 Screen Layout for Voter.......................9 2.......................................................4 Enroll as Nominee …....................................................................................................19 Get Voter List …....................... ..................................Table of Contents 1................................................................ 14 Add Nominee …...................................................................................................................................21 Elect the nominee …...........................................................................................6 1.................................................................13 Remove Voter…................................................................................ Dependencies........................................12 2................................................26 Screen Layout for Administration.............................3 Key Assumptions....................................................................................8 2..................................23 Use Case Diagram …..........................................................3 2.......................................................................................................27 III ...............................................................................27 4.........26 Screen Layout for Nominee:.................................16 3........5 1................24 Conceptual Class Diagram….....20 Get Nominee List …........................................................................................................................................27 4.......3 3....................................................................................................................................................................................8 2...................................................................................................................................................................7 1...................4 User Classes and Characteristics..15 2.................................6 1................................................................................14 2................................................................................................................1 User Access Control and Security............ 16 View Nominee Details…....................................................22 Generate Voting Report......................................

we are preparing and managing the government elections of a constituency.1 Background This document outlines the software requirement specification for the Election Automation System. if any. it keeps track of voters. It also prevents redundant voting against a voter. Client Details: Election Automation System is the up gradation of existing obsolete Election process that requires an automated system to provide better services to public that is easy to manage for the Election Commission. •The document can be used as a basis for development of the System Test data. EMS configures the details for each voting booth in the city based on the nominations. If these are not taken care of at this stage. it may be difficult to incorporate the desired modifications to overcome the shortcomings at a later stage. •The document is a clear and unambiguous statement of functionality required from the system for the design and development team. 1. It is the outcome of the Analysis Phase during which discussions were held with the users. Introduction Here. nominees in a constituency and the respective voting details. Both the user and designer should go through the document carefully in order to ensure that: •All the user requirements which need to be supported by the system have been identified and detailed. Broad Requirements: •Generate complete voting results report. Project Details: Develop an application that allow the Super EMS to handle manipulations with Nominee details and Voter details and result of election in the concerned constituency. with the basic structure of the proposed system at this stage. This system will maintain the nominations and voting information for an election in a given constituency.1. Nominee is voter of the current constituency. A nominee can opt to cancel his nomination before the given date. Along with this. . as detailed in the contract. It is essential to identify the problems. The objective of this Analysis Phase was to: •Define the scope for the Election Automation System •Serve as the baseline for the design of the Election Automation System Any changes to requirements after acceptance of this document will be through appropriate Change Management procedure.

2. 5.1. . the entire voter list will be replaced with the new list provided.3 Key Assumptions. Out of Scope: Percentage of genuine voters registered with Election Commission. A voting booth may be allocated to any number of voters. If a nominee does not meet the minimum requirements decided for the candidature. A voter may or may not cast his/her vote. Every nominee has fulfilled all the requirements necessary to participate in election. 3. 7. 6. 4. Business Users: •EMS •Nominee •Voter Geography: National Target System: An application to shift whole Election process from the manual system to an automated system. Dependencies. any number of nominees can participate in Election. Every voter has attained the age of Eighteen years. In a constituency.2 Scope The Scope of the project is to develop an automated system for • Enroll as nominee • Cancel nomination • Add voter • Update voter details • Remove voter • View nominee details • View voter details • Cast vote • Generate voting report. Constraints and Overriding Priorities The successful execution of the assignment will depend on the following factors: Assumptions 1. While modifying Voter details. his/her candidature will be rejected. 1.

Remove Voter 4. Update Voter Details 3. Availability of System Software from the client for development. 2. Add Voter 2. Availability of installed hardware/System software for implementation. Nominee should be voter of the current constituency. Add Nominee 6. 2. Generate Voting Report Constituency:The functionality that the constituency can perform 1. Enroll As Nominee 2. Get Voter List 2. Remove Nominee 7. Nomination acceptance criteria is out of scope of the system. Cancel Nomination . View Nominee Details 8. 1. Constraints 1. View Voter Details 5. Get Nominee List Nominee:The functionality that the nominee can perform 1. Involvement of the end users in signing off this SRS document. 3.4 User Classes and Characteristics EMS:The functionality that the EMS can perform 1.Dependencies 1. Add Booth Booth:The functionality that the booth can perform 1.

.6 Application Security 1. View Nominee Details 2. DR. Voter and Nominee authentication has not been taken into consideration as it is assumed that it has been done in advance.5. Elect Nominee 1.JAVA for implementation 1.5 Hardware and Software Platform Hardware Platform: P3 1Ghz processor RAM 128MB Hard disk space 20GB Software Platform: Windows 2000 & above with JDK 1.Voter:The functionality that the voter can perform 1.

3.The nominee is added in the nominee list. Main Success Scenario: 1.2. 6. 2. .System prompts for confirmation of addition of nominee.System validates for uniqueness of nominee name. 4. Nominee Id is generated. 7. 2. Functional Requirements: The Functional Requirements are provided in the form of use cases that explain the important processes that are going to be implemented in the system. Success Guarantee: Nominee details given by the nominee is recorded.EMS confirms addition.1 Enroll as Nominee Use Case UC1: Enroll as Nominee for nomination Level : User goal Scope: Election Automation System Primary Actor: Nominee Stake Holders and Interests: EMS: Can add the nominee details Nominee:Wants the system to accurately store the nominee details Preconditions: Nominee should be eligible abide by the rules and regulations of government.System validates the nominee details. 8.EMS enters nominee details in to the system. 5.System generates a nominee id for the nominee.The nominee details are saved in the system.

the nominee should exist in the system with a nominee id to contest in the elections. Election System: Wants to automate the cancellation of the nomination of particular nominee. Nominee: Wants to cancel the nomination of the given nominee by removing that particular nominee details from the system. System displays an error message.EMS wants to alter the nominee details. . 7a.2 Cancel Nomination Use Case UC2: Cancel Nomination Level : User goal Scope: Election Automation System Primary Actor: Nominee Stakeholders and Interests: EMS: Can cancel the nomination. 5a. System displays an error message. 2. Success Guarantee: Nominee details given by the nominee are deleted from the list and the nomination is canceled. System fails to save the nominee details provided due to power outage.Extensions: 1a. Duplicate Nominee name . Invalid input data. 2a. Preconditions: Before cancellation. System displays an error message. EMS cancels addition process.

1b. then cancellation is done or else the cancellation is not possible. Extensions: 1a.Invalid input data.Main Success Scenario: 1.Canceling nomination after the last date. System displays an error message. System displays an error message. 2. System displays an error message. System checks for the last date for canceling the nomination. 3. System fails to remove the nominee details provided due to power outage. System prompts for confirmation of removal of nominee from the list. Election System: Wants to automate the addition of voters and the generation of voter Id.3 Add Voter Use Case UC3: Add Voter Level: User goal Scope: Election Automation System Primary Actor: EMS Stake Holders and Interests: EMS: Can add Voter details Voter:Wants the system to accurately add the voter details in to the voters list of the system. . 5a. System removes the nominee from the list. If the nominee wants to cancel before the last date. Cancellation is not possible. 2. EMS confirms removal. 4. Preconditions: Before adding the voter in to the voter list of the system. the voter should not exist previously in the system. EMS removes nominee details from the system. 5.

Success Guarantee: Voter details given by the voter are added successfully in to the voters list. 4. Main Success Scenario: 1. 2a. Extensions: 1a. Domain Model for UC3: . 7.The voter is added in the voter list.System prompts for confirmation of addition of voter.System generates a voter id for the voter.EMS confirms addition. System fails to save the voter details provided due to power outage. Invalid input data.System validates for uniqueness of voter name.EMS enters voter details in to the system. System displays an error message. 8. 6.The voter details are saved in the system. Duplicate voter name . 5. 2.System validates the voter details. System displays an error message. System displays an error message. 3. 7a.

System validates for uniqueness of voter name.Duplicate Voter name.4 Update Voter Details Use Case UC4: Update voter details Level: User goal Scope: Election Automation System Primary Actor: EMS Stakeholders and Interests: Voter:Wants the system to accurately update the voter details Election System: Wants to automate updation of voter details. 7a. . The voter details are saved in the system. EMS updates the voter details in to the system. Success Guarantee: Updated voter details are recorded in the system by the EMS. System displays an error message. 5. The voter details are updated. that particular voter must exist in the system. Voter details updated successfully message is displayed to the user. 6. Invalid input data. 3. System displays an error message.2. 3a. Main Success Scenario: 1. EMS confirms updates. Preconditions: Before modifying the voter details. System prompts for confirmation of updating the voter details. Extensions: 1a. System fails to update the voter details provided due to power outage. System displays an error message. 4. 7. 2. System validates the voter details.

5 Remove Voter Use Case UC5: Remove voter details Level : User goal Scope: Election Automation System Primary Actor: EMS Stakeholders and Interests: Voter:Wants the system to accurately remove the voter details from the voter list of the system. EMS removes voter details from the system.Invalid input data. System displays an error message. Extensions: 1a. 7a. EMS confirms removal. System fails to remove the voter details provided due to power outage. System removes the voter from the list. 4. 5. Removing voter from the voters list. System prompts for confirmation of removal of voter from the list. System displays an error message.2. Main Success Scenario: 1. System displays an error message. Success Guarantee: Voter details are removed from the system and the voter is not able to vote a nominee. If removal is not possible. the voter should previously exist in the system. 1b. . Election System: Wants to automate the removal of voter details of a particular voter. 3. Preconditions: Before removing.

7a. System displays an error message. 2.System validates the nominee details. 5. Nominee: Wants the system to accurately update the nominee details.6 Add Nominee Use Case UC6: Add Nominee Level:User Goal Scope: Election Automation System Primary Actor: EMS Stakeholders and Interests: EMS : Should add the nominee details in to the nominee list. Main Success Scenario: 1.System generates a nominee id for the nominee. 4. System fails to save the nominee details provided due to power outage. 2a. 7.The nominee details are saved in the system. Election System: Wants to automate addition of nominee details. Preconditions: None Success Guarantee: Nominee details are recorded in the system by the EMS. System displays an error message.EMS enters nominee details in to the system.System prompts for confirmation of addition of nominee.The nominee is added in the voter list.EMS confirms addition.2. Invalid input data.System validates for uniqueness of nominee name. Extensions: 1a. . 3. System displays an error message. 8. 6. Duplicate nominee name .

the nominee should previously exist in the system. Preconditions: Before removing.7 Remove Nominee: Use Case UC5: Remove nominee details Level : User goal Scope: Election Automation System Primary Actor: EMS Stakeholders and Interests: Nominee:Wants the system to accurately remove the nominee details from the nominee list of the system.Domain Model for UC6: 2. Main Success Scenario: . Success Guarantee: Nominee details are removed from the system and the voter is not able to vote a nominee. Election System: Wants to automate the removal of nominee details of a particular voter.

System fails to remove the nominee details provided due to power outage. System prompts for confirmation of removal of nominee from the list. Main Success Scenario: .Invalid input data. Removing voter from the nominee list. If removal is not possible.1. System displays an error message. EMS Stakeholders and Interests: Voter: Should be able to view the nominee details to elect them. Election System: System wants to automate the list of all the nominees in the constituency with their respective details so that the voters can view the nominee details. System displays an error message. 2. 2. EMS removes nominee details from the system. EMS confirms removal. System removes the nominee from the list.8 View Nominee Details Use Case UC8: View Nominee Details Level: User goal Scope: Election Automation System Primary Actor: Voter. Wants the system to make the voters view the nominee details accurately before the election get started EMS: Can view the nominee list. 1b. 4. Preconditions: None Success Guarantee: Nominee details are recorded in the system by the EMS. 3. 4a. System displays an error message. Extensions: 1a.

14 Preconditions: None Success Guarantee: Voter details are recorded in the system by the EMS. EMS maintains the list of all the voters of that constituency.9 View Voter Details Use Case UC9: View Voter details Level: User goal Scope: Election Automation System Primary Actor: EMS Stakeholders and Interests: Wants the system to make the EMS to know the voter details. 3. Election System: System wants to automate the list of all the voters in the constituency with their respective details. Extensions: 1a. Main Success Scenario: 1. EMS maintains the list of all the nominees of that constituency. 2.1. System displays an error message. .Voters should be able to view the details of all the nominees. EMS gives access to voters to view voters details. 2.EMS gives access to voters to view nominee details. 2.Voters should be able to view the details of all the voters 3. Invalid input data. 3a. System fails to display the nominee details provided due to power outage. System displays an error message.

2a.System prompts for confirmation of addition of booth.EMS enters booth details in to the system.The booth details are saved in the system.System validates for uniqueness of booth name. 2.10 Add Booth: Use Case UC10: Add Booth Level:User goal Scope: Election Automation System Primary Actor: Constituency Stakeholders and Interests: EMS : Should add the voting booth details. Extensions: 1a. 5. Election System: Wants to automate addition of voting booth details.4. System displays an error message. Preconditions: None Success Guarantee: Booth details are recorded in the system by the EMS. System displays an error message. 3. Extensions: . The voter view the voters details. System fails to display the nominee details provided due to power outage. 2.EMS confirms addition. Main Success Scenario: 1. Invalid input data. 6.System validates the booth details. 4.

Preconditions: None Success Guarantee: Voting booth is having its respective Voter details. System fails to save the booth details provided due to power outage. The Voting booth contains its respective voter list. Domain Model for UC10: 2. System displays an error message.11 Get Voter List Use Case UC11: Get Voter details Level: User goal Scope: Election Automation System Primary Actor: Voting Booth Stakeholders and Interests: Booth: Wants the system to make the EMS to know the voter details. Election System: System wants to automate the list of all the voters in the constituency with their respective details.1a. Extensions: . 6a. System displays an error message. Main Success Scenario: Booth maintains the list of all the voters of that constituency. Invalid input data.

Main Success Scenario: 1. 2. System displays an error message. Election System: System wants to automate the list of all the nominee in the constituency with their respective details.12 Get Nominee List Use Case UC12: Get Nominee details Level: User goal Scope: Election Automation System Primary Actor: Voting Booth Stakeholders and Interests: Booth: Wants the system to make the EMS to know the nominee details. Extensions: 1a. Invalid input data. System displays an error message. System displays an error message. System displays an error message.1a. 1b. Booth maintains the list of all the nominee of that constituency. 2.13 Cast Vote . Invalid input data. System fails to display the voter details provided due to power outage. 1a. Preconditions: None Success Guarantee: Voting booth is having the nominee details of all the nominees. The Voting booth contains its respective voter list. System fails to display the nominee details provided due to power outage.

his vote is invalid System displays an error message. If voter votes for more than one nominee. he cannot elect the nominee.A voter should not vote for more than one nominee. Extensions: 1a. Preconditions: To elect the nominee.Voter should do voting only once.Use Case UC13: Cast Vote Level: User goal Scope: Election Automation System Primary Actor: Voter Stake Holders and Interests: Voter: Has to elect the nominee EMS: Provides the nominee details. 5. 2. EMS gives access to voters to view nominee details. 6. voter should get registered in the voter list. Success Guarantee: Voter can vote for a single nominee.Before voting. System fails to display the nominee details provided due to power outage. Voter elected his nominee successfully. Main Success Scenario: 1. The voter view the nominee details. 3. voter can see the details of all the nominees.If the voters name is not present in the list. 2a. Voter can go to the nearest voting booth in that constituency to elect the nominee.14 Generate Voting Report . 2. his vote is invalid System displays an error message. If voter votes more than once. 4. 5a. System displays an error message.

2. EMS generates the result. System fails to generate the election results provided due to power outage.EMS gets the results from all the voting booths present in the constituency. 3. System prompts for confirmation of the election result. If results are not available from booths. 2.15 Use Case Diagram: . the nominee who got elected in the constituency election is released to the commission successfully. 2a. 4.Use Case UC14:Generating the election result Level: User goal Scope: Election Automation System Primary Actor: EMS Stake Holders and Interests: Wants the system to accurately generate the result of the election conducted in the constituency. System displays an error message. System displays an error message. 5. The generated results are saved in the system. Main Success Scenario: 1. Election System: Wants to automate the result of the election process. 6. EMS confirms the result. Preconditions: None Success Guarantee: Results are generated successfully and a Nominee got elected. The result. Extensions: 1a.

.

2.16. Conceptual Class Diagram: .

3. Generate result 7. Return to Main Menu Enter your choice : . Enroll as nominee 2. View Nominee details 2. Add Voter 2. 5. Return to Main Menu Enter your choice : Screen Layout for Nominee 1. EMS Nominee Voter Constituency Booth Exit Enter your choice : Screen Layout for EMS 1. Cancel Nomination 3. Remove voter 4.3. 6. Return to Main Menu Enter your choice : Screen Layout for Voter 1. 4. Modify voter details 3. Elect the nominee 3. 2. Remove Nominee 6. User Interface Specifications The following may be the possible output screens for the application Main Menu 1. Add Nominee 5.

The throughput of the application will be about 99%. User Access Control and Security Security provisions may be made at the following levels: Operating System Level Each user may be given separate log-in Id and password. Each user or group of users will have access to certain screens/functions of the system relevant to his area of operation. In case of an invalid combination of these two codes. They may be divided into three groups. . throughput etc. These users may not have any access to the Operating System commands outside of Application Menus Besides it will be possible to set or change the password interactively. Each user will have to log-on to the system using the correct user name and password. Performance Requirements Performance requirements specify the performance characteristics of the system like response time. The response time of the application will be 100 milliseconds.4. the system will display an error message and prevent further processing. Application User may have access to Application software only. Other Requirements The other requirements may include the user access control and security requirements and performance requirements.