Electronic Voting System

  • View
    4.887

  • Download
    3

Embed Size (px)

Text of Electronic Voting System

1

1. PROBLEM STATEMENTAn electronic voting system via the Internet must fulfill the following five basic requirements: Only people eligible to vote should be able to vote. It should be possible to use ones vote only once. Ballots should be absolutely secret. It should not be possible for a vote cast to be changed by anyone else. The system should ensure correct tallying of votes at all levels (voting district, constituency and area). Other circumstances that may need to be taken into account in such a system are safeguards for the voters personal integrity and means of preventing the sale of votes. Authentication: At present, the election database contains the national civic registration number of everyone who is included in the electoral register. In an Internet voting system, the electoral register needs supplement with the voters personal password or code, to permit reliable identification. Only one vote: The system has information on all those who are eligible to vote, and when they do so their votes are just as in the present-day manual procedure checked against the electionic electoral register. Ballot secrecy: The system must not be technically feasible for any one to access the Ballot information and should transmit it to the counting system. Trustworthiness and legitimacy: The system should be perceived as trustworthy and should impart legitimacy to the election results, imposes special requirements in terms of permitting a revision of the system to be carried out where necessary.

2

AnalysisUse case view2. IDENTIFICATION OF ACTORSActors represent system users. They help delimit the system and give a clear picture of what the system should do. It is important to note that an actor interacts with, but has no control over the use cases.

An actor is someone or something that:1. Interacts with or uses the system 2. Provides input to & receive information from the system 3. Is external to the system and has no control over the use cases

Graphical DepictionAn actor is a stereotype of a class and is depicted as a "stickman" on a use-case diagram.

ACTOR

The following question should be answered to identify actors:1. Who is interested in a certain requirement? 2. Where in the organization the system is used? 3. Who will benefit from the use of the system? 4. Who will supply the system with the information, use this information and remove this information? 5. Who will support and maintain the system? 6. Does the system use the external resource? 7. Does one person play several different roles? 8. Do several people play same role? 9. Does the system interact with the legacy system?

3

Actors identified are:1. Voter: A member of the organization who participates in the election by casting his/her vote.

voter(from Actors)

2. Candidate: A member of the organization who participates in election by contesting in it.

Candidate(from Actors)

3. Administrator: The person who takes care of conducting the elections by declaring the election details and declaring the results.

Administrator(from Actors)

4. Election Database: External resource used by the system for voter Identification and profile manipulation operation.

Election Database (from Actors)

5. Election Commission: System that maintains the election database and get benefit form the e-voting process.

4

Election Commission (from Actors)

3. IDENTIFICATION OF USECASES AND SUB USE CASESIn its simplest form a use case can be described as a specific way of using the system from a users perspective. A more detailed description might characterize a use case as: A pattern of behavior the system exhibits A sequence of related transactions performed by an actor and the system Delivering something of value to the actor.

Use case provides a mean to: 1. Capture system requirements 2. Communicate with the end users and domain experts 3. Test the system Use cases are the best discovered by examining the actors and defining what the actor will be able to do with the system. Since all needs of a system typically cannot be covered in one use case, it is usual to have a collection of use cases. Together this use case collection specifies all ways of using the system.

UML notation for the use case:1. An ellipse containing the name of the use case inside it. Error: Reference source not found Voting

2. An ellipse containing the name of the use case below it

5

voting(from voti ng)

The following questions are to be answered to identify the use cases:1. What are the tasks of each actor? 2. Will any actor create, store, change, remove, or read information in the system? 3. What use cases will store, change, remove or read this information? 4. Will any actor need to inform the system about sudden external changes? 5. Does any actor need to be perform about certain occurrences in the system? 6. What use cases will support and maintain the system? 7. Can all functional requirements be performed by the use cases?

Use cases identified are:1. Authentication System: It verifies the voters authorization based on the voterID and password. 2. View profile: It allows the Authorized voter to see the candidate/his profile and to get know about this vote that is polled for selected candidate with a confirmation receipt to voter. 3. Voting System: It will process the voters ballot. 4. Profile Manipulation: It will process the profile of voters and the candidates that includes the certain, modification and deletion process. 5. Ballot Secrecy: It makes the ballot information secured and passes the encrypted secured ballot information to the results use case. 6. Results: Performs the counting of ballots polled for each candidate and announce the Election results to the Election commission.

6 7. Database Manipulation: Performs creation and manipulation of the database.

7

4. FLOW OF EVENTSA flow of events is a sequence of transactions (or events) performed by the system. They atypically contain very detailed information, written in terms of what the system should do, not how the system accomplishes the task. Flow of events are created as separate files or documents in your favorite text editor and then attached or linked to a use case using the files tab of a model element.

Flow of events should include: When and how the use case starts and ends Use case / actor interactions Data needed by the use case Normal sequence of events for the use case Alternate or exceptional flows

Flow of events in E-Voting system: 1. Use Case Specification for the Authentication system use case: 1.0 Use Case NameAuthentication System

1.1 Brief DescriptionThe voter starts this use case. It provides the capability for the system to perform on-line identification of the voters.

2.0 Flow of Events 2.1 Basic FlowThis Use Case begins when the voter logs into the identification system and enters his/her password. The system verifies that the voter ID and the password is valid (if they are invalid alternate flow 2.2.1 is executed). To perform this validation, this use case makes use of the election database. After the Successful validation it will pass a report to the Administrator.

8

2.2 Alternate Flows 2.2.1 Invalid Voter IDAn invalid Voter ID is entered. The user can re-enter his/her voter ID or terminate the use case.

2.2.2 Invalid PasswordAn invalid password is entered. The user can re-enter his/her Password or terminate the use case.

3.0 Special RequirementsTo perform voter identification this use case requires the external Election Database.

4.0 PreconditionsThere are no preconditions.

5.0 Post ConditionsThere are no Post Conditions.

6.0 Extension PointsThere are no extension points.

2. Use Case Specification for the View Profile use case: 1.0 Use Case NameView profile

1.1 Brief DescriptionThis use case is started by the Authentication system use case and access by the voter. It allows voter to see the candidate profile and also to get know about his vote is polled/counted for selected candidate or not with some conformation receipt to voter.

2.0 Flow of Events 2.1 Basic FlowThis Use Case begins after the voter was authenticated and shows the profile of him/her self or the candidate.

9

2.2 Alternate Flows 2.2.1 Wrong profile selection:When the voter selected wrong profile, the use case allows selecting correct profile again.

3.0 Special RequirementsThere are no special requirements.

4.0 Preconditions 4.1. Authentication:The voter must be identified as a valid voter before entering into this use case.

4.2. Correct profile/update profile:The profile must be the updated one before it is going to access.

5.0 Post ConditionsThere are no Post Conditions.

6.0 Extension PointsThere are no extension points.

3. Use Case Specification for the Voting system use case: 1.0 Use Case NameVoting System

1.1 Brief DescriptionThis use case is started by the Authentication system use case. It provides the capability to the system to process the voters ballot.

2.0 Flow of Events 2.1 Basic FlowThis Use Case begins when the voter is identified as the valid voter by the Authentication system.

10

2.2 Alternate Flows 2.2.1 Invalid Ballot:An invalid ballot of voter is rejected and prompts the voter to perform correct ballot, i.e., when the submit button is pressed without selecting the candidates vote/ballot, then the above said operation will be taken place.

2.2.2 Cancellation of Ballot:If voter selected the cancel operation at any time before the submit button is pressed, and then this use case cancels the noted ballot.

3.0 Special RequirementsThere are no special requirements.