DAMBI DOLLO UNIVERSITY

COLLEGE OF ENGINEERING AND TCHNOLOGY

DEPARTEMENT OF COMPUTER SCIENCE

PROJECT TITLE: WEBBASED VOTING SYSTEM

Done By
Group Members ID number

1. BEKALU WONDAWOK NSR/284/20

2. ABEL ABERA NSR/070/20
3. BONTU TESFA NSR/ 1556 /20
4. WAQJIRA YADETA NSR/1322/20

Advisor name

M.R Mendasa Tesfa

March, 2024

Dambi Dollo Ethiopia

 DECLARATION
This is to declare that the project entitled “ONLINE VOTING SYSTEM” has been carried out by:
BEKALU WONDAWOK, BONTU TESFA, WAQJIRA YADETA and ABEL ABERA. This
online voting system project is ours and it is designed and implement by the members effort.
Under my guidance and supervision, for the partial fulfillment of the requirement for the award of
degree of Bachelor science in computer science.

Project Advisor: Head of Department:

INS: - Mendasa Tesfa. Ms. Laty Wakuma

Signature: ____________ Signature: ____________

Examiners:

Name: Signature:

1.________________________________ _____________

2.________________________________ _____________

i|Page
 Acknowledgement
First we thank the almighty of God he helped us to do this project. This project is not done only by
our effort. It has got an input from different individuals. First of all, we would like to present our
gratitude to our advisor, instructor Mendasa Tesfa for his help; the department of computer
science on confirming the proposal of our project and facilitating conducive environment for the
work; last, but not least, to all our friends and others who gave us comments on our work. Without
the contribution of these people, our work would not be successful. We would like to say once
again Thank You to you all.

ii | P a g e
 Abstract
The intension of this project is developing automated voting system for Ethiopia. The current
mechanism for handling the vote management system of the country is limited on manual work.
This has limitation on declaring the result on time, and has high consumption on resources. Many
countries have used different technologies to support their voting activity and have got successful
results. Electronic voting is the most known technology for voting from the existed alternatives. It
is used for citizens who live abroad to elect their party thorough internet. The experience of other
countries is used as an input for the system .The requirements for the system are collected from
historical records and policies of the Ethiopian election. The system architecture, the security risks,
and the implementation details of the system are also included in the document. so our project goal
is to fix the problems in the manual system and generate flexible efficient and accurate voting
system for peoples that participate in the vote.

iii | P a g e
 Table of Contents
DECLARATION ................................................................................................................................ i
Acknowledgement ............................................................................................................................. ii
Abstract ............................................................................................................................................. iii
Table of Contents .............................................................................................................................. iv
ACRONYMS .................................................................................................................................. viii
CHAPTER ONE ................................................................................................................................ 1
1. INTRODUCTION ......................................................................................................................... 1
1.1 Background .............................................................................................................................. 1
1.2. Statement of the problem ........................................................................................................ 1
1.3. Objective of the project ........................................................................................................... 2
1.3.1 General objective ............................................................................................................... 2
1.3.2 Specific objective .............................................................................................................. 2
1.4. Scope of the project ................................................................................................................. 2
1.4.1 Scope of the project ........................................................................................................... 2
1.5 Feasibility Study of the new System ........................................................................................ 2
1.5.1 Operational Feasibility ...................................................................................................... 3
1.5.2 Technical Feasibility.......................................................................................................... 3
1.5.3 Economic Feasibility ......................................................................................................... 3
1.6. Significance of the project....................................................................................................... 3
1.7. Methodology and software used ............................................................................................. 4
1.7.1. Fact finding techniques ..................................................................................................... 4
1.7.2. System analysis techniques .............................................................................................. 4
1.7.3. Tools to be used in this project ......................................................................................... 4
1.9Cost Scheduling......................................................................................................................... 4
01.10 Team organization ................................................................................................................ 5
2 REQUIREMENT ANALYSIS AND SPECIFICATION ............................................................... 7
2.1 Description of the current system............................................................................................. 7
2.1.1. Practices to be preserved from the existing system .......................................................... 7
2.2 Actors in the existing system ................................................................................................... 7
2.4 Business Rule of the current system ........................................................................................ 8

iv | P a g e
 Business rule of the new system .................................................................................................... 8
2.5 Classes Responsibilities and collaboration (CRC) Modeling .................................................. 9
2.5.1 Classes and their Responsibilities ......................................................................................... 9
2. 6 Proposed Systems .................................................................................................................. 10
2.6.1 Overview of the proposed system ....................................................................................... 10
2.7 Requirement Analysis ............................................................................................................ 11
2.7.1 Functional requirements .................................................................................................. 11
2.7.2 Nonfunctional requirements ............................................................................................ 11
2.8. Use case diagram ................................................................................................................... 12
2.8.1. Modeling the Functions of the system (Use Case Modeling) ........................................ 12
2.8.2. System models and the artifacts .................................................................................... 13
2.9 Dynamic Models .................................................................................................................... 18
2.9.1 Sequence diagram ............................................................................................................ 18
2.9.2 Activity diagram .................................................................................................................. 26
2.9.3 State chart diagram .......................................................................................................... 28
2.9. 4 User interface prototyping design................................................................................... 31
CHAPTER THREE ......................................................................................................................... 34
3 SYSTEM DESIGN ....................................................................................................................... 34
3.1 INTRODUCTION .................................................................................................................. 34
3.2 Purpose of Design .................................................................................................................. 34
3.3 Design Goals .......................................................................................................................... 34
3.4. Architecture of the System ................................................................................................. 34
3.5. System Decomposition ........................................................................................................ 36
3.6 Component Modeling............................................................................................................. 37
3.7 class design diagram............................................................................................................... 38
3.8. Deployment Diagram ............................................................................................................ 39
3.9. Persistent Data Management ................................................................................................. 40
3.10. Security Technique .............................................................................................................. 41
Reference ...................................................................................................................................... 43

v|Page
LIST OF TABLES
Table 1 cost scheduling .............................................................................................................. 5
Table 2 team organization .......................................................................................................... 5
Table 3 class and thier responsibility ......................................................................................... 9

vi | P a g e
 LIST OF FIGURES
Figure 1 Main use case diagram ______________________________________________ 13
Figure 2 Sequence diagram for login ___________________________________________ 19
Figure 3 Sequence diagram for logout. _________________________________________ 20
Figure 4 Sequence Diagram for cast vote. _______________________________________ 21
Figure 5 Sequence diagram for Register candidates. _______________________________ 22
Figure 6 Sequence diagram for Create Account. __________________________________ 23
Figure 7 Sequence diagram for generate report ___________________________________ 24
Figure 8 sequence diagram for register voters. ___________________________________ 25
Figure 9Sequence diagram for view result initiated by the Election officer. ____________ 26
Figure 10 activity diagram for cast vote ________________________________________ 27
Figure 11 Activity diagram for login ___________________________________________ 27
Figure 12 A ctivity Diagram for election register _________________________________ 28
Figure 13 Activity Diagram for candidate _______________________________________ 28
Figure 14 state chart diagram for generate report _________________________________ 29
Figure 15state chart diagram for Register _______________________________________ 30
Figure 16 state chart diagram for register voter ___________________________________ 30
Figure 17, state chart diagram for profile manipulation ____________________________ 31
Figure 18User interface Diagram. _____________________________________________ 32
Figure 19 system architecture Diagram _________________________________________ 35
Figure 20 System decomposition Diagram ______________________________________ 37
Figure 21 Component Diagram. ______________________________________________ 38
Figure 22 class design diagram _______________________________________________ 39
Figure 23 Deployment Diagram. ______________________________________________ 40
Figure 24 Database Design diagram. ___________________________________________ 41

vii | P a g e
 ACRONYMS
 BR……………………………………………….Business Rule

 CPU…………………………………………….Central Processing Unit

 RAM……………………………………………..Random Access Memory

 HTTP…………………………………………….Hyper Text Transfer Protocol

 MYSQL…………………………………………My Structure Query Language

 PHP……………………………………………Hyper Text Pre Processor

 HOR…………………………………………..House Of Representatives

 NEBE………………………………………National Election Board of Ethiopia

viii | P a g e
 CHAPTER ONE

1. INTRODUCTION
1.1 Background
Election or voting is a formal process by which Voters make their political choice on public office
or candidates for public office. It makes a fundamental contribution to democratic governance. The
Constitution of the Federal Democratic Republic of Ethiopia, in its article 56, declares a Political
Party or a Coalition of Political Parties that has the greatest number of seats in the House of
People's Representatives shall form the executive and lead it. Also in the Amended Electoral Law
of Ethiopia, Proclamation clearly puts that a Candidate who received more votes than other
Candidates within a Constituency shall be declared the winner. (1).

Elections allow the populace to choose their representatives and express their preferences for how
they will be governed. Naturally, the integrity of the election process is fundamental to the
integrity of democracy itself. The election system must be sufficiently robust to withstand a variety
of fraudulent behaviors and must be sufficiently transparent and comprehensible that voters and
candidates can accept the results of an election. (2)

In the present the election system in Ethiopia is using paper ballot and there are 45 000 polling
stations in the country which makes the voting process more time consuming and needs man
power to execute the voting process. This existing election system in Ethiopia has many problems
during the election process and the outcome of actual results and it is not a kind of election system
they can trust. The integrity of the election process is fundamental to the integrity of democracy
itself.

Therefore, the purpose of this study is to develop a web-based voting system in which is which
votes can be casted electronically and also used for counting results instead of traditional manual
schemes.

1.2. Statement of the problem

In Ethiopia, elections take place every five years to elect members of HOR. The electoral
procedure involves many processes. The processes are voter Registration, Voter Register

1|Page
Exhibition, Voting, Vote Counting, Collation and Publication of Results. (3)A number of problems
associated with each phase of the electoral process are such as Invalid votes, long voting process,
Delays in result publication, and High cost of election organizing those are the problems during the
election time. Therefore, this project is an effort in solving the problems associated with each
phase of the electoral process. The Efforts may be geared towards the minimization, if possible the
total elimination of the problems associated with the manual election system. (4)

1.3. Objective of the project

1.3.1 General objective
The main objective of the project is producing a web based voting system that can supplement the
current paper based voting system of Ethiopia.
1.3.2 Specific objective
 Identifying the existing problem
 Designing friendly user interface

 Designing database to the system that can hold all the information

 Implementing standard security algorithms that can keep the confidentiality of the data.

 Testing the system

1.4. Scope of the project

1.4.1 Scope of the project
The scope of this project is developing web based voting system for Ethiopia specifically for
Dambi Dollo city. There are different kinds of electronic voting system in the world, but this
project targets to do web based voting system. The system contains modules that can handle
voters’ and candidates’ registration system, including vote counting module. Generally the system
works thought the country; specifically it begins in Dambi Dollo city.

Our system cannot help any blind voter those wants to vote their representatives by sound
synthesizer and illiterate voter.

1.5 Feasibility Study of the new System

Feasibility study is essential to evaluate the cost and benefits of the new system. On the basis of
the feasibility study decision is taken on whether to proceed or to cancel the project.
Need of the feasibility study:
 It determines the potential of the existing system.
2|Page
  It used to determine/finds out the problem of the existing system.
 To determine all goals of the new system.
 It finds all possible solutions of the problems of the existing system.
1.5.1 Operational Feasibility
The system to be developed will provide accurate, active, secured service and decreases labor of
workers and also it is not limited to particular groups or body. And also it is platform independent
i.e. it run’s in all operating system.
1.5.2 Technical Feasibility
The system to be developed by using technologically system development techniques such as
asp.net, Java script, css and MYSQL database server without any problems and the group members
have enough capability to develop the project. So the system will be technically feasible.
1.5.3 Economic Feasibility
The system to be developed is economically feasible and the benefit is outweighing the cost. Since
this project already computerizes the existing system, by now the reduction of cost for materials
used in manual operation becomes beneficiary to the organization.
Generally the system that we developed, online voting system brought a number of tangible and
intangible benefits.
1.5.3.1 Tangible benefits:
 Cost Reduction.
 Error Reduction.
 Increase Speed of activity.

1.5.3.2 Intangible benefits:

 Reduce Resource Consumption.
 Increase security.

1.6. Significance of the project

The main purpose of online voting system is to boost voter satisfaction by providing quick easy
and timely voting, decreasing the expense that the election board bears during the voting process in
order to support the success of the manual system by paying the numerous clerks that are hired.
During the election this system requires few employees, used to provide service particularly to
allow foreign residents to choose their party online it is far simpler to independently moderate the
elections and then strengthen the systems equity and openness. To create an efficient election
management system, online voting methods must be extremely accurate or cost-effective.
3|Page
1.7. Methodology and software used
1.7.1. Fact finding techniques
 Interview
The additional data would be gathered through the technique of interview, through this technique
we get different information’s from the current workers of the organization and from peoples who
have been participating on voting before.
 Document(literature review)
We will collect information from different references, projects and web sites.
1.7.2. System analysis techniques
We use some system analysis technique for our project development. Some of them are:
 Use case diagram
 Sequence diagram
 Activity diagram
 Class diagram
 Database diagram
1.7.3. Tools to be used in this project
1.7.3.1 Software requirement
This project team will use the HTML as a front end and the SQL Server as a back and or database
tool to develop the new computer based system. In addition to these programing and database tools
we will use additional software to different tasks. These are Microsoft word 2013, Rational Rose,
Edrew max, Microsoft PowerPoint 2013, Xampp Server, mySql database server, and Notepad++.

1.7.3.2 Hardware requirement

The hard ware tools that we are developed is these, any Desktop Computer, Flash disk 2GB - 8GB
, Compactable CD-ROM 700MB, and Laptop

1.9Cost Scheduling

No. Teams Quantity Total price(birr)

1 Computer and laptop 1(for development and Free
deployment purpose)
2 Printing 300

4|Page
 3 Ms office free
4 Paper 1 packet 100

5 Mysql database server free

6 Xamp server free

7 Notepad++ free
9 Edrow max Free
Total 400
Table 1 cost scheduling

1.10 Team organization

Table 2 team organization

Tasks Responsible person Deliverables

PROJECT INITIATION AND PLANNING
Explanation of the existing Bekalu Wondawok
system Existing system documentation
Major functions of existing Bekalu Wondawok and Abel
system Abera
PROJECT ANALYSIS
Use case modeling Bekalu Wondawok And Use case diagram and
Waqjira Yadeta description
Sequence diagramming Bekalu Sequence diagram
Activity diagramming Bontu Activity diagram
Functional & non Functional Abel Abera and WAqjira User Requirement
Requirement Yadeta documentation
PROJECT DESIGN
State chart modeling Bekalu State chart diagram
Design class diagramming Bekalu And Waqjira Class diagram
Collaboration diagramming Bontu And Abel Collaboration diagram
Component diagramming Bontu and Waqjira Component diagram

5|Page
User interface diagramming BekaluAnd Abel User interface flow diagram

PROJECT IMPLEMENTATION
Coding All group members Project code
Testing All group members Checked the code and tested the
system

6|Page
 CHAPTER TWO

REQUIREMENT ANALYSIS AND SPECIFICATION

2.1 Description of the current system
The Current system is the manual system that needs intensive human labor, resource, consume
time, less security. First of all in these manual systems voters have requested to register.

2.1.1. Practices to be preserved from the existing system

Even if the existing system has a lot of problems, there are a number of activities that need to be
preserved. Those are:-

 Existing data storage system is partially automated for use; Since the NEBE used
manually and partially automated data storage system. This stored data has a vital role in
the case power lose and when the automated system got the affected by the virus.
 Registration: - shall be made up on presentation of an identity card or passport.
 Distribution of tasks:-Here everyone has its duty to do and come over the problem of
overloading the work to some part of the workgroup.

2.2 Actors in the existing system

There are different players in the existing system:-
1. Voters:-
 They should vote their candidates.
 View the result.
2. Election offices:-
 Register the candidates.
 Coordinates and manages the workers and co-workers.
 Count the votes.
 Report the result.
3. Workers and co-workers:-
 Register the voters.
. 4. Candidates:-
 Candidates registered by Election offices.
5. Spectators:-

7|Page
  They should see what is going on in the election.
In our proposed system
Actors in the new system
 System Admin
 Election Officer
 Election Registrar
 Voter
 Candidate

2.4 Business Rule of the current system

BR1: To vote at Federal level:-

 You must be above 18 years old.

 You must be an Ethiopian.
 Has not served a term of imprisonment is eligible to vote.
 You must reside within the constituencies for at least 6 months.
BR2: The voter must be come to the office on the registration day.
BR3: The Election Offices can register the candidates and tell when the Election date is begin.
BR4: The Workers can register the voters and tell, when the Election date is begun.
BR5: The voter must come in the given schedule.
BR6: The voter can select one candidates and putting an "X" mark across the symbol of the
candidate on a voting paper box.
BR7: The Election Officer can coordinate the workers and the co-workers in the time of Election.
BR8: The NEBE can announce the result in mass media such as: - TV, Radio, Magazines, Internet
etc...

Business rule of the new system

BR1: To participate in vote at Federal level You must be above 18 years old, You must be an
Ethiopian and Has not served a term of imprisonment is eligible to vote.

BR3: The Election Offices can register the candidates and tell when the Election date is begun.

BR4: The Election Registrar can register the voters and tell when the Election date is begin.
BR5: The voter must vote in the given time schedule online.

8|Page
BR6: The election page must be activated on the Election Day and deactivated when the election
schedule time ends.
BR7: The voter can select one candidate and select the check box across the symbol of the
candidate.
BR8: The System show the result online as soon as the voting starts
BR9: The system user must use their ID as their username and password to cast a vote and do
other activities.

2.5 Classes Responsibilities and collaboration (CRC) Modeling

Classes’ responsibilities and collaborator (CRC) is technique used for identifying classes’
responsibilities and their attributes and methods. They also help in identifying the classes. Class’s
responsibilities and collaborators are based on the ideas that an object either can accomplish a
certain responsibility itself or it may require the assistance of other objects. To fulfill its
responsibility identifying an object’s responsibilities and collaborators attributes and methods can
be identifies.
The classes, Responsibilities, and Collaborators process consists of three steps:
 Identify responsibilities(and identify classes)
 Assign responsibilities
 Identify collaborators

2.5.1 Classes and their Responsibilities

Table 3 class and thier responsibility

No. Class Name Responsibilities

1. System Admin Manipulate database and create account for the
system users.
2. Voter Castes his/her vote and views candidate profile

3. Election Registrar Register voter, view profile and view result.

4. Election officer Generate result, view profile of the selected user,

register candidate

9|Page
 5. View profile Displays the required profile information

6. View result Displays the election result

7. Voter register Registers the voters
8. Candidate register Registers the participant candidates
9. Profile manipulation Updates the selected profile in the database

10.General manipulation Update and add new feature to the system

11.Generate result Count the vote and generate the result

12.Login Check the validity of the system user
13.Check Eligibility to cast vote Validate the reliability of system
14.Create Account Creates account for the system user

2. 6 Proposed Systems
2.6.1 Overview of the proposed system
The main aim of this project is to automate the current manual system and it will solve the
problems that are in the manual system. This system saves resources by doing all things used in
election system; and counts the result for each candidate correctly and report with exact value
electronically. The new system does not pass over without reporting the occurred errors during the
counting result. Also in security side our system is secured because, it needs User name and
Password. Before the Election Day the system will be used for viewing candidates’ profiles. Our
system will be in election mode, for the purpose of vote casting only on the Election Day. and also
our project will work in peoples who live in abroad or outside the country they can participate the
election in online. These systems will be used for Reducing the time and task required to perform
the operation within the election area; it will change the manual processing to computerize system,
It will provide speed, efficient, Flexibility, reliability, and security for the system users, For voters,
better satisfaction of the speed provided by the system casting their vote.

10 | P a g e
2.7 Requirement Analysis
2.7.1 Functional requirements
Functional requirements describe the interactions between the system and its environment
independent of its implementation. The environment includes the user and any other external
system with which the system interacts. The following points list down the functional requirements
of our system:-

 Register Election Officer: The person who takes care of conducting the elections by
declaring the election details should be declared the result.
 Register Candidates: Before the vote casting process begins, the election offices needs to
register the candidates.
 Check authorization to cast a vote: Our system will check whether the voter is
authorized to cast a vote or not by interacting with database.
 Cast Vote: When the voter keys the correct Username and Password to the system, the
system will extract the eligible candidates on that polling station, then, the voter casts the
vote by keeping the rules.

 Generate report: At the end of the election, the System will generate the reports based on
the polling stations code.
 Counting: This system will count the votes automatically so the counting process will be
faster and that will help to publish the result faster.
 Authentication: Election offices have their own credentials stored in the database. The
system will check the keyed values against the values stored in the database.
2.7.2 Nonfunctional requirements
Non-functional requirements (also known as quality requirements), which impose constraints on
the design or implementation (such as performance requirements, security, or reliability).

 Usability Requirements: - It is expected that the user should be able to vote easily online.
User should complete voting in a few minutes. Provide an online help and a quick guide for
users.
 Reliability Requirements: - The system should be reliable. Security is a major concern for
an online voting system. Process used in this system should be secure enough to be able to
meet the requirements mentioned for online voting. It requires database connections and

11 | P a g e
 network connections. Changes can be done in the databases to store the votes. All changes
needs to be confirmed and if the transfer is complete the confirmation should be displayed.
The changes should be monitored.
 Performance Requirements: - There might be many users accessing to the web server
simultaneously. As an online voting tool performance shouldn’t be affected much and
response time for submitted page should be less than a minute.
 Security Requirements:- The system should provide basic security features like password
authentication. 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.
 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 Election officer should set up his system time
appropriately for the election process to start at the correct time. The system should be
capable of gracefully recovering from earlier crashes and continuing the voting process

2.8. Use case diagram

2.8.1. Modeling the Functions of the system (Use Case Modeling)
The main activities that are performed in this part will be:
 Identifying if there is any additional actors and use cases,
 Constructing a use case model, and
 Documenting the use case course of events
Use Case represents interaction between a user (human or machine) and the system.
Use case components:
 Actor: is a person, or external system that plays a role in one or more interaction with the
system. And represented with:

 Use case: describes a sequence of actions that provides something of measurable value to an
actor and is drawn as a horizontal ellipse.

12 | P a g e
  System boundary: indicates the scope of the system project. Anything within the box
represent functionalities in side in scope.
System

2.8.2. System models and the artifacts

2.8.2.1 Use case diagram

Figure 1 Main use case diagram

2.8.2.2Actor Description
 System Admin: perform login, create account, generate report and control the system.

13 | P a g e
  Election officer: perform login, register Election Registrar and approve (register)
Candidate and manipulate the profile of the election registrar and candidate when there is a
change.
 Election Registrar: perform login, register voter and manipulate the profile of the voter
when there is a change.
 Voter: perform login and cast vote.
 Candidate: perform login and advertise information.

2.8.2.3Use Case Description

Table 4 use case description

Use case name: Login

Use case id: 01

Description: used to authenticate used to authenticate the user

the user
Actors: Administrator, voter, candidate, Precondition
Precondition The actors should activate the system.
Basic course of action:  1.The actor instantiate login page
 Login page will be activating
 Actor enters user name and password and clicks login
button
 System checks the validity of the provided information
 If the user ID and password are valid, the actors will be
logged on to the system
 Confirmation message will be. Displayed
 7. Workers home form displayed
Post condition: the actor should log on successfully
Alternative course of action:
 actor enters user name and password and clicks
login button
 system checks the validity of the provided
information
 If the user ID and password are invalid.
 The system displays “error message”.
 5. The system asked to re-enter user name and
password.
Use case name: Cast Vote

Use case id: UI-2

14 | P a g e
Description: used to authenticate This use case is initiated by the voter. This use case will enable
the user the voter to cast one vote at a time. It provides the capability to
the system to process the voter’s ballot.
Actors: Voter
Precondition The voter must have valid user id.
Basic course of action: This use case begins when the voters select cast vote from
main page.
 The system shall display the well come page.
 The voter will insert his/her id number and encrypted
code.
 The system shall check the id number and encrypted
code with the existing id number and encrypted code.
 The system will open.
Post condition: The voter can vote one candidate.
Use case name View Result
Use case id: UI-3

Description: used to authenticate This use case is initiated by the voters, candidate, Election
the user Officer, system Admin and Election Registrar. It provides the
capability to the system to perform the counting of ballots
polled for each candidate and announces the election results.
Actors: Voter, Election Officer, candidate system Admin and Election
Registrar.
Precondition Ballot information should be secured before the counting
Basic course of action: The Use Case begins when the voter, Election Registrar,
Election Officer sends request to view the result.
Post condition: Must report the result to the voters, Election Registrar,
Election Officer.
Use case name Register
Use case id: UC-4

Description: used to authenticate this use case is initiated by the Election officer and Election
the user Registrar. It provides to register voter and candidate
Actors: Election officer, Election Registrar
Precondition The Election officer and Election Registrar must log on the
system
Basic course of action:  The Election officer must activate the system.
 The Election officer fills user name and password on
the login page.
 The system shall check the user name and password
with the existing user name and password.
 The system will open the Election officer page or the
Election Registrar page.
 The Election officer or Election Registrar will be
registering the voter/candidate. 6. The Election officer/
15 | P a g e
 Election Registrar click the save button.
Post condition: The Election officer/ Election Registrar register the candidate
or voter respectively
Use case name Create Account
Use case id: UC-5

Description: used to authenticate this use case is initiated by the System Administrator. It
the user provides to Create Account.
Actors: System Administrator
Precondition The System Administrator must log on the system.
Basic course of action:  The administrator selects Create account from
account menu.
 Create new account user interface displayed. The
administrator insert account name, password.
 Click of create account button.
 . New account created message displayed to the
administrator

Post condition: System Administrator Creates Account

Use case name Generate Report
Use case id: UI-6

Description: used to authenticate this use case is initiated by the Election Officer. It provides
the user to generate result.
Actors: System Admin
Precondition The Election Officer must log on the system.
Basic course of action:  The System admin must activate the system. The
System Admin select report form from Report menu
Report from menu interface displayed.
 The System can generate the report from the page.
Post condition: The System Admin generate result that the system can
count the casting vote.
Use case name View Profile
Use case id: UI-7

Description: used to authenticate This use case is initiated by the voters, Election Registrar,
the user Election Officer. It provides the capability to the system to
View each candidates
Actors: Voter, Election Registrar, Election Officer
Precondition The Actors must activate the system
Basic course of action: The Use Case begins when the voter, Election Registrar,
Election Officer sends request to view the Profile.
Post condition: Must report the Profile to the voters, Election Registrar,
Election Officer.
Use case name Profile Manipulation

16 | P a g e
Use case id: : UI-8

Description: used to authenticate This use case is initiated by Election Registrar, Election
the user Officer, and System Admin. It provides the capability to
the system to process the profiles of the voters and the
candidates. The processing here includes creation,
modification and deletion process.
Actors: Election Registrar, Election Officer, System Admin
Precondition the Election Registrar, Election officer, and System Admin
must log on to the system. And the election database must
be the updated one, before this use case is started.
Basic course of action:  First the Election Officer ,Election Registrar, and
System Admin must initiate the system by log on to
the system
 And then those actors select the update form from
the profile menu
 Then update page displayed
 The Election Officer, Election Registrar, and
System Admin can update the profile that has to be
updated.
Use case name : General Manipulation
Use case id: : UI-9

Description: used to authenticate This use case is initiated by System Admin; update and add
the user new feature to the system.
Actors: System Admin
Precondition the system admin must logon to the system first.
Basic course of action:  The system admin must activate the system first –
 The Admin then go to main database system and
manipulate the database

Use case name : System control

Use case id: : UI-10

Description: used to authenticate This use case is initiated by System Admin. And the system
the user Admin control the system by activating it
Actors: System Admin
Precondition the system admin must logon to the system first.
Basic course of action:  The system admin must activate the system first
 The Admin then go to main database system and
activate the system from the database.

17 | P a g e
2.9 Dynamic Models
2.9.1 Sequence diagram
A Sequence diagram is an interaction diagram that shows how processes operate with one another
and in what order. It is a construct of a Message Sequence Chart. A sequence diagram shows
object interactions arranged in time sequence. It depicts the objects and classes involved in the
scenario and the sequence of messages exchanged between the objects needed to carry out the
functionality of the scenario. Sequence diagrams are typically associated with use case realizations
in the Logical View of the system under development. Sequence diagrams are sometimes
called event diagrams or event scenarios.

A sequence diagram shows, as parallel vertical lines (lifelines), different processes or objects that
live simultaneously, and, as horizontal arrows, the messages exchanged between them, in the order
in which they occur. This allows the specification of simple runtime scenarios in a graphical
manner.

The main purpose of a sequence diagram is to define event sequences that result in some desired
outcome. The focus is less on messages themselves and more on the order in which messages
occur; nevertheless, most sequence diagrams will communicate what messages are sent between a
system's objects as well as the order in which they occur.

18 | P a g e
 Home page Login link Login Form Controller Database
: user
1.isite Home page()

2.select Login link()

3.Display the login form()

4.Fill username and password()

5.Submit()
6.validator()

7.Try again
8.step 5 continue

9.check()

10.Display the target page()

Figure 2 Sequence diagram for login

19 | P a g e
 Logout link System controller
: user

1.click logout link()

2.logout()
3.close user session()

4.Display the login form()

Figure 3 Sequence diagram for logout.

20 | P a g e
 Login form Login controller Voter page cast vote UI System Database
: Voter
controller
1.fill the form()

2.Submit()
3.validate()

4.try again()

5.continue()

6.Display the voter page()

7.select candidate()

8.click the vote button()

9.validate()

10.try again()

11.continue()

12.save vote()

13.Display succesfull mesage()

Figure 4 Sequence Diagram for cast vote.

21 | P a g e
 Election officer Register Register Controller Database
: Candidate
page Candidate link Candidate Form

logon to the EOP()

select the RG link()

Display the registration form()

fill the form()

Submit()
validate()

try again()

continue()

register()

succesessfully registered()

Figure 5 Sequence diagram for Register candidates.

22 | P a g e
 System Admin Create Account Create Account System Database
: Admin
page link Form controller

logon to the system()

select the create account link()

Display the create account Form()

Fill the form()

submit()
validate()

try again()

continue()

register()

successesfully registered()

Figure 6 Sequence diagram for Create Account.

23 | P a g e
 Admin page Report UI System Database
: Admin
controller

logon to the page

select type of the report

click report button()

validator()

try again()

continue()

retrive()

Display the targeted report()

Figure 7 Sequence diagram for generate report

24 | P a g e
 Election Register link Register Form System Database
: Election
Registerar page controller
Registerar

logon to ERP()

select Register link

Display the register Form()

Submit()

Validate()

Try again()

continue()

Register()

Display succesessful message()

Figure 8 sequence diagram for register voters.

25 | P a g e
 Election Officer View Result UI System Database
: Election officer
page controller

lgoin to the EOP()

select type of result()

click result buttone()

validate()

Try again()

continue()

View result()

Display the result()

Figure 9Sequence diagram for view result initiated by the Election officer.

2.9.2 Activity diagram

Activity diagram is another important diagram in UML to describe dynamic aspects of the system.
Activity diagram is basically a flow chart to represent the flow form one activity to another
activity. The activity can be described as an operation of the system. So the control flow is drawn
from one operation to another. This flow can be sequential, branched or concurrent. Activity

Diagrams deals with all type of flow control by using different elements like fork, join etc. The
purposes of activity diagram can be described as:

 Draw the activity flow of a system.

 Describe the sequence from one activity to another.
 Describe the parallel, branched and concurrent flow of the system.

26 | P a g e
 Figure 10 activity diagram for cast vote

Figure 11 Activity diagram for login

27 | P a g e
Figure 12 A ctivity Diagram for election register

Figure 13 Activity Diagram for candidate

2.9.3 State chart diagram

A state chart diagram is a view of a state machine that models the changing behavior of a state.
State chart diagrams show the various states that an object goes through, as well as the events that

28 | P a g e
cause a transition from one state to another. The common model elements that state chart diagrams
contain are:

 States
 Start and end states
 Transitions
A state represents a condition during the life of an object during which it satisfies some condition
or waits for some event. Start and end states represent the beginning or ending of a process.

Figure 14 state chart diagram for generate report

29 | P a g e
 initial state Idel Activate Fill the Send register normal exit Verfiy
Form request

un normal exit
leave the page
Evaluate
Final state

Confirm

complite state

Figure 15state chart diagram for Register

Initial sate Idel Activate send vote select normal exit verify
request candidate

un normal exit
failed

Evaluate

Final
state

confirm

complete state

Figure 16 state chart diagram for register voter

30 | P a g e
 fill update request
initial state Idel send update normal exit Edit
request

Evaluate

un normal exit ignor edit

Confirm

Final state

Save

complete state

Figure 17, state chart diagram for profile manipulation

2.9. 4 User interface prototyping design

A user-interface prototype is a prototype of the user interface. It is an iterative analysis technique
in which users are actively involved in the mocking-up of the UI for a system.

31 | P a g e
Figure 18User interface Diagram.

User Interface Description

1. Home Page: Description:- This user interface is a place where Online Voting are viewed and
links for related topics (websites) are also mentioned in this user interface.

2. Login Page: Description: - This page is the most important and key user interface to the system.
It is a place where the system users (voters, Election Offices, Election Registrar, administrators)
get access to the system by entering their user name and password. A user must provide a valid
user id and password to access the next user interfaces.

32 | P a g e
3. Voter: Description:-This User interface is used to vote the candidates by using his encrypted
code and user name.

4. Election Officer: Description:- This User interface is used for the Election Officers can login to
the system and register the candidates.

5. Election Registrar: Description: - This User interface is used for the Election Registrar's can
login into the system and register the voters.

6. View Result: Description:-This User interface is used to view the result that can generate by the
Election Officer.

7. System Administrator: Description: - this interfaces used for Administrator only to Add,
delete, and change data and user account.

8. Create Account: Description: - This interface allows the administrator to add workers name, id,
and password to the workers list of the system.

9. View Profile: Description: - This interface used for the voter that can view the profile of the
candidates

33 | P a g e
 CHAPTER THREE

3 SYSTEM DESIGN
3.1 INTRODUCTION
This chapter of the project document which provides a system design of this project. This chapter
contains and describes about Component modeling, Deployment diagram, User interface
prototyping design, Database design and Class mapping.

3.2 Purpose of Design

The purpose of designing is to show the direction how the Application is built and to obtain clear
and enough information needed to drive the actual implementation of application. It is based on
understanding of the model the Application built on system design also focuses on decomposing
the system in to manageable parts.

3.3 Design Goals

The objectives of designing are to model a system with high quality. Implementing of high quality
system depends on the nature of the design created by the designer. If one wants to make changes
to the system after it has been put in to operation depends on the quality of the system design. So if
the system is designed perfectly, it will be easy to make changes to it.

The goal of the system design is to manage complexity by dividing the system in to manageable
pieces. Some of the goals are listed below.

 Modifiability: The system should be modifiable to modify different services depending on

the need of the user.
 Flexibility: The system should be changeable to suit new condition or situation.
 Efficiency: The system must do what it supposed to do efficiently without the problem.
 Accessibility One of best feature of proposed system is its accessibility. Users can access
the current information being everywhere in the country as well as on internet.

3.4. Architecture of the System

The architecture chosen for the system is three tiers. The first layer runs on the client side, the
second layer at the middle layer and the third layer will be the database system. The system will
run using web technology. This architecture provides greater application scalability, high

34 | P a g e
flexibility, high efficiency, lower maintenance, and reusability of components. Since each tier runs
on a separate machine, it improves systems performance.
The system uses dynamic web technology, i.e., adding and retrieving data to and from the data
store whenever requested is possible. It requires a client side program which is accessed by the
Election officer, by the registrar, by the voter and also an interface that communicate with the
external system. It needs server side functions that implement the functional requirements and the
database system that stores data.

Figure 19 system architecture Diagram

Client Tier: As described in shown in Fig. 20, at the client side there are five kinds of users. The
first user is the System Admin. This person is responsible for adding critical data to the system
control and activates the system. The type of data is like Election Officer’ Authorization,’
username and password, control and activate the system. The final report is also generated by this
person. The second user is the Election officer. This person is responsible for registering Election
Registrar and approves Candidates, and manipulation the profile of the registrar and the candidate.

The third user is Election Registrar. This user is responsible for registering voter and manipulating
voter’s profile. And he can cast a vote.
The fourth user is the voter; the role of this voter is casting votes. The interface used by the voter is
web form. As vote casting is processed at the polling stations, which are distant from the database

35 | P a g e
server. The fives user is candidate; the role of this candidate is advertising information and he also
can cast a vote.
Middle Tier: The middle tier will contain the core parts of the vote application, i.e., the web
server and business logic. The web server will handle all requests coming from the client
machines. The requests are different with its type, for example; request for data insertion, request
for report generation and others. It is also the web server which the responses that is forwarded to
the client machines.
The business logic part will hold the process and core functions that will be implemented in the
system. When the data is submitted from the client machines, first it will be handled by the
functions of the web server and then transferred to the business logic for processing. Again, the
business logic processes the data and sends it either to the database or back to the web server, this
is determined by the type of service required.
Data Tier: The system uses one database; this database is the repository consisting of the
application data. It is here that all the database tables will be stored.

3.5. System Decomposition

System decomposition refers to the process by which a complex problem or system is broken
down into parts that are easier to conceive, understand, program, and maintain. To reduce the
complexity of the solution domain, we decompose our system into simpler parts, called
subsystems, which are made of a number of solution domain classes. In the case of complex
subsystems, we recursively apply this principle and decompose a sub- system into simpler
subsystems. We decompose our system in to six subsystems. These are:
 Registration system, Account creation, Candidate registration, Voter registration
 Profile manipulation system, Update account, Delete Account/user, Change password,
Update profile
 View system, View profile, View comment, View result
 Report system
 Vote system
 Comment and Advertisement system

36 | P a g e
 Figure 20 System decomposition Diagram

3.6 Component Modeling

Component based development ( CBD) and object oriented development go hand in hand and it is
generally recognized that object technology is the preferred foundation from which to build
components the UML includes a component diagram that can be used to both analyze and design
our component based software it shows the various components in a system and their
dependencies.

In this Diagram components of the system will be wired showing that there is relation
among components, management of the system, database and operations performed on

37 | P a g e
databases such security issue. This in some extent shows which component or objects will
be accessed by whom and what type of security infrastructures it is using. The diagram is
simulated below.

Figure 21 Component Diagram.

3.7 class design diagram

Class diagrams are used to represent the structure of the system in terms of objects, their notes and
nature of relationship between classes. It shows the static features of the actors and do not
represent any particular processing. It is an abstraction of the real environment class of, user and

38 | P a g e
Administrator.

Figure 22 class design diagram

3.8. Deployment Diagram

Deployment modeling is used to show the hardware of the system, the software that is installed in
the hardware and also the middleware that is used to connect the dissimilar machines to one and
other. It also shows how the software and the hardware components work together in order
perform the task.

39 | P a g e
Figure 23 Deployment Diagram.

3.9. Persistent Data Management

Database design is the process of producing a detailed data model of a database. This logical data
model contains all the needed logical and physical design choices and physical storage parameters
needed to generate a design in a Data Definition Language, which can then be used to create a
database. A fully attributed data model contains detailed attributes for each entity. The term
database design can be used to describe many different parts of the design of an overall database
system. Principally, and most correctly, it can be thought of as the logical design of the base data
structures used to store the data.

40 | P a g e
Figure 24 Database Design diagram.

3.10. Security Technique

Ensuring the security of the online voting management system is one of utmost importance, to
achieve this; our team considered and addressed several security issues in the system. These
include protecting against unauthorized access, ensuring data privacy and confidentiality,
preventing manipulation of data or system, ensuring secure communication between user and
server, and implementing measures to prevent fraudulent activities. When a voter registered to cast
his/her vote, IDN is given to the voter for authentication. The registered voter can login to the
system with the help of the IDN code. (5) Then, the system shows the check box, names and party
symbol of the candidates. The voter checked the check box corresponding to each candidate and
submits his/her vote to the system. And we will use encryption method in order to secure the use
41 | P a g e
data when registering and accessing the data from the database. The suspected problem is man-in-
the-middle attack. Before the data reaching at the destination, it can be trapped and modified. For
the case of the channel between the web browser and the web server, SSL technology is viable
solution. so we will try to use SSL technology to secure the data. (6)

42 | P a g e
Reference
1. home. election in ethiopia. [Online]
https://getliner.com/workspace?ref=serp&q=election%20in%20ethiopia.

2. 6) Joseph R., Alen E., Dermot C., Fintan F.,. the KOA Remote Voting System, Available from:
http://secure.ucd.ie/documents/submitted/KOAEVT06.pdf . (Accessed October 2014/2015).

3. Ethiopian Elections: Past and Future. [Online] https://www.jstor.org/stable/41757576.

4. 30th meeting of the working Group on 28th August 2001 in Berlin, Data Protection and
Online Voting in Parliament and Other governmental elections, Available
from:http:www.theregisterBerlin.co.uk. Data Protection and Online Voting in Parliament and
Other governmental elections. 30th meeting of the working Group on 28th August 2001 in Berlin,.
[Online] http:www.theregisterBerlin.co.uk.

5. 2) Electricnews.net, All internets voting is Insecure, Available

from:http:www.theregister.co.uk/2004/01/23 ((Accessed September 2014/2015). net, All
internets voting is Insecure. Electricnews. [Online] September ( 2014/2015).
:http:www.theregister.co.uk.

6. —. Electricnews.net, All internets voting is Insecure,. http:www.theregister.co.uk/2004/01/23

((Accessed September 2018/2019. [Online]

7. D., Doug. 1) How Electronic Voting Impacts the Trustworthiness of Elections, AvailableFrom: .
WWW.OpEdNews.com (AccessedSeptember2014/2015). [Online]

8. 3) StevenM., ABetterBallotBox,.
Availablefrom:http://www.notablesoftware.com/papers/1002evot.pdf (accessed 15 January 2007).
[Online]

9. 4) Pipaa N., Evoting as a magic Ballot,. Available from:

http://ksghome.harvard.edu((Accessed October 2014/2015). [Online]

10. [Online]

11. 5), Available from: (accessed 26 February 2007). Every One Counts PL. A Virtual Private
Network for Internet Voting. [Online] (accessed 26 February 2007).
http://www.everyonecounts.com .

43 | P a g e