Best Election System

WEB BASED ELECTION SYSTEM FOR ETHIOPIAN ELECTION
BOARD
A PROJECT REPORT
Submitted by
1. NIGUSU ADEME TEE/984/06
2. HABTAMU SIMACHEW TEE/968/06
3. MELESE MISGANAWTEE/1113/06
4. WEYENSHET MELESE TEE/994/06
5. ABEBE ATINAF TEE/1138/06
6. BIRHAN BENAYEW TEE/960/06
in partial fulfilment for the award of the degree of
BACHELOR OF SCIENCE IN INFORMATION TECHNOLOGY
Under the guidance of
LAMESGINEW .A
--------------------------------------
ADVISOR SIGNATURE
DEPARTMENT OF INFORMATION TECHNOLOGY
COLLEGE OF TECHNOLOGY
DEBRE MARKOS UNIVERSITY
DEBRE MARKOS
JUNE 2009 E.C
1
Table of Contents
List of Table.....................................................................................................................................................iii
List of Figures..................................................................................................................................................iv
List of Acronyms..............................................................................................................................................v
CHAPTER ONE...............................................................................................................................................1
1. INTRODUCTION....................................................................................................................................1
1.1. BACKGROUND OF THE STUDY.................................................................................................1
1.2. STATEMENT OF THE PROBLEM................................................................................................2
1.3. OBJECTIVE OF THE PROJECT.....................................................................................................3
1.3.1. General Objective.....................................................................................................................3
1.3.2. Specific Objectives...................................................................................................................3
1.4. SCOPE OF THE PROJECT.............................................................................................................3
1.5. SIGNIFICANCE OF THE PROJECT..............................................................................................4
1.6. SYSTEM REQUIREMENTS...........................................................................................................6
1.6.1. Hardware Requirement.............................................................................................................6
1.6.2. Software Requirement...............................................................................................................6
1.7. DATA COLLECTION METHODOLOGY......................................................................................7
1.7.1. Interviews.................................................................................................................................7
1.7.2. Document Analysis...................................................................................................................7
1.8. FEASIBILITY STUDY....................................................................................................................7
1.8.1. Economic Feasibility.................................................................................................................7
1.8.2. Technical Feasibility.................................................................................................................8
1.8.3. Operational Feasibility..............................................................................................................8
1.8.4. Schedule Feasibility..................................................................................................................8
1.8.5. Legal Feasibility........................................................................................................................8
CHAPTER TWO..............................................................................................................................................9
2. SYSTEM ANALYSIS..............................................................................................................................9
2.1. Over View of Existing Problem........................................................................................................9
2.2. Problems of the Existing System Using Pieces Framework............................................................10
2.3. SYSTEM REQUIREMENT SPECIFICATION.............................................................................12
2.3.1. Functional Requirements........................................................................................................12
i
WEB BASED ELECTION SYSTEM FOR ETHIOPIAN ELECTION BOARD
2.3.2. Non Functional Requirements.................................................................................................13

F. Error handling issue........................................................................................................................15
2.3.3. System Business Rules............................................................................................................16
2.4. SYSTEM REQUIREMENT ANALYSIS.......................................................................................16
2.3.1. Actor and Use Case Identification................................................................................................16
1.3.2. Sequence Diagram..................................................................................................................39
1.3.3. Activity Diagram....................................................................................................................46
1.3.4. Analysis Class Diagram..........................................................................................................50
CHAPTER THREE........................................................................................................................................52
3. SYSTEM DESIGN.....................................................................................................................................52
3.1. Design Class Diagram.........................................................................................................................52
b. Database Design /Physical Data Model..............................................................................................53
3.3. User Interface Design.....................................................................................................................60
3.4. System Architecture (Deployment Diagram)..................................................................................60
Reference........................................................................................................................................................61
List of Table
Table 2.1Use Case Identification....................................................................................................................19
Table 2. 2: Login use case description............................................................................................................22
Table 2.3: Use case Registrations of Election committee description.............................................................22
Table 2. 4: Use case Post information description...........................................................................................23
Table 2.5: Use case Approve candidate description........................................................................................24
Table 2.6: Use case Generate reports description............................................................................................25
Table 2.7: Use case cast vote description........................................................................................................25
Table 2.8: Use case Search information description.......................................................................................26
Table 2.9: Use case View result description...................................................................................................27
Table 2.10: Use case Post nominated election committee description............................................................28
Table 2. 11: Use case candidate registration description.................................................................................29
Table 2.12: Use case voter’s registration description......................................................................................29
Table 2.13: Use case view candidate description............................................................................................30
Table 2.14: Use case updates user profile description.....................................................................................31
Table 2. 15: Use case create privilege description..........................................................................................32
Table 2.16 Use case create registrar description.............................................................................................32
Table 2.17: Use case data backup description.................................................................................................33
Table 2.18 Use case create polling station description....................................................................................34
Table 2.19 Use case Post announcement description......................................................................................35
Table 2.20: Use case maintain policy description...........................................................................................36
Table 2.21: Use case view information description........................................................................................37
Table 2. 22: Use case feedback description....................................................................................................38
List of Figures
Figure 2.1: use case diagram..........................................................................................................................21
Figure 2.2: Sequences diagram of login into the system.................................................................................39
Figure 2.3 Sequences diagram of Generate reports.........................................................................................40
Figure 2. 4 Sequences diagram of register candidate......................................................................................41
Figure 2.5 Sequences diagram of search information......................................................................................42
Figure 2.6 Sequences diagram of registration’s voter.....................................................................................43
Figure 2.7 Sequences diagram of cast vote.....................................................................................................44
Figure 2. 8 Sequences diagram of data backup...............................................................................................44
Figure 2.9 Sequences diagram of post announcement.....................................................................................45
Figure 2.10 Activity diagram of login to the system.......................................................................................46
Figure 2.11 Activity diagram of Generate reports...........................................................................................47
Figure 2. 12 Activity diagram of Search information......................................................................................48
Figure 2.13 Activity diagram of cast vote.......................................................................................................48
Figure 2.14 Activity diagram of registration of voters....................................................................................49
Figure 2.15 Activity diagram of creating privilege.........................................................................................49
Figure 2.16 Activity diagram of view information..........................................................................................50
Figure 2.17 class diagram...............................................................................................................................51
Figure 3.18 Design Class Diagram.................................................................................................................53
Figure 3.19 Database Design..........................................................................................................................57
Figure 3.20 Home page screen shut UI...........................................................................................................60
Figure 3.21 Deployment Diagram...................................................................................................................60
List of Acronyms
 RAM------------ Random Access Memory
 HTML----------Hypertext markup language
 MYSQL-------My structural query language
 EC--------------Election committee
 DM--------------Debre markos
 CPU------------central Processing unit
 CSS-------------cascading style sheet
 UML-------------unified modeling language
 OS---------------operating system
 VPIN-------------voter personal identification number
 UC-----------------use case
 HPR--------------house of people representative
 (SSN)----------- Social Security Number
 ICT----------------information communication technology
CHAPTER ONE
1. INTRODUCTION
1.1. BACKGROUND OF THE STUDY

Nowadays, the application of ICT is introduced at several domains of fields. Its’ multidimensional
benefits is becoming more visible from time to times. The economic benefit gained from the
technology is the most significant one. Furthermore, it helps to increase the qualities of the work,
reduces the complexities of tasks, keeps the security of data in most favorable condition, makes data
transfer more easy, and others. ICT role is wide, starting from low level systems to high level
business and governmental applications. The business applications are used by business people to
manage the business process; e-commerce can be taken as one example that shows the application
of ICT to the business community. Similarly, ICT can play its role for governmental applications.
Election is one of the tasks of the government that can be benefited from ICT. Electronic voting is
common in several countries, but not practiced in Ethiopia still now. This project initiated to start
an initial work on e-voting for Ethiopia that can be extended in the future. The project does not have
a plan to totally replacing the existed paper based voting methods. Rather, for supplementing the
existed paper based vote casting with ICT. There are countries which are using both the paper based
and electronic based vote casting system for one election process. For instance, Switzerland has
managed its voting system both by electronic and with the manual method at one time. One of the
challenges for e-voting is identity identification issue. In the current voting system of Ethiopia,
identity card is used for identifying the individuals and ink for separating voters who have given
their vote. It is possible to use this traditional individuals’ identification mechanism to e-voting as
well. But the methodology has problems; it didn’t address the problems very well that are raised
related with uniqueness identification. For example, it has lesser capability to protect voters from
registering at more than one place. This system proposes alternative technology that can minimize
uniqueness identification problems seen on the current voting system [1, 4]. Many countries have
automated systems that can help to uniquely identify its citizens. For instance, USA uses Social
Security Number (SSN) for this purpose. In Ethiopia, there is no such strong uniqueness
identification system. This project considers the case by assuming that there is automated system
that facilitates citizens’ identification task, which is an external system that communicates with this
system through the network. If this methodology is employed, it can minimize double voters
1
registration problem, reduces age related problem for electors, protects those which are not eligible
to cast a vote due to court related cases, identifies localities of individuals very well, etc. The rest of
the document is organized as follows. In chapter-2, system analysis has been discussed. A system
design is discussed in chapter-3. In chapter-4, implementation of the proposed system will be
discussed. Testing of the developed system is shown in chapter-5. Finally, summary and conclusion
of the document are elaborated in chapter-6.
1.2. STATEMENT OF THE PROBLEM

The existing system of the Debre Marko’s city used manual election system and distributed
information about election process by manual system such as write a collection of sheets paper and to
post on to different place on boards and on block of walls. The existing system is used a manual
registration of candidate, election committee and voters(people) or recording and traditional counting
(i.e. the main tools of selecting, recording the peoples vote by using pen, pencil, with hard paper,
cards, shelf and so on).
The existence system has a number of problems in the working procedure for the city and peoples.
These problems are: -
 Lack of security: Poor security system because one can get easily the document and change what-
ever they want, loss of information etc. The manual election systems may not secure. For example
when election process occur, the peoples who gives voting may be forced by election committees
that gives service in station.
 Time and resource consumption: by using such manual election system time and materials are
wasted. For example to record voters information and to give candidate cards the election board need
to organize the committee that implement these mission, the committees who give these service until
the elections are completed they loss their time. And the Election board pays out money to these
committees in order to succeed the election successfully.
 It is difficult to keep our interest: All candidates’ information is not placed separately.
 Lack of information:The manual information distribution system most of the peoples could not have
the habit of reading notice or accessing information from board. During the election time there is
crowded of voters in order to vote they must be waiting and spent their time in order to give their
voice. It may also inform some of information of candidate to peoples by themselves.
 The other shortcoming of using manual system file lost, then after the peoples go back and ask
information about him or her following process about how to vote.
 Requires high man power to handle the manual system, the need to print ballot paper is an expensive,
inflexible, environmentally hostile process, visual impairments and also last minute changes to the
voter register are difficult to accommodate among others. And counting is done manually, hence it
consumes a lot of time and there can be possibility of invalid votes. When we see the problems to the
voter side, there is low rate of response from voters due to lack of time or motivation in having to
complete forms and make the effort since this process has a queue and lake of keeping their secret.
All these makes election time and resource consuming, tedious and inconvenient task.
1.3. OBJECTIVE OF THE PROJECT
1.3.1. General Objective

The main objective of the project is developingautomated electronic election system in the case
of Debre Markos City.
1.3.2. Specific Objectives

The specific objectives of the project include:-
 To validate the system to ensure only legible voters are allowed to vote.
 To Eliminating the chance of vote’s rejection.
 To develop friendly user interface system to do web based election system
 To implement standard advance encryption system security algorithms that can keep the
confidentiality of the data at rest as well as at communication lines.
 Registration of the voters
 The system displays the result of the vote and the winner after vote
 Registration of the candidates.
1.4. SCOPE OF THE PROJECT

The scope of this project is developing e-voting system for Ethiopia, specifically to Debre Marko’s
City that can be extended in the future. There are different kinds of electronic voting system in the
world, but this project targets to do web based e-voting system. The system contains modules that
can handle voters’ and candidates’ registration system, including vote counting module.Our study
contains the following major activities:
1. Pre Voting
- Register candidates based on qualification and provide complete profiles of them.
- Setting starting and ending date for both registration and voting.
- Generating secrete keys and distribute to voters and candidates.
2. Voting(voting process itself)
- Create account.
- Secure login procedure.
- Registrations of voters.
- Review complete candidates profiles.
- Give votes to the alleged candidates.
3. Post –Voting
- Counting votes.
- Generating the final result.
- Reset the election. Allow to conduct election again.
1.5. SIGNIFICANCE OF THE PROJECT

The main purpose of this study is to increase the turnout of votes. For this purpose we have to View
all the aspects responsible for low turnout. Some peoples hesitate to vote due to weather conditions in
different areas during the election, most of the time youngest peoples have no attraction to cast the vote.
People who are outside of their town/city don’t want to come to their area for just casting the votes due to the
expenses and trouble of transportation. Same situation is also for those who are on duty during the election,
they don’t have any interest to cast their Vote during job or they don’t have facility to submit their vote.
A second purpose is to make it more difficult to commit fraud and cheating during an election. In a
manual system, it takes time to register vote to select their representatives in correct way. By
creating an online database covering the entry it will be possible to eliminate the double casting of
votes. Peoples in DM city are well aware of available online services and, from the last few years
the Use of internet has increased. Peoples have developed interest in using internet for various
purposes. After looking above factors, the decision for online voting is more neutral than
before. The expenditure of an election will be decreased and it will cover peoples of all
within the city . It will be a facility for the people who have different problems such as mentioned
earlier. When this project finished it will be used for election commission or administrators, voters,
candidates. There are many benefits. Among these, there will be Reducing of manpower needed to
handle manual system because of this cost and time will be reduced. Voters will vote remotely via
wherever they are whenever they like. There will be valid votes and error free counting during
election process. Since it will be used in any place, it will motivate all citizens to participate in
election and make the service fast, easy and less time consuming and it will reduce the paper work
and make the election less tedious. This project will also support multi-user environment and will
create better environment for voting. The following are Significances of the system:-
 Reducing the chances of error occurrence, while counting votes.

 Minimizing time being consumed.
 Increase the security of votes.
 Easy management of records.
 Make searching of desire candidate record easy.
 The polling is online by being wherever.
 To know easily whether the voter is registered or not.
 High and reliable security can be achieved.
 Incomplete and incorrect data about voters or candidates cannot be registered.
 It supports data validation
 Reduces cost by minimizing the number of peoples participated in the election process.
 It contributes some to growth of democracy in Ethiopia too much.
 Voters can learn details about the candidates and they will be interacting with each other
before the Election Day.
 Small response time and many services
 Easy and fast voting process management.
 It saves a lot of time and money wasted by traditional paper ballots.
 It facilitates the vote counting processes and generates more accurate results within a short
time; thanks to the computer technology.
 It speedup the registration process because more than one voter can register at one time.
 It reduces vote or data loss because of recovery or backup.
 To make voters could give their selection at the same time, so that minimize work load
and increase voter’s participations.
 To show application of technology for modern election systems, and propose the system to
implement throughout the country.
1.6. SYSTEM REQUIREMENTS

1.6.1. Hardware Requirement
Different requirements and materials are required to implement the new system. Includes:-
 Personal computer: -:2GB RAM, 120GBHDD,Core i3 2.2 GHzCPU.
1.6.2. Software Requirement
This project will be developed by using different programming and database tools which are easy to
understand and suit to implement and create user friendly web application.
 PHP programming language:
Front –End: web based (PHP)
Reason:
 It is Faster compiler
 Allows database integration with wide variety of application
 It is the latest web based
 New package & Deployment Wizard and additional internet capabilities
 MySQL Database: -MYSQL is an open source relational database management system. It
is based on the structure query language (SQL), which is used for adding, removing, and
modifying information in the database. Standard SQL commands, such as ADD, DROP,
INSERT, and UPDATE can be used with MySQL.
Back-End: MYSQL
Reason:
 It allows easy to create database connection to PHP.
 It provides different security mechanisms.
 It is powerful of any database querying.

 Microsoft word :- it is used for writing ,edit ,delete, and insert different texts and also write
the documentation part of the project:
 CSS (cascaded style sheets) for presentation: - uses for designing different web styles and
also change the styles easily.
 System development tools
 Web browsers: Mozilla Firefox, Google chrome, Opera and Internet Explorer
 WampServer: this software assists to create database or back end of the system, to run and
test system application
 Editor: - Code lobster editor, Notepad++ and XML editor used to write codes.
 Edraw Max:-For drawing different UML diagrams.
 Browser like chrome and Firefox :- used to display webpages of the project
 Anti-Virus Software: - used to keep secure, scan, fix Flash Disk and to prevent data
destruction and corruption.
 Window 7 OS:-used to access, manipulate, update and manage files easily by searching on
the start menu.
1.7. DATA COLLECTION METHODOLOGY

To conduct this project, primary data such as interview, observation and secondary data such as
document analysis and internet will be used.
1.7.1. Interviews
Information’s are gathered about the existing system from peoples by interviewing. This technique
is the way that uses to directly interface individually users like peoples to get what they need to get
from the system.
1.7.2. Document Analysis

 Relevant documents and techniques those are helpful to our project from internet.
 Understanding the business rule
 Business form-used for many functions example, candidate and voter registration,
vote, and report.
 Study the procedures manual and written documents on Ethiopian Election Board, to
obtain information on how the existing system works [1].
1.8. FEASIBILITY STUDY
1.8.1. Economic Feasibility

Economically the system is more functional in reducing costs of the organization. There will be less
requirement of manpower for registration and no requirement of manpower for casting vote because
it helps to communicate online rather than attending on the place. The project is economically
feasible since we are getting sufficient free software required for the project from Internet and
others materials are covered by the group members.
1.8.2. Technical Feasibility

Technically, the system will be powerful to be applied by low skilled users as much as possible.
There is no need for the developer involvement in almost all implementation of the entire system.
1.8.3. Operational Feasibility

Operationally the system will become easily operable and quick enough in producing the desired
deliverables. As it is web based, the operational level sometimes based on the internetworking
devices and the number of users at a time this helps to increase the operational level of the system.
The new system is operationally feasible because:-
 The new system fits with the existing system.
 Satisfy the user needs or requirements
 Provides the end users and managers with timely, accurate, reliable, flexible and usefully
formatted information.
 Provides adequate through put and response time.
 The system offers adequate control to protect against fraud and embezzlement (misuse) to
guarantee the accuracy and security of the data and information.
1.8.4. Schedule Feasibility

Time evaluation is the most important consideration in the development of project. The time schedule
required for the developed of this project is very important since more development time effect
machine time, cost and cause delay in the development of other systems. A reliable Online voting
systemcan be developed in the considerable amount of time
1.8.5. Legal Feasibility

Legally the project is fully feasible because it never contradicts with legal and criminal laws of the
country. The project that will contradict with the governmental rules regulations will be
automatically rejected. When will develop our project it will never contradict with the government.
Therefore it will not have any negative impact on the government and legal laws.
CHAPTER TWO
2. SYSTEM ANALYSIS
2.1. Over View of Existing Problem

In most cases, computer programs are developed for handling daily routine tasks. But voting process
is not an everyday task. In Debre Markos city, it is conducted within every five year. However, the
volume of the work is massive and wide. The current system used in Debre Markos city for this
purpose is manual starting from the registration process till the vote counting stage. It is complex and
error prone task. The material cost required for managing the whole vote process is also high. The
time for declaring the final result will also be beyond the schedules. Moreover, it seeks strong
security system. By considering the complexity of the vote management system, many countries
have been automating their voting process, and have gained successful result. Therefore,
implementing the state of art technology for Debre Markos city that can reduce the major problems
seen on the paper based vote casting system is necessary. The technology is tried in many countries
and brings significant changes. And this project targets to do an initial work on the area that can be
extended in the future. The existing system of the Debre Markos city election commission used
manual election system and distributed information about election process by manual system such as
write a collection of sheets paper and to post on to different place on boards and on block of walls.
The existing system is used a manual registration of candidate, election committee and
voters(people) or recording and traditional counting (i.e. the main tools of selecting, recording the
peoples vote by using pen, pencil, with hard paper, cards, shelf and so on).The problems of the
existing manual system of voting [1, 6] include the following:-
1. Expensive and Time consuming:The process of collecting data and entering thisdata into the
database takes too much time and is expensive to conduct, for example, time and money is spent in
printing data capture forms, in preparing registration stations together with human resources, and there
after advertising the days set for registration process including sensitizing voters on the need for
registration, as well as time spent on entering this data to the database. The paradigm shift from Hand
based Polling System to Paper based Polling System is cause due to population growth whereas, now,
time and safety are so important that it has driven new paradigm shift from Paper to electronic.
2. Too much paper work: The process involves too much paper work and paper storage which is
difficult as papers become bulky with the population size.

3. Errors during data entry: Errors are part of all human beings; it is very unlikely for humans to
be 100 percent efficient in data entry.
4. Loss of registration forms: Some times, registration forms get lost after being filled in with
voters’ details, in most cases these are difficult to follow-up and therefore many remain
unregistered even though they are voting age nationals and interested in exercising their right to
vote.
5. Short time provided to view the voter register: This is a very big problem since not all people
have free time during the given short period of time to check and update the voter register.
6. Lack of security: Poor security system because one can get easily the document and change
whatever they want, loss of information etc. The manual election systems may not secure. For
example when election process occur, the peoples who gives voting may be forced by election
committees that gives service in station.
7. Paper-based voting systems originated as a system where votes are cast and counted by hand, in
this case faults are highly generatedsuch as incorrect vote counting.
2.2. Problems of the Existing System Using Pieces Framework

Problems are undesirable situation that prevent the organization from fully achieving its purpose,
goals, and/or objective.
We classified the problems according to PIECES framework

P the need to improve performance
I theneed to improve information (data)
E the need to improve economics, control, costs
C the need to improve control or security
E the need to improve efficiency of people and process
S the need to improve servicesto voters, candidates and election officers
Performance
 Presiding Officers count the ballot papers, but human counting is usually has chances of
errors; which means an ultimate disaster ahead in the process of Democracy.
 Because the system is not web based, the full information about candidates is not arriv-
ing to individual voters at the right time, in the right place and with right format.
 Many of the votes are not counted due to slight mistake by the voter, e.g. Voter left
Thumb impression in between two check boxes etc.
 A small mistake can cause of rejection of vote.
 Incorrect casted vote will lose.
Information
 Lack of necessary information because data is not captured in time to be useful.
 Because the current system cannot enhance the data validation in a meaningful manner,
voters often get incomplete and incorrect data.
 Problem for duty staff to search the record of a particular voter.
 Difficult to generate report timely
 Lack of information cause problems in filling the forms.
Economics
 Telephone cost (from one polling station to another polling station).

 A huge number of ballot papers are printed and distributed on polling stations and this
cost thousands.
 Manual voting system requires many employees to participate and this is too costly.
Control or Security
 The system offers inadequate controls to protect against fraud and embezzlement (mis-
use) to guarantee the accuracy and security of the data and information. E.g. Storage of
data that requested to store voters and candidates vote is not secured since it is placed in
manual form. There is no check and balance on the timings of casting votes as some in-
fluential Candidates let their own people cast vote even after the time is over; as it is nor-
mally From 2 AM till 11 PM. So this means people go on voting even after 11 PM.
 Problem for election board to manage (control) the records.
 Unauthorized vote casting.
 Appointment of polling stations is problematic. Polling stations can help in corruption
during the polling, so many of the candidates try to appoint their own staff at their
polling stations and thus the authorities are approached by such candidates. Increasing
number of polling stations raises the number of staff required. Polling station is ap-
pointed away from the area where they belong to, thus many of the people could not cast
their vote.
Efficiency
 Presiding Officers count the ballot papers, but human counting is usually slow.
 Validating the Voter ID in time of registration, vote ID in time of vote and the votes in
time of vote counting takes much time.
 The procedure of ratification or approving the required number of candidates from the
registered is boring, because the requesting process passes through different evaluation
levels.
 Time is very important factor for measuring the efficiency of the system. The current
system requires a lot of time for vote counting process and registering voters.
Service
 Communication made between voters, candidates and election officer is not modernized.
 Sometimes voters and candidate have no clear understanding about the counting process
made.
 Lack of information sharing accordingly, because they have no system connection
among polling stations.
2.3. SYSTEM REQUIREMENT SPECIFICATION
2.3.1. Functional Requirements

A functional requirement is a requirement that the system must perform. In addition to the function
that must be performed, a functional requirement also implies something about the need for system
memory to support the function.The following are functional requirement in the system.
 Registration of the voters.

 Registration of the candidates.
 The system calculates votes for each candidate.
 Secure storage and retrieval of voters detail from the voter database.
 Election committee can register and post candidate information.
 Registration of the Voter depends upon the information that are available in the population
database System gives voter identity (VPIN) to identify each voter during election.
 Voter can caste vote after login and entering their voter VPIN
 The system displays the result of the vote and the winner after vote
 The system must provide voters with accurate data
 It must adhere to government requirements
 The system should supply standard reports for decision making
 The system allow voting administrators to make updates to the voter information database
 The systemset time for Registration, voting and viewing election result etc.
2.3.2. Non Functional Requirements

Non-functional requirements are requirements that are not specifically concerned with the
functionality of a system. They normally place restrictions on the product being developed and the
development process. Non-functional requirements may be regarded as parameters of functionality
in that they determine how quickly, accurately, reliably, securely, etc., functions must operate.
Some of the E-Voting System’s non-functional requirements are as follows:
 Response and net processing time must be acceptable by user and by application.
 The system should be allow adding more voters to allow a greater connectivity rate
 The system should provide information to inform users of system functionality and any
change to the system
 The system should provide friendly graphical Interface to ensure ease of use when end users
utilize system functionality.
 The system must verify responsible users username and passwords
 The system must provide standard error checking
 The system must provide data integrity checks to ensure data remains consistent and updated
In general non-functional requirement describes constrains for implementing the project. Some of
them are; the central server have to be provided at secured area, the system must be maintainable
and expandable, the network infrastructure have to be private network, client machines at each of
the polling stations must be installed. In each of the polling stations there should be technically
supporting people. The voter should have also basic computer skills and training should be provided
to the voters on the demo version of the voting application. The input value which is used to
generate the encryption key must be provided from the election officials, and needs to be kept
securely, and others. Outlined below are some of the expectations of the system when
implemented:-
A. Reliability
The system should only be available during election time. Also in the occurrence of any
major system malfunctioning, the system should be available in 1 to 2 working days, so that
business process is not severely affected.
 The electronic voting system software will be available for voter use only during normal
poll hours. During this time it shall be operational for as long as is possible.
 Administrators will have 24 hour access to the system.
 The online voting system (e-vote) shall be robust enough to have a high degree of fault
tolerance. For example if there is an invalid entry, the system should not crash and shall
identify the invalid input and produce a suitable error message.
 The online voting system shall impose a successful voter determination strategy in order to
determine a successful voter in order to avoid multi voting.
 The online voting system shall be available during the voting hours of the voting day.
 Failures and others natural catastrophes should rollback the database to their most recent
valid state.
B. Security
A top priority requirement for the proposed system is to have highly efficient and secure
features, to safe guard the integrity of the voting system. With the system recording confidential
information, users (voters and candidates) other than Election officers can only access part of
the system that is relevant to them. In order to make the system secure, four forms of security
measures are used where engineered into the system to safeguard the data flow within
the system and the information being stored in the database. The four measures to be used in
addition to the system’s login access facility are:-
System Access Attempts Log:- This security measure would enable the system to count the number
of attempts a user tries to log into system with a wrong password. The system should lock
the user out, if the attempted tries exceeds a certain number. This measure has been used to
prevent password guessing.
Session Control: - The system is with session controlled way to permit URL based system access.
Password Encryption: -This security measure would be used to encrypt password entered into
the system through the use of an AES/MD5encryption algorithm, thus in the case of the
database being compromised, the password stored would be useless.
C. Performance
 The software will only accommodate one user at a time. No simultaneous use of the
system by multiple voters, administrators, or a combination thereof shall be allowed.
 Is hint of the responsiveness of a system to execute specific actions in a given time
interval. Our system is better component design to get better performance at peak time
the system should accommodate all Debre Marko’s city who are already register in voter
data base .(how many users can access your system simultaneously).
 Response time of e-vote should be less than 5 second most of the time by the use of
latest browser, high speed processor ,high speed server based network etc. response
time refers to the time that the user should wait for before getting a response from a
system after querying it.
 There might be many users accessing to the web server simultaneously. As an online e-
voting tool performance shouldn’t be affected much and response time for submitted
page should be less than a minute.
D. Usability
 A voter may only cast a vote if they are eligible to vote.
 A voter may only cast one (1) vote per election.
 Users should be understood the menu and options provided by the system.
 The system shall provide an easy to use interface so that the users do not strain to
interact with the system.
 Any notification or error messages generated by the system shall be clear, policy
and free of jargon.
 The interface should be initiative and easily navigable
E. Availability and accessibility
 The system should be up and running whenever needed by the enhancements of
facility such as generator, which is used to increase availability when the power is
goes out.
F. Error handling issue

This system handles error done by the user giving error message when the user enters wrong
inputs. In addition, the system provides error handling mechanism on the ways system interacts
with database and input accepter fields. To reduce input fault, the system enable the user to
confirm that details are correct before creation, process or modification occurs. Respond to error
inputs by asking the user to reenter data in the correct format.
G. Interoperability
The system should forward compatibility by the use of integrated or open source software.
2.3.3. System Business Rules

A business rule is a rule that defines or constrains some aspect of election and always resolves to
either true or false. Election rules are intended to assert election structure or to control or influence
the behavior of the election [1, 5].
BR#1: The candidates and voters must be Ethiopian citizen.
BR #2: The candidates should be members of parties.
BR #3: The candidate must pass the electoral procedures.
BR#4: Candidates must be at least approved with 7 signatures from board.
BR#5: voter age has to be 18
BR#6: candidate age has to be 22
BR#7: voter has to live in the poll stationarea for 6 month
2.4. SYSTEM REQUIREMENT ANALYSIS
2.3.1. Actor and Use Case Identification

2.3.1.1. Actors
Actors represent system users. They help delimit the system and give a clear picture of what the
system should do. An actor is someone or something that:
 Interacts with or uses the system.
 Provides input to & receive information from the system.
 Is external to the system and has no control over the use cases.
The followings are the actors involved in the system.
 Administrator:-Administrator utilizing the system functionality.Each administrator will have a

unique user name and passwords to log to system .The roles that are play by administrator are
listed below:
 Control system information flows.
 View onlinefeedback.
 generate the reports in case of the system
 take backup
 create privilege for appropriate user
 view log file
 Voter:-In this system peoples that participate above 18 years old. The voter is the people for
Debre Marko’stownwho interact with the system. The roles they play are listed below:
 View candidate result in election
 Cast Vote
 View post Information
 View Online Help
 View candidate result after election
 View candidate profile
 Election committee:-election committee do all task related to this election. The roles they
play are listed below:
 Review the Rules and other guiding documents for use in the elections and make recom-
mendations to the Returning Officer on any changes
 Set targets to improve diversity and participation in the whole elections process:- num-
ber and diversity of candidates standing and number diversity of voters overall
 Raise awareness of the Elections to ensure these targets are metApprove candidates.
 Manipulate Voter data: incase if there is problem for the people record in the registrar.
 Create polling station and generate the reports based on the polling stations code.
 Manipulate Candidate data: incase if one candidate leave before election.
 View candidate result.
 Play a role in regulating political party finances
 Candidate:-agent of the party or independent candidate is candidate for this election to

represent people. The roles they play are listed below:
• View result after election.
• Post information
 Registrar: - the registrar will register and update voter profile.
 Election officer: - election officer operates personal computer when the voter want to cast
their vote in the election time and give training for voters.
 Parties:-post information, propose a candidate and view the results
 Prime minister: the role of the prime minister here in voting system is that nominating the
election committee.
 HPR:The HPR approves the election committee nominated by prime minister.
2.3.1.2. Use Case
In its simplest form, a use case can be described as a specific way of using the system from a user’s
(actor’s) perspective and describes what the system does from the stand point of view. Use cases
provide a means to capture system requirements, communicate with the end users and domain ex-
perts, and test the system. Use cases are best discovered by examining the actors and defining what
the actor will be able to do with the system. Use case has been identified from the system specifica -
tion [3, 6].
 Login: - used for protecting information to do validate task by their account username and
password validation.
 Register Election committee: - Administrator record 7 members election committee.
 Create privilege: administrator give permission for appropriate users.
 Backupdata: - administratormust take data backup.
 View log file:-administrator view login file throughout the system.
 Generates Report: valid usersgenerate reports when needed.
 Post Nominatedelection committee: prime ministernominates election committee that par-
ticipates in the election as election committee.
 Approve candidate: - Election committee can approve candidate that participate in the elec-
tion as a candidate.
 Candidate’s registration: Before the vote casting process begins, the election committee
needs to register the candidates.
 Create Registrars: Before the registration process begins, the election committee has to
create the username and password of the registrars.
 Create Polling Stations: The election committee has to create the codes of the selected
polling stations before the vote casting process begins.
 Post Maintain Policy: The election committee has to postrules and regulations of election
process.
 Post announcement: Committee can post new announcements for voters in the election
process.
 Cast Vote: people can vote online anywhere at any time in the schedule When the voter
keys the correct VPIN and poll station code to the system, the system will extract the
eligible candidates on that polling station, then the voters casts the vote by keeping the
rules.
 View result: - after election is completed anyone who want to see the result able to view.
 Post information: - the valid user can post their information on the web.
 View information: - users view information from the web.
 View candidate: - the details of candidate should be seen by users.
 Check eligibility to cast a vote: When the voter registers to cast a vote, the system will
check whether the user is eligible to cast a vote or not.
 Voters Registration: After the eligible registrars are created, the registrar will register the
voters and check voter requirements.
 Search information:-find information from the system using system queries.
 Update information: -This use-case describes the process by which valid users may add, re-
move or update ballot items. trusted
 Approve election committee: The HPR approves the election committee nominated by the
prime minister.
 Give Feedback: -users forward comments on the election process.
 Logout:-after task is finished any user must logout the system.
Table 2.1Use Case Identification
No Use case Use case ID

1 Login UC-01
2 Registration’s Election committee UC-02
3 Post information UC-03
4 Approve Candidate UC-04
Generate reports UC-05
6 Cast Vote UC-06

7 Search information UC-07
8 View result UC-08
9 Post nominated Election committee UC-09
10 Candidate registration UC-10
11 Voter’s registration UC-11
12 View candidate UC-12
13 Update user profile UC-13
14 Create privilege UC-14
15 Create registrar UC-15
16 Backup data UC-16
17 Create polling station UC-17
18 Post announcement UC-18
19 Post Maintain policy UC-19
20 View information UC-20
21 Give Feedback UC-21
2.3.1.3. Use Case Diagram

A use case diagram is a graphic depiction of the interactions among the elements of a system. A use
case is a methodology used in system analysis to identify, clarify, and organize system
requirements. The use cases, which the specific roles are played by the actors within and around the
system. Now the below are our actors [3]:
Search
information
Create privilege
Post information
extend
Backup database
Send request Candid
View log file
View candidate
Generate report
Cast vote
Administrator
view result
Update
information Voter
<<Include>>
<<Include>>
Parties
<<Include>>
Give Feedback Register election

committee
Register complaint Login
Register candidate
View information Regi
Approve election
<<Include>> <<Include>>
committee
Create registrar
Register voters
Election committee Election
Create polling
station Extend
Approve candidate Check eligibility to

cast vote
Post Maintain Forecasting result HPR

policy
Post Post Nominated

announcement election committee
Prime m
22
Figure 2.1: use case diagram

2.3.1.4. Use Case Description
Table 2.2: Login use case description
Use case number UC-01
Name Login
Actor Users
Description This use case describes how to access to the e-voting system
Precondition: Users of the system should have user name and password
Basic course of action User action System response
1. The user opens the main page by 2. The system display

writing the URL website. the main home page
3. The user inputs user name and pass- 4.The system validates the ac-
word and submits count and displays the user
require information.
5.use case ends
Alternative course of A If the login name or password is invalid

action
A 4.The system displays invalid user name or password message
A 5.The user reenters the user name and password
A 6.The use case continues from step 3
Post condition The users successfully login.
Table 2.3: Use case Registrations of Election committee description

Name Registration’s Election committee
Actor administrator
Description In order to participate in the election as election committee theadministrator-
must register to the system.
Precondition: Election committees must valid users to register in to the database.
Basic course of ac- User action System response
24
tion
1. Open website if you want to 3. Check password and username and
register. return message and page.
2. Enter password and username to

5. The system check validate inputs
go registration form.
4. Password and username is valid 7. Displaysuccessfully registered mes-
sage.
fill the form correctly.
6. Click on register button.
Alternative course 1. If password and username entered by administratoris not valid return to ba-
of action sic course of action step 2 and try again.
Post condition Register election committees correctly.
Table2. 4: Use case Post information description
Name Post information

Actor Valid users
Description This explains how the userscan post their information.
Precondition: The user should be login in into the system

1. After the user login in to the system 2 The system gives response
he/she poststheir information. post successfully.
2. The valid user canpost information.
3.end use case
Alternative course of Unless you feed information right now try next time
action
Post condition Post information successfully

Table 2.5: Use case Approve candidate description

Name Approve Candidate
Actor Election committee
Description Election committee can approve candidate that participate in the election as a
candidate.
Precondition: The candidate should have filled his/her application form that specified by
Electioncommittee.

tion
2. Check if the necessary infor-
1. Election committee see applicant form mation of candidate is inserted.
registration list. 6. Successfully inserted mes-
3.Election committee selects the candidate sage display.
application form from list by their perfor-
mance
4. Post selected candidate for user
Of the system.
5. Insert selected candidate to
the system.
7. Use case ends.
Alternative course of If candidates do not full fill the criteria of the election, the EC can change
action other candidate.
Post condition Gaining of qualified candidates

Table 2.6: Use case Generate reports description

Name Generate reports
Actor Valid users
Description The userssee reports from the system
Precondition: When there is relevant information or result that should be addressed to target
users
Basic course of ac-
User action System response
tion
1. The users login to the system by 2. Check if username and password are
their username and password. correct system responded valid page.
3. If username and password are 4. If not correct display error message.
correct page is displayed.
5. Click on necessary reports from

page.
6. prepare report
7. end use case
Alternative course of If you are not able to report information right now, is better to try again.
action
Post condition Generate final Report.
Table 2.7: Use case cast vote description

Name Cast Vote
Actor Voters
Description Perform vote
Precondition: Voters must have a voter VPIN to be eligible and registered in the database.

tion 1. Voters must have user name and pass- 3. The system checks if username and
word to login in to the system. password is correct or not.
2. Enterher/his username and password.
8. You select successfully mes-
4. Voter gets his validation form from sage displayed.
the system.
5. If the username and password is cor-
rect online vote page is opened.
6. Voter see candidate and then select
only one competitor.
7. Finally click on vote button.
9. Use case ends.
Alternative course of 1 If the username and password is not correct go to step 1 basic course of ac-
action tion and login again.
2. If the voter votes more than one candidate. Then the system confirms please
vote only one candidate.
Post condition Voting process is performed.
Table 2.8: Use case Search information description

Name Search information
Actor All User
Description To access information which distributed by the users and votes from data-
base.
Precondition: The user should login in to the system and identifying the information that
you need to search.
1. User of the system wants to search 5. The system responds the re-
data from the system. quested action.
2. User of the system opens the site of 6. The system display searched data
the system. or information to the wanted per-
3. Go to search button text area write son.
information search from database.
4. Click on search button.
7. The user views searched informa-
tion.
8. Use case ends.
Alternative course of 1 If the searching word not available the system generates alternative retry
action message to the web users, the user go to step 3 basic course of action and try
again.
Post condition View the searched information correctly
Table 2.9: Use case View result description

Name View result
Actor All user
Description This describes the process of how the voters view the election results by using
the system.
Precondition: Search the result that you need to view
tion
1. The user should open the website. 4. The system respond requested ac-
2. The user can search information tion to the administrator.
they want to know. 5. The system display searched data
3. After searching necessary infor- or information.
mation click on view button. 7. System display successfully mes-
6. After getting necessary information sage.
they can view.
8. Use case end.

Alternative course of If all users can’t see the result of the election, try again and login to the sys-
action tem.
Post condition The user knows the required information.
Table 2.10: Use case Post nominated election committee description

Name Post nominated Election committee
Actor Prime minister
Description Nominate election committee for elections purpose.
Precondition: Identify the qualified individuals for election committee

tion
1. Prime minister selects members 3.Successfully Posted the announced
for committee by performance information
and status.
2. Prime minister announce/post the
selected election committee for
HPR
4. Use case ends.
Alternative course 2. If there is any complain the prime minister review’s their profile.
of action
Post condition Announce for HPR selected election committee.
Table 2. 11: Use case candidateregistration description
Use casenumber UC-10

Name Candidate registration
Description In order to participate in the election as candidate the election committee must reg-
ister to the system.
Precondition: Candidates are valid agentto register in to the database.
Basic course of User action System response

action
1. Open website if you want to register. 3. Check password and username
2. Enter password and username to go regis- and return message and page.
tration form. 6. Display successfully registered
message.
4. Password and username is valid fill the
form correctly.

7. us case ends
Alternative If the candidate is not valid agent or have note correct profile the election com-
mittee try to check candidate’s profile whether the candidate is valid or not.
course of action
Post condition Register candidate correctly.
Table 2.12: Use case voter’s registration description

Name Voter’s registration
Actor Registrar
Description In order to participate in the election as voter the registrar must register vot-
ersinto system.
Precondition: Voters are valid must register in the database.

tion
1. Open website if you want to register. 3. Check password and username and
2. Enter password and username to go return message and page.
registration form. 6. Displaysuccessfully registered mes-
4. Password and username is valid fill sage.
the form correctly.
Alternative course 3. If password and username entered by people is not valid return to basic course
of action of action step 2 and try again.
Post condition Voters Successfully registered.
Table 2.13: Use case view candidate description
Name View candidate
Actor All Users
Description The details of candidate should be seen by users.
Precondition: Users can see the candidate information.

action
1. The voter clicks view candidate 2. The system checks whether the
button. candidate registered to the system
3. The system displays the candidate or not.
details.
4. Use case ends.
Alternative course of Try again
action
Post condition Candidates successfully displayed.
Table 2.14: Use case updates user profiledescription
Name Update user profile
Actor Valid Users
Description Users can modifies or update their information
Precondition: The information should be available in the database.
Select the user data manipu- 3. The system check the user informa-
1.
lation page. tion is correctly registered or not.
2. Select the user data to be
modified.
4. The valid user performs oper-
ation.
5. Used case ends.
Alternative course of A. system check the operation
action 2. If user did not select the option.
3. The system display error message & go to step 2.
4. Use case ends
Post condition information is updated successfully
Name Create privilege
Actor Administrator
Description Administrator gives permission for appropriate users in order to perform

specific task.
Precondition: The user must be a members of administrator


action
1. Administrator wants to access valid users. 4. Check if the necessary infor-
mation of user is recorded
2.Specify valid users to give privilege
on the database.
3.Give appropriate privilege for users
5.End use case
Alternative course The system returns the admin to specify valid users.
of action
Post condition Administrator create privilege successfully
Table 2. 15: Use case create privilege description
Table 2.16 Use case create registrar description
Use case num- UC-15

ber
Name Create registrar
Description Before the registration process begins, the election committee has to create the
username and password of the registrars.
Precondition: Registrar must be fulfill the requirement of election committee
Basic course User action Basic course of action
of action
1. Election committee announce for 3. Check if the necessary informa-
people and parties to creating tion recorded in the database.
registrar. 5. The system display necessary
2. Election committee select registrar information from the database.
based on the requirement.
4. Election committee select registrar by
experience and status.
6. Election committee tells what type of

work the registrar does.
Alternative 4. If any complain make from people return to registrarprofile and check again.
course of ac-
tion
Post condition Selected registrar created successfully.
Table 2.17: Use case data backup description

Name Backup data
Actor Administrator
Description Administrator must be take data backup if the system corrupted in some case.
Precondition: The data must be exist in the database

tion
1. 3. Check if the necessary information
1. The administrator want to recorded in the database.
open the system 5. Successfully backup message display.
2. Administrator view necessary
information from the database
4.Backup important information
6.End use case
Alternative course 4. If administratoris not take backup correctly and the system of the database
of action cannot display necessary information and try again.
Post condition Administrator takes backup correctly.

Table 2.18 Use case create polling station description

Name Create polling station
Description The election committee has to create the codes of the selected polling stations
before the vote casting process begins.
Precondition: Specify the location of polling station

tion
1. Election committee wants to login the 4. Check if the polling sta-

system. tion code is registered on
2. Specify number of polling station on de- the database.
bre markos city 6. The system display suc-
3. Create polling station unique code for cessfully created polling
each polling station. station code message.
5. Register each polling station code into the
database.
7. End use case.
Alternative course If the information is invalid or incomplete at step 3

of action
1: the system displays error message.
2: The use case continues at step 4.
Post condition Creating unique polling station code
Table 2.19 Use case Post announcement description

Name Post announcement
Description The election committee can post new announcements after getting login
Precondition: Login to the system using username and password

tion
1. Look the site on the address bar of the 5. The system display suc-
browser. cessfully post new an-
2. Enter user name and password nouncements message.
3. Click on announcements menu.
4. Enters announcement details and sub-
mit the form.
6. End of use case.
Alternative course of A: If login is incomplete or mismatch at step 2 and 4.

action
A1: the system displays error message.
Post condition Can read success message of post announcement.
Table 2.20: Use case maintain policy description

Name Post Maintain policy
Description The election committee has to set the rules and regulations and also maintain
policies when necessary.
Precondition: Login to the system using username and password and check existing policies

tion
1. Election committee wants to login using 4. The system display suc-

username and password cessfully registered maintain
2. Over view the existing policies of elec- policy message.
tion system
3. Register maintained policies into the
database
5. Post maintains policy for users.
6.End use case
Alternative course Try again If the system should not successfully maintain policy.
of action
Post condition post announcement for improving policy
Table 2.21: Use case view information description

Name View information
Actor All users
Description This describes the process of how the users view the information from the
website.
Precondition: Information is available on the website

tion
1. The user wants to open the 4. The system respond requested ac-
website. tion to the administrator.
2. The user can ask information 5. The system display searched data
they want to know. or information.
3. After searching necessary in- 7. System display successfully mes-
formation click on view but- sage.
ton.
6. After getting necessary infor-
mation they can view.
8. Use case end.
Alternative course If all users can’t see available information, try again and login to the system.
of action
Post condition The users view the required information.
Table 2. 22: Use case feedback description

Name Give Feedback
Actor All Users
Description Users give comments in the election process.
Precondition: See the system performance
Basic course of ac- User action Basic course of action

tion 1. Open the system and the user evaluate the

performance of the system effectively and
efficiently.
2. send comment to the system
3. successfully send message displayed
4. End use case.
Alternative course Comments not successfully send to the system, try again and fill the feedback
of action form.
Post condition Comments are posted.
1.3.2. Sequence Diagram

A sequence diagramshows an interaction arranged in time sequence. In particular, it shows the
instances participating in the interaction by their “lifelines” and the stimuli that they arranged in
time sequence. It does not show the associations among the objects.
The following are login sequence diagram
Figure 2.2: Sequences diagram of login into the system

The following are Generate Reports sequence diagram
Figure 2.3Sequences diagram of Generate reports

The following are Registrations of candidate sequence diagram
Figure 2. 4Sequences diagram of register candidate

The following are Search Information sequence diagram
Figure 2.5Sequences diagram of search information

The following are Registrations of voter sequence diagram
Figure 2.6Sequences diagram of registration’s voter

The following are Cast Vote sequence diagram
Figure 2.7Sequences diagram of cast vote
The following are Data backupsequence diagram
Figure 2. 8Sequences diagram of data backup

The following are view result sequence diagram
Figure 2.9Sequences diagram of post announcement

1.3.3. Activity Diagram

An activity diagram is a variation of a state machine in which the states represent the performance
of actions or sub activities and the transitions are triggered by the completion of the actions or sub
activities. It represents a state machine of a procedure itself [3, 6].
The following are login activity diagram
Figure 2.10Activity diagram of login to the system

The following are generate report activity diagram
Figure 2.11Activity diagram of Generate reports

Figure 2. 12Activity diagram of Search information
Figure 2.13Activity diagram of cast vote

Figure 2.14Activity diagram of registration of voters
Figure 2.15Activity diagram of creating privilege

Figure 2.16Activity diagram of view information
1.3.4. Analysis Class Diagram

Class diagrams are refined by adding relationships between classes, attributes and methods
representing how objects of the static view are used to realize use cases in sequence diagrams.
Identify classes, attributes of each class, and operations of each class
Figure 2.17class diagram
53
CHAPTER THREE
3. SYSTEM DESIGN
3.1. Design Class Diagram
54
Voter's
Design Class Diagram
Can see Parties
-VPIN: Varchar(10)
-VFname varchar(50) Candidate's -Pname :varchar(50)
-VLname varchar(50) -CPIN:varchar(10) -Psymbol :varchar(20)
-Sex: Varchar(30) +CFname:varchar(50)
*
-Age: Varchar(30) Cast vote +CLname:varchar(50) +login( )
1 1
+CRD:date +post informarion( ) *
-Adress: Varchar(15) -CPIN:varchar(10) has +Status:varchar(15) 1 +search info()
can 1
-VPSN:
-VRD date
Varchar(10) 1 cast 1 -VPIN:varchar(10)
+TimeStamp:varchar(12)
1 * +party_symbol
Name
1
+view result()
+Login()
1 has + Login() +submite vote( ) + view result() c
+View result()
User account's +cancel vote( ) +post info() Election officer
-cast vote()
+View candidate() *
* +send feedback()
-cast vote()
+Name:string(15) o
-username:varchar(50) +View announcement() +search info()
+adress:string(20) n
-password:varchar(50) +search info() *
-Role: varchar(50) +give feedback() logical relation
Administrator
+view result()
t
-AFname varchar(50)
schedule
1
-ALname varchar(50) 1 +search info() r
+start date Log file -address varchar(24) o
+create account() +end date
set schedule updates
+Login()
l
setschedule() 1 check validation() +viewlogfile() Add & Manage
+backup() update 1
1 +update info ()
1
1system -give privileg() Election Committee
+generate report() 1
display +reg electionResult
committee() +login( )
+check eligibility()
+date +post announce( )
+setschedule() +party_name 1 +view vote result( )
can register +create registrar()
manage +display result()
<<publish>> +post maintan policy()
1 1
can see +approve candidate()
1 Registrar Approve +create pollistation ()
HPR +generate report()
-RFname varchar(50)
+view candidate()
-RLname varchar(50) Name 1 1 Prime minister
-sex varchar(5) +approve election committee ( can post -Name:string(20)
-adress varchar(50) ) -Status:string(25)
-PSN:varchar(20) +view info()
-religion type(20) +view result()
+Post nominated
election committee()
+login( )
+register voters( )
+view result()
+update info()
+generate report()
This section discusses classes and their variations, including templates and instantiated classes, and the relationships between classes
association and the contents of classes (attributes and operations).Class diagrams show the static structure of the model, in particular, the
things that exist (such as classes and types), their internal structure, and their relationships to other things
Figure 3.18Design Class Diagram
b. Database Design /Physical Data Model

During physical modeling, objects such as tables and columns are created based on entities and
attributes that were defined during logical modeling. Constraints are also defined, including primary
keys, foreign keys, other unique keys, and check constraints. Views can be created from database
tables to summarize data or to simply provide the user with another perspective of certain data.
Other objects such as indexes and snapshots can also be defined during physical modeling. Physical
modeling is when all the pieces come together to complete the process of defining a database for a
business. Physical modeling is database software specific, meaning that the objects defined during
physical modeling can vary depending on the relational database software being used. For example,
most relational database systems have variations with the way data types are represented and the
way data is stored, although basic data types are conceptually the same among different
implementations. Additionally, some database systems have objects that are not available in other
database systems. To do physical database design first we must know what the class diagram seems
to be.
Tables: As shown in Fig.20, the database will consist of several tables. The tables are used for
storing the attributes of voters, candidates, polling stations, votes, election committee, administrator,
and registrar and election officer. The design is constructed to be used for the parliamentary
elections. To read the attributes of the tables easily, the following abbreviations are described as
follows.
Abbreviation Description
Voter table
VPSN Voters Polling Station Number
VPIN Voters’ Personal Identification Number
VFirstName Voters’ First Name
VLastName Voters’ Last Name
VRegDate Voters’ Registration Date
57
VSex Voter sex
VAdress Voter address
Vage Voter age
VPhoneNo Voter phone number
Candidate table
CPIN Candidates’ Personal Identification Number
CFirstName Candidates’ First Name
CLastName Candidates’ Last Name
Csex Sex of Candidate
Cage Age of Candidate
CPSN Candidates’ Polling Station Number
CRegDate Candidates’ Registration Date
Status Candidate status
Photo Photo of candidate
Polling station table
PSN Polling Station Number
PSName Polling Station Name
Administrator table
Roll_no Administrator roll number
User name Administrator username
Password Administrator password
AEmail Administrator e-mail address
Parties table
Pname Parties name
Psymbol Parties symbol
Election committee table
ECaddress The place of Election committee
Email Election committee email address
Election officer table
PSN Polling station number
EOFname Election officer first name
EOLname Election officer last name
Email Election officer email address
Registrar table
RID Registrar id
RFname Registrar first name
RLname Registrar last name
RBNO Registrar building number
RONO Registrar office number
Email Registrar email address
Raddress Registrar specific location
Descriptions of Database Table Attributes

There are two tables with the same attributes (see Fig.3.20), i.e., PEVotes and PDVotes . The
PEVotes tables will hold votes submitted to parliament candidates. CPIN and VPSN are two of the
attributes in these tables, which are stored with encrypted format. But at the end of the election, the
content of PEVotes table will be copied to the corresponding PDVotes tables by decrypting the
encrypted attributes in the previous tables. The content of PDVotes will remain empty until the
votes become decrypted. The voter table will consist of VPIN, VFirstName, VLastName,
VPSN,Vsex,Vadress,Vage,Vphone and VRegDate. The VPIN will uniquely identify each record of
the voters .This attribute will be stored by converting its value into hashed format. The reason of
hashing the VPIN is to hide its identity. In case, if an attacker gets the chance to access the
database, it will be difficult to use the PIN. The voter table will be associated with PEVotes tables
with one-to-many relation. This is because with one VPIN, the voter will give votes for more than
one candidate, i.e., at least for one parliament candidates. The Candidates table will consist of
CPIN, CFirstName, CLastName, PatrySymbol, CCN and CRegDates. The CPIN attribute is the
primary key which will uniquely identify each of candidate’s record. CCN represents the
constituency number where the candidate registered. In one constituency, there can be many polling
stations. This tables associates with the PEVotes table with one-to-many relationship. This is to
enforce that with one CPIN, so many votes can be given. Similarly, Polling Station table will hold
PSN and PSName for identifying the selected polling stations.
The following are relationships of data base design
Figure 3.19Database Design

The following are account table
The following are Candidatestable
The following are Election committee table
The following are Parties table

The following are Polling station table
The following areVoters table
The following are Registrars table

3.3. User Interface Design

User interface is the external part of the system which is used to access and interact with the system
easily.
Home Page
Figure 3.20Home page screen shut UI

3.4. System Architecture (Deployment Diagram)

Deployment diagrams show the configuration of run-time processing elements and the software
components, processes, and objects that live on them. Software component instances represent run-
time manifestations of code units [3].
Figure 3.21 Deployment Diagram
Reference
http://www.electionethiopia.org.com(visited on June 20017,12:00 AM)
[1]
[2]
Douglas Bell “Software Engineering for Students,”, (4rd Edition), 2001
Introducing Electronic VotingPolicyPaper December 2011

[3]
James Rumbaugh, “The Unified Modeling Language User Guide” (2rd Edition), 2004
[4]
Joseph Schuller, SAMS Teach Yourself UML in 24 Hours (3nd Edition), 2003
[5]
http://www.businessrulesgroup.org/first_paper/br01c3.htm: Accessed on January 3, 2014

[6]
http://creately.com/blog/diagrams/uml-diagram-types-examples/: Accessed on December

[6]
14, 2013
Michele Cyran “Database Concepts” release 2, October 2005

[7]

Best Election System

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Best Election System

Uploaded by

Copyright:

Available Formats

WEB BASED ELECTION SYSTEM FOR ETHIOPIAN ELECTION

BACHELOR OF SCIENCE IN INFORMATION TECHNOLOGY

Under the guidance of

DEPARTMENT OF INFORMATION TECHNOLOGY

2.3.2. Non Functional Requirements.................................................................................................13

1.1. BACKGROUND OF THE STUDY

1.2. STATEMENT OF THE PROBLEM

1.3. OBJECTIVE OF THE PROJECT

1.3.1. General Objective

1.3.2. Specific Objectives

1.4. SCOPE OF THE PROJECT

1.5. SIGNIFICANCE OF THE PROJECT

 Reducing the chances of error occurrence, while counting votes.

1.6. SYSTEM REQUIREMENTS

 It allows easy to create database connection to PHP.

 It provides different security mechanisms.

 It is powerful of any database querying.

1.7. DATA COLLECTION METHODOLOGY

1.7.2. Document Analysis

1.8. FEASIBILITY STUDY

1.8.1. Economic Feasibility

1.8.2. Technical Feasibility

1.8.3. Operational Feasibility

1.8.4. Schedule Feasibility

1.8.5. Legal Feasibility

2.1. Over View of Existing Problem

difficult as papers become bulky with the population size.

2.2. Problems of the Existing System Using Pieces Framework

We classified the problems according to PIECES framework

 Telephone cost (from one polling station to another polling station).

2.3. SYSTEM REQUIREMENT SPECIFICATION

2.3.1. Functional Requirements

 Registration of the voters.

2.3.2. Non Functional Requirements

 Administrators will have 24 hour access to the system.

F. Error handling issue

2.3.3. System Business Rules

2.4. SYSTEM REQUIREMENT ANALYSIS

2.3.1. Actor and Use Case Identification

 Administrator:-Administrator utilizing the system functionality.Each administrator will have a

 Candidate:-agent of the party or independent candidate is candidate for this election to

Table 2.1Use Case Identification

No Use case Use case ID

6 Cast Vote UC-06

2.3.1.3. Use Case Diagram

Give Feedback Register election

Approve candidate Check eligibility to

Post Maintain Forecasting result HPR

Post Post Nominated

Figure 2.1: use case diagram

Use case number UC-01

Basic course of action User action System response

1. The user opens the main page by 2. The system display

5.use case ends

Alternative course of A If the login name or password is invalid

A 5.The user reenters the user name and password

A 6.The use case continues from step 3

Post condition The users successfully login.

Table 2.3: Use case Registrations of Election committee description

Use case number UC-2

Precondition: Election committees must valid users to register in to the database.

Basic course of ac- User action System response

2. Enter password and username to