Olline Voting System12

WSUSU ONLINE VOTING SYSTEM
WOLAITA SODO UNIVERSITY

COLLEGE OF NATURAL AND COMPUTATOINAL SCIENCE
DEPARTEMENT OF COMPUTERSCIENCE AND INFORMATION
TECHNOLOGY
DOCUMENTATION FOR INDUSTRAIAL PROJECT-1
Project title: - Online Voting System for WSU Student Union
GROUP MEMBERS
1.
2.
3.
4.
5.
ID_N0
Hizbayush Dessalew--------------------------------------NCS/R/606/04
Bezawit Gizaw ..NCS/R/283/04
Bezawit Merihun.NCS/R/1317/04
Edilawit MebratuNCS/R/397/04
Kalab Mesfin ..NCS/R/636/04
Advisor Mr. Mesay Wana

Submitted to Department of Computer Science and IT, College of Natural and computational
Science, Wolaita Sodo University, in partial fulfillment for the requirement of the Degree of
Bachelor science in (CSIT)
Wolaita Sodo, Ethiopia
Submission Date Jun 08, 2007 E.C
WSU CSIT
Page I
Abstract
This project was conducted in woliaita Sodo University Student Union Online Voting system. The
objective of this study is design and implement online voting system that can change the current paper
based voting system for Woliata sodo University Student union. To do this project we collect data by
using different methodologies. This project provides solution to handle problem that face voting in the
manual system. In addition, we can identify problems in the existing system using various analyses,
techniques after then we proposed automated system. In order to avoid voter frauds we made security
consideration in which password is used as the security control mechanism. At the end the candidate
result must be keep secret untilthe vote is over to avoid the riot from the candidates supporters and
automatically the systemrelease the timestamp security and the result should be available in the result
page
Acknowledgment
WSU CSIT
Page II

First of all we would thanks to God for help us. We would like to our families for their moral, financial
and loudly support.
We would like to say thanks to our advisor instructor Mesay Wana for his constructive opinion and
willingness to participate in our project, guidance, Temesgen Walilegn to support for the
accomplishing of this project.
We also wish to thank the WSU Student Union, who gave us the required information about the
election.
Finally, we would like to thank the teaching staffs of Information Technology who have contributed
greatly to the success of this project documentation.
Table of Contents
Abstract.............................................................................................................................II
Acknowledgment.............................................................................................................III
List of Acronyms............................................................................................................VI
Chapter One.....................................................................................................................1
WSU CSIT
Page III

Proposal...........................................................................................................................1
1.1 Introduction..............................................................................................................1
1.2 Background...............................................................................................................1
4. Objective......................................................................................................................4
4.1 General Objective....................................................................................................4
4.2 Specific objective......................................................................................................4
5. The Scope of the Project............................................................................................4
6. Methodology................................................................................................................4
6.1 Data Collection Methods.........................................................................................4
6.2 Tool to be used or development tools....................................................................5
6.3 Design approach.......................................................................................................5
7. Required Resource with Costs.................................................................................5
8. Limitationofthe Project.............................................................................................6
Chapter Two....................................................................................................................7
Description of the existing system..................................................................................7
2.1 Introductionof existing system.................................................................................7
2.2 Players in the existing system...................................................................................7
2.3.1. Inputs in existing system............................................................................................... 9
2.3.2. Process of the existing system.......................................................................9

2.7.1 Input (Inaccurate/redundant/flexible) and Output (Inaccurate).....................13
2.7.2 Security and Controls...........................................................................................13
2.7.3 Efficiency...............................................................................................................13
2.8. Proposed Solution for the existing System...........................................................13
2.8.1 Functional Requirement......................................................................................14
Chapter Three................................................................................................................16
System analysis..............................................................................................................16
3.1 Introduction.............................................................................................................16
3.2 System Requirement Specifications (SRS)............................................................16
3.2.1 Use case diagram..................................................................................................16
3.2.2 Use case documentation.......................................................................................18
3.2.3 Sequence diagram.................................................................................................28
3.2.4. Activity diagram....................................................................................................35
WSU CSIT
Page IV

3.2.6 User Interface Prototype......................................................................................43
Chapter Four.................................................................................................................45
System Design................................................................................................................45
4.1 Introduction.............................................................................................................45
4.2 Class Type Architecture..........................................................................................45
4.3 Class Modeling.........................................................................................................47
4.4
State chart modeling.............................................................................................48
4.5 Collaboration modeling...........................................................................................50

4.6 Component modeling..............................................................................................52
4.7 Deployment modeling..............................................................................................52
4.9. User Interface Design.............................................................................................55
Chapter Five..................................................................................................................57
Implementation..............................................................................................................57
5.1. Introduction............................................................................................................57
5.2. Final Testing Of the System...................................................................................57
5.3.Hardware Software Acquisition.............................................................................71
5.4. Installation Process.................................................................................................72
5.5. Start-Up Strategy....................................................................................................72
Chapter Six.....................................................................................................................74
6.1. Conclusions..............................................................................................................74
6.2. Recommendations...................................................................................................74
REFERENCE................................................................................................................75
LIST OF ACRONYMS
PHP..Hypertext Preprocessor
CSS.Cascading Style Sheet
MYSQL .MY Structural Query Language
WSU CSIT
Page V

HTML..Hypertext Markup Language
UML. ..unify Modeling language
UCuse case
WSU--------------------Wolaita Sodo University
WSUSU-------------------- Wolaita Sodo University Student Union
WSU CSIT
Page VI
Chapter One
Proposal
1.1 Introduction
1.2 Background
Background of the Organization
Wolaita Sodo University is one of the universities among 33 universities that found in Ethiopia. It
was established in 1999. Wolaita Sodo university student union is non-profitable office in the
university management.
Wolaita Sodo University Students Union (WSUSU), prior to its establishment as a Wolaita Sodo
University Students Union in 2006, it had first established in the form of students council. But
due existence of varies fields which needs intervention, the more existence of counseling services
is found insufficient and narrower in scope than later on the council is changed (transformed) to
WSUSU. It is founded and proceeded there on as per its own constitution. The constitution, which
establishes and defines the power and structure, is adopted in July 2006. The union is autonomous
non- political and fully secular union which is formed and governed by the students. The primary
objective of the union is to work for the academic and social rights of Wolaita Sodo University.
The current system

Wolaita Sodo University student union voting system is manual and indirect. The union has
parliament system. So, all class except first and graduating students has three candidates with
getting highest vote. After that the students announce the candidates by paper based or mass media
club.
Election conducted in free and fair manner in every 2year.The president, the vice president and
the general secretary come to power through indirect election in a secret ballot. The person with
highest vote shall be come the president, in addition to these chief executives; the union has executive
committee.
They use random selection to elect the administrative
Class representative will be elected with highest vote and they will come together to
form general assembly the union executive committee is composed of each class
representatives.

The elected candidates can process election campaign and introduce their mission and
vision to voters.
By using the ballot paper the voter elect the candidate by the given code.
The vote given to the 18-candidate count in a place where all voters are located, and
the result is verified.
Among the 18 candidates, 9 who have the highest vote can come to the executive
committee of the union.
One physically disabled student representatives and one university girls representatives. Both the
physically disable and university girls representatives possesses its own rule and principle freely for
finding solution to the deeply rooted problem of disabled and female students.
2. Statement of the Problem

We are interested to do this project because to update the existing system in to the automate system
that means the whole academic system, maintain teaching learning process in harmony and all needs in
campus was fulfilling by student union according to their rule and regulation. Also we seen many
problems that challenges during election process based this case we select this topic to redesign the
system. As, result election in online will be very interesting.
In order to find fact and investigate problem and opportunities for improving the activity and filed of
Wolaita Sodo University student Union we identify what problems happen. During the election process
the problems are as follow: Data redundancy and duplication during counting ballots.
It is impossible to generate report.
If the paper is lost all information is destroyed.
Because in the manual system have no permanent storage.
Miscounting of the voter, which makes the result incorrect.
Boring for voters during election.
It needs labor and loss of energy
Exposed to human error.
When the mistake is occurred it is impossible to correct
It is costly to arrange the election board for the election process.
During the election, the arrangement of board for the member must need budget, so it is
costly.
3. Team Composition
Project
Online Voting System For WSU Student Union
title
WSU CSIT
Page 2

Prepared
By Group
10th
S.NO
Name
ID-NO
Responsibility
283/04
Design
BezawitGizaw,
And EdilawitMebratu
BezawitMerihun
1317/04
Analysis
KalabMesfin
636/04
Requirement specification
HizbayushDessalew and
KalabMesfin
606/04
Implementation and testing
Date
Nov15-03-2007
Advisor Mesay Wana
WSU CSIT
Page 3
4. Objective
4.1 General Objective
Design and implement online voting system that can change the current paper based voting system for
WSUSU.
4.2 Specific objective
Reduce voter duplication.

Counting the result.
Recording voter data.
Generating report at end of the election while its going on.
Minimize the election board tasks.
Manage time and cost.
5. The Scope of the Project

The project will include the precession for competent students each get all them by their e-mail and
password , check the student in which it is available in the campus with their id-no. Competent update
their status and as well the system finally can show the result online for the student
6. Methodology
Information is the major requirement for accomplishes our project. Throughout the progress of the
project we gather voter requirement by using face to face interview.
6.1 Data Collection Methods

Interview: We interview the student union president of Teshale Tadese and General Secretary GetachewZewudu.
They give the information about the principles and background of their union.They forward us how the
election process going on as we describe in the current system and about their number of members,
also they tell us the responsibilities of each member.
6.2 Tool to be used or development tools
WSU CSIT
Page 4

We select the tools listed below because they are very suitable for our project.
Client side coding __________________HTML

Client side scripting ________________ JavaScript
Platform ________________________ MS Window
Database server ________________
MySQL
Server side scripting ________________ php
Web server_______________________ Apache
Browser _________________________ IE 5.5/6.0/7.0, Mozilla Firefox 3.0.
Editor__________________________ notepad++,
Documentation __________________ Ms Word
User Training ____________________ MS PowerPoint
6.3 Design approach

Object oriented approached system analysis methodology will be used, as a primary requirement
modeling methodology to structure the systems requirements.
7. Required Resource with Costs
NO
Required Resource
Amount
Price in birr
Required Resource
Stationary
A4 paper
1desta
90birr
Pen
10
50birr
Internet
__
200birr
Hard ware
Dell computer ,CD, flash disk ,
__
5,000birr
Soft ware
Dreamweaver, notepad++,
__
100birr
Total
5440birr
8. Limitation of the Project

The limitation of our project is not included Sumer, night and weekend, because they are not
found in regular time.
WSU CSIT
Page 5

9. Task and Time Schedule
Task
MONTHES
NOV
DEC
JAN
MAR
APR
MAY
JUN
Project
1
Proposal
Requirement
specification
System analysis
System design
Implementation
Testing
Documentation
Chapter Two
Description of the existing system
2.1 Introduction of Existing System
The current system of Wolaita Sodo University Student Union system is manual. The union election is
conducted free and fairly through process and the committee should run many of the process. The
students that work on the union organized the election committee. The election of the candidate is
WSU CSIT
Page 6

running within the normal way. The election of the executive committee is conduct in the place where
the university president and student president are appearing. After the election is finished the result is
known or nine winners candidate was announce to the student and the management office of the
university.
2.2 Players in the existing system

Player or actor refers to a person, organization, or external system that plays a role in one or more
interactions with the existing system. The major actors or players that are involved in the existing
system are the following.
1.
Voters
2 Observant
3. Executive committee
4. Chief Executives
5.Tallying
6. Candidates
Definition of players in the system:

Executive committee:
An executive committee has executive power within the union. The executive committee meets and
determines what the agenda of the board will be. Revise the activities and deal problems reported to it
and recommend the president to take action, also gives recognition or reject as to formation of club or
association of discipline in the union.
Observant
University president, student president, the roles that are play below:
Controls incase if one candidate leave before election.

Observe how the election is flow or going on identifying availability.
Chief Executives in the student union like president, Vice president and General Secretary.
The President: is he the person with highest executive power. He Nominate the members to be the
electoral board. In addition, present it to the executive committee for approval. As well appoints the
executive committee within the union.
WSU CSIT
Page 7

Vice President: Up on a vacancy in the office of the president, he shall assume position of the
president and fulfill all the presidential role or duties.
General Secretary: is the person with high executive power the psychological relevance of the
affected person in and outside of the university.
Others are student union clubs: the unions have various clubs, which enable the student to promote
and assist welfare, social, educational, cultural activities advertising in the mini media.
Tallying
The tallying authorities count the votes and announce the election results.
Voter or students: the voter is the students for Woalita Sodo University who interact with candidates.
A voter has the right for voting, and he votes in the election.
Candidates
Candidates are one of the participants in the existing system that are students nominated for election.
Election committee
The election committee post announcements, rules, and regulations of the election to the all University
students before and after the election.
2.3 Major Functions of the Existing System

The Wolaita Sodo University Student Union has major functions as to observe and secure that the best
interest of students in the academic and services are realized with the required quality and observing
students adopting culture of peace, love and unity regardless of their difference. Each activity has
their input, process and output. The input used to as a row material for the result of the activities or
output.
2.3.1. INPUTS IN EXISTING SYSTEM
The whole process of the current is system done manually. In this regard, the inputs include like:
Candidates registration including candidates information like,

Name
Sex
Department
WSU CSIT
Page 8
Faculty
Election committee
Tally .
2.3.2. Process of the existing system

This process is starts from election committee. First, the election committee post on the news board or
any place in the university as election campaigns up to 15 day. After than election committee distribute
each Department to select the candidate and they will come together to form general assembly, the
elected candidates that elected from each department can process election campaign and introduce
their mission and vision to voters. By using the ballot paper the voter elect the candidate by the given
code among the candidates18 have their own code and each code have its own value also they
announce their mission and vision to other candidates and voter. The votes given to the 18 candidates
count in a place where all voters are located then election committee know the result.
2 .3.3. Output in the existing system
The output in the voting system is the vote should be counted by the committee and post the result or
the electoral board can post candidates result that is who will be elected.
2.4. Business rule

Business rule is a rule in which the organization uses it to perform any activities. The following are the
major business rule used by Wolaita Sodo University Student Unions.
The candidates and voters must be Woalita Sodo University Regular Students.
The candidate must pass the electoral procedures like, have good communication to students.
Candidates must be free from any political issues that means not interfere to any
political difference.
The electoral board can post candidates result that is who will be elected.
The candidate can post their photo so that the voters can know them very well as well as their
vision.
The committee can post the date of election.
The candidates have good performance in academic.
Voters cant vote more than once
After vote is finished, the electoral committee count and announce the vote result.
As well as who won the vote by posting them in the campus.
2.5 Report generated in the existing system

The reports were generating for the General student union of Wolaita Sodo University. Different
reports were generating in the existing system based on the work done. How the election is going,
WSU CSIT
Page 9

during the election who win and in what way the election become best in the union how the function is
flow these all were reporting in monthly and annually. These all are as well report to student president
and General assembly in horizontally.
2.6 Forms and other documents of the existing systems

There are some forms used by the election for different purpose. These forms and documents are paper
based. The following are currently used forms, Candidates form
The following form shows Executive committees form
WSU CSIT
Page 10
2.7 Bottlenecks of the existing system

As we described in the proposal paper in Statement of the problem part there are some problems that
existing system face because it is manual. In this part we describe the problems in detail by dividing
them according to performance, input and output accuracy, security and control lastly efficiency.
WSU CSIT
Page 11

2.7.1 INPUT (INACCURATE/REDUNDANT/FLEXIBLE) AND OUTPUT
(INACCURATE )
Input
Inputs in the current manual system have problems like unnecessary duplication of data, data entry
procedure exposed to errors, files occupy a large storage space and generating report is not easy. That
means, counting errors has occurred in this process, and in some cases, voters find ways to vote more
than once, introducing irregularities in the final count results.
Output
The current manual system, it is not easy to get the appropriate information. Example Papers is plug
off from the board news Or the Rain may washed out also the vote result always is not prompt to all
students at the same time in case that theposted. If the input is inaccurate, also the output is inaccurate.
There is also data redundancy.
2.7.2 Security and Controls

In the current system, files were exposing to theft, unauthorized modification due to low data security
levels and standards.
2.7.3 Efficiency
The current system lacks much efficiency because it takes time to perform tasks. Counting vote is
more time consuming the data may beredundantly recorded and data entry procedure may be exposed
to errors. The system not organized to perform each activities and it is not flexible to change or modify
the data whenever needed.
2.8. Proposed Solution for the existing System

The main user of this project is Wolaita Sodo University Regular Students. The main aim of the
proposed system is to automate the election system and facilitate the electoral process, which was
conducted manually. Automate online voting system is being designed and implemented by group
members. Our main aim was to develop web based online voting system. The task of developing
automateonline voting system was assigned to Woalita Sodo University Student Union (WSUSU). The
proposed systems goals are the following:
Saving labor before and during the election or reduce voter duplication.
The system becomes more secure.
The counting process is easy.
WSU CSIT
Page 12

The system displays the result of the vote.
It has effective report generation.
It is better and wise to perform election.
It is flexible to change or modify the data whenever needed.
2.8.1 Functional Requirement

A Functional Requirement is a requirement in which the area of functionality of the system
must support. Functional requirements specify the functions of the system, how it records,
computes, transforms, and transmits data. Each interface has its own functions. Typically, the
user interface is the most important interface, since most of the data are record and shown
through it. Functional requirement define what the system needs to do. The following are the
functional requirements of our system.
Post Announcements: - The committee will post announcements, rules, and regulations of the
election, which will be show for all students and candidates.
Manage time: - The committee sets a vote by entering Election Day, start time, end time. Then the
system will check validate date
Manage: The committee manages all the student, general assembles, and candidates activity.
Check Duplicate Vote: - The system checks voter vote more than once by storing all the votes in a
database.
Check eligibility: it checks weather a student, general assembles or a candidate is eligible student for
the election or not.
Select candidate: the general assembles select the candidate.
Make campaign: candidates introduce themselves to the voters.
Select candidate: the general assembles perform vote.
Generate report: - The system will generate report of the election by the election committee.
Moreover, the users can see the result of election.
2.8.2 Non functional Requirement
A non-functional requirement is a requirement that specifies criteria that used to judge the operation of
a system. Nonfunctional requirements describe user-visible aspects of the system are not related
WSU CSIT
Page 13

directly to the functional behavior of the system. The non-functional requirement of our system is list
below:
Uniqueness: No student should be able to vote more than once and the vote is secret.
Accuracy: Voting systems should record the votes correctly. All operation shall be accurate.
Authentication: Only an authorized students hold is able to vote by login to the system.
Availability: All data in the system should be available all the time.
Integrity: Votes should not be able to modify by another rather than committee.
Confidentiality: Increase student confidence and improve the voting experience.
User- interface: our system shall provide an easy-to-use graphical user interface users to input
and retrieve data.

Usability: our system expected that the user should be able to vote easily online. Provide
systematic guide for both committee and users. User should complete voting in a few minutes.
Performance:
Our system is better component design to get better performance at peak time the system should
accommodate all WolaitaSodo University regular students who are already register in student database.
The system can access by the users, or student inside the university and the system must have a good
response time.
Security and Access permissions: the security requirements work based on the information security
management. System should be secured from attacks and unauthorized access. Student database plus
detail information of student ask during registration and the system displays student ID to check.
Concurrency: the system should support multiple voters to cast their votes concurrently.
Backup and Recovery
The system should be holding a backup of the data by using different storage device.
That means our system will back up using external drives like CD, DVD, Flash.
Chapter Three
System analysis
3.1 Introduction
Systems analysis is a process of collecting factual data, understand the processes involved, identifying
problems and recommending feasible suggestions for improving the system functioning. In this
WSU CSIT
Page 14

system, we used an object oriented system development methodology including use case diagram,
sequence diagram, class activity, conceptual modeling and interface.
3.2 System Requirement Specifications (SRS)

System requirement is structured collection of information that embodies the requirements of a system.
3.2.1 Use case diagram

Use Case the specification of sequences of actions that a system, subsystem, or class can perform by
interacting with outside actors. In addition, use case diagram have boundary, actor and use case Actors
are:
Committee
Candidates
General assembles
Student
The use cases of this system are:
Register for vote.
Cast vote.
View campaign.
View report.
Make campaign.
Manage announcement.
Manage candidates.
Manage general assembles
Manage time.
Login.
The use case diagram has shown as below:
WSU CSIT
Page 15
WSU CSIT
Page 16

3.2.2 Use case documentation
Table1: Use case documentation for log in
Use case Name
Login
Actor
Candidate, committee, general assembles
Description
This use case is used to authenticate users to the system
Precondition
User must have username and password
Post condition
Users enter to the authorized page
Basic course of action
Actor Action
System Response
1. The user loads to the
system.
2. The users click on the
login page.
4 The users enter user name
7
and password.
The users go their own
page.
Systems display the login

form and ask to fill the
username and Password.

System check entered
value and its privilege.

6 System displays authorized
8
page.
Use case end.
Alternative course
A: The system validates the entered information
the input data is invalid
The system asks again to enter password and username or update
account.
Table2: Use case documentation for registration for vote
WSU CSIT
Page 17
Use case Name
registration for vote
Actor
Committee
Description
Committee register the general assembles.
Precondition
The committee adds their information in to account database.
Post condition
The general assembles will form
Basic course of
Actor Action
action
The committee
select login page.

Enter user name
System Action
and password.
6. Click on the voter
button.
8 Click add new button
9 Enter required the
information.
2. System displays the login form and asks to

fill the username and Password.
4. System check entered value, and its
privilege.
5. System displays authorized page.
7. System displays the general assembles.
10. System store data in voter table.
11. Use case ends.
Table 3 use case documentation for view campaign
WSU CSIT
Page 18

Use case Name
View campaign.
Actor
General assembles, candidate.
Description
User should see the campaign of candidate.
Precondition
The candidate will post campaign.
Post condition
User can see the candidate campaign.
Basic course of
Actor Action
action
System Action
1. The users load to
3. The system displays the campaign.
system or enter to
2
home page.
Click on view
Use case ends.
campaign page.
Table4: Use case documentation for cast vote

Use case Name
Cast vote.
Actor
General assembles
Description
Perform vote.
Precondition
They do not cast before.
Post condition
The candidate will vote
Basic course of
Actor Action
action
The general
System displays login form and asks to
assembles select
enter the required information.
login page.
Enter user name
4 System check entered value and its
and password.
privilege.
6. Click on cast vote

button.
8. Select their own
choose.
WSU CSIT
System Action

7. Display candidates to the vote
7
System stores the vote to voting

database. Moreover, send successful
Page 19

message.
Use case ends.
A: The system checks the voter ballot,

Alternative
If voters vote more than one times,

Then the system updates the vote.
Table5: Use case documentation for view report

Use case Name
View report
Actor
Student, candidate, general assembles
Description
User should see the result of election.
Precondition
The election will be started
Post condition
User can see the candidate result.
Basic course of
Actor Action
action
1. The users load to

the system enters
to home page.
2. Click on view
System Action
3. The system displays the report.
4. Use case ends.
report button.
.
Table6: Use case documentation for make campaign
Use case Name
Make campaign.
Actor
Candidates
WSU CSIT
Page 20
Description
The campaign should display on the system.
Precondition
The candidate must have user name and password.
Post condition
Users saw precession campaign.
Basic course of
Actor Action
action
1. The students select
System Action
2. System displays login form and
candidate page.
3. Enter user name and
password.
6. Click on make
campaign button.
7. Upload their campaign.
asks to enter the required

information.
privilege.
5. System displays authorized page to
user.
8. Enter the campaign to the candidate
database.
9. Use case ends.
Table7: Use case documentation for manage time
Use case Name
Manage time
Actor
Committee
Description
The committee decides the end and start of election date & time.
WSU CSIT
Page 21

Precondition
The committee must have user name and password.
Post condition
The schedule time is set.
Basic course of
Actor Action
action
System Action
1. The user loads to
3. The system displays the login
the system.
2. Enter login page.
4. Enter user name
form and asks to enter the
and pass word.

7. Click manage time
button.
8. Set election
schedule.
required information.
5. System checks entered value
and its privilege.
6. System displays authorized
page.
9. Store in to time database.
10. Use case ends.
Table8: Use case documentation for manage candidate
WSU CSIT
Page 22

Use case Name
Manage candidate
Actor
Committee
Description
The committees manage the candidates.
Precondition
Post condition
Candidates information modified.
Basic course of
Actor Action
action
System Action
3. Display the login form and ask
the system.
2. The users click on
them to enter user name and
login page.
4. The users enter
user name and
password.
7. Click on manage
candidate button.
8. Manipulate
password.
5. System checks entered value and
its privilege.
9. Store the information in candidate
database.
10. Use case ends.
information.
Table9: Use case documentation for manage announcement
Use case Name
Manage announcement.
Primary actor
Committee
Description
The announcement should display on the system.
Precondition
Post condition
User saw the announcement.
WSU CSIT
Page 23

Basic course of
action
Actor Action
1. The students select
login page.
System Action
2.System displays login form and asks
to enter the required information.
3. Enter user name and
password.
privilege.
6. Click on manage
announcement button.
7. Manage announcement.
8. Enter to home page.

9. Use case ends.
Table10: Use case documentation for general assemble
WSU CSIT
Page 24

Use case Name
Manage general assembles
Actor
Committee
Description
The committees manage the general assembly.
Precondition
Post condition
The general assembles will be managed.
Basic course of
Actor Action
action
System Action
3. Display the login form and ask
the system.
2. The users click on
them to enter user name and
login page.
4. The users enter
user name and
password.
7. Click on manage
general assembles
password.
5. System checks entered value and
its privilege.
9. Store the information in general
assembles database.
10. Use case ends.
button.
8. Manipulate
information.
Security Login
On the case diagram of proposed system, every actor in the system has their own privilege to
access the system based on their assigned job.
Registration
In the existing system, the activities done are register in paper forms. To mention some
When a students register for a candidate, it is registered on a candidate form.
When the candidate elect for an executive committee, it has registered on an executive
committee form.
When a candidates elect an executive committee, it is registered on an executive
committee form.
The candidate precession was cannot register.
In the proposed system, the activities performed are register in the systems database, which is the
container of all data. It is explain as follows:
WSU CSIT
Page 25
When the students register for voting, it is register on a system database.

The student vote is register on the system database.
3.2.3 Sequence diagram

Sequence diagram used to show the interactions between objects and actors in a timely sequence
manner. It depicts the sequential flow of messages among objects and actors. Sequence diagrams used
to model usage scenario of one or more use cases. Below are a sequence diagrams for each the above
use case documentation.
1. Sequence diagram for login use case
2. Sequence diagram for registration for vote
WSU CSIT
Page 26
3. Sequence diagram for view campaign
WSU CSIT
Page 27
3. Sequence diagram for casting vote
5.
5.Sequence diagram for view report
WSU CSIT
Page 28
6.
Sequence diagram for make campaign.
7. Sequence diagram for manage time

WSU CSIT
Page 29
8. Sequence diagram for manage candidate

WSU CSIT
Page 30
9. Sequence diagram for manage announcement.
WSU CSIT
Page 31
10. Sequence diagram for manage general assembles.
WSU CSIT
Page 32
3.2.4. ACTIVITY DIAGRAM

Activity diagram used to document the logic of a single operation/method, a single use case or system
in terms of activities. Activities are states that represent the execution of a set of operations. It is
equivalent to flowchart and data flow diagram from structure development. It is an UML diagram used
to model high-level business process or transition between states of a class. Activity diagram shows the
series of activities, which are done in use case. Activity diagram is essentially a flowchart, showing
flow of control from activity to activity.
1. Activity diagram for login page
WSU CSIT
Page 33
2.Activity diagram for registration for vote
WSU CSIT
Page 34
3. Activity diagram for view campaign.
WSU CSIT
Page 35
4. Activity diagram for cast vote.
WSU CSIT
Page 36

5. Activity diagram for view report
6. Activity diagram for make campaign
7.Activity diagram for manage time
WSU CSIT
Page 37
8.Activity diagram for manage candidate
WSU CSIT
Page 38
9. Activity diagram for make announcement
10. Activity diagram

for manage general
assemble
3.2.5 Analysis level class diagram (conceptual modeling)
WSU CSIT
Page 39

Class diagrams should refined by adding relationships between classes, attributes and methods
represent 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.
3.2.6 User Interface Prototype

User interface flow diagram show the relationships between the major user interface elements.
WSU CSIT
Page 40

Interface prototype describes the skeleton of the structural model of the system. User interface
Prototype used to determine gathering requirements for use case modeling, domain modeling used for
determine the requirement of the system.
Chapter Four
WSU CSIT
Page 41

System Design
4.1 Introduction
This chapter is concerned system design that provides the understanding and procedural details
necessary for implementing the system recommended in the system study. The purpose of designing is
to show the direction how the system is built and to obtain clear and enough information needed to
drive the actual implementation of the system.
4.2 Class Type Architecture

Software architecture is used organizing our software design into layers/collections of classes or
components that fulfill common purpose, such as implementing our user interface or the business logic
of our system. Components that perform similar types of functions are generally grouped into layers.
These layers are further organized as a stack in which components in a higher layer use the services of
components in the layer below. A component in a given layer will generally use the functionality of
other components in its own layer or the layers below it. Our system will have the following enterprise
application layer structure.
The description of class type architecture
Presentation Layer: The presentation layer contains components needed to interact with the
user of the application. Examples of such components are web pages, rich-client forms, user
interaction process components etc. that we are about to develop them in jsp and servlets.
Business Layer: The business layer encapsulates the core business functionality of the
application.
Data Access Layer: The data access layer provides a simple API for accessing and
manipulating data. The components in this layer abstract the semantics of the underlying data
access technology thus allowing the business layer to focus on business logic. Each component
typically provides methods to perform Create, Read, Update, and Delete operations for a
specific business entity.
Data Stores: Enterprise applications store their data in one or more data stores. Databases and
file systems are two very common types of data stores. We use the MySQL data base server for
our project.
WSU CSIT
Page 42

We divide our classes to this layered architecture.
Figure
4.1 class
type architecture
Business Layer
Data Access
WSU Layer
CSIT
OnlineVotingSystem.Business
Data
store (MySQL)
OnlineVotingSystem.Persistence
Page 43
Data store
Presentation Layer
JSP and
servlet
Business Layer
Online voting
system.Businesssystem.
Bussiness
Data Access Layer
Online
votingsystempersistenceppb
opresistenceprepresistences
ystempresistence
4.3 Class Modeling

A class modeling provides an overview of a system by describing the object and classes inside the
system and the relationship between them. Class modeling are static; they display what interacts or
soultion but not what happens during the interaction or problem.
WSU CSIT
Page 44
4.4
State chart modeling
State chart diagrams describe the behavior of an individual object as a number of states and transitions
between these states. A state is a condition that an object satisfies. A transition represents changes of
state triggered by events, conditions, or time.). The state chart diagram focuses on the transitions
between States as a result of external events for an individual object.
Both activity and state chart diagrams are useful in modeling the lifetime of an object. However,
activity diagram shows flow of control from activity to activity; whereas state chart diagram shows
flow of control from state to state.
WSU CSIT
Page 45

State chart diagram for login
Fig 1 state chart diagram for login
State chart register for vote

WSU CSIT
Page 46
Fig 2 state chart student registration for vote
4.5 Collaboration modeling

A collaboration diagram is a diagram that shows object interactions organized around the objects and
their links to each other. It shows the message flow between objects and basic associations or
relationships between classes. It is also communication diagram.
Collaboration model for login
WSU CSIT
Page 47
Fig 4 collaboration diagram for login

Collaboration model for register for vote
WSU CSIT
Page 48

4.6 Component modeling
Component diagrams represent a set of components and their relationships. Component diagrams are
used to visualize the physical components in a system.
4.7 Deployment modeling

Deployment diagrams are a set of nodes and their relationships. A deployment diagram illustrates the
physical deployment of the system into a production (or test) environment. It shows where components
will be located, on what servers, machines or hardware. It may illustrate network links, LAN
bandwidth.
To describe a web site, for example, a deployment diagram would show what hardware components
("nodes") exist (e.g., a web server, an application server, and a database server), what software
components ("artifacts") run on each node (e.g., web application, database), and how the different
pieces are connected
The nodes appear as boxes, and the artifacts allocated to each node appear as rectangles within the
boxes. Nodes may have sub nodes, which appear as nested boxes. A single node in a deployment
diagram may conceptually represent multiple physical nodes, such as a cluster of database servers.
WSU CSIT
Page 49
3.8 .Persistence modeling

The persistent classes are used to store most important and permanent in formation of the system.
The data part of a system is modeled using a data modeling methodologies. Persistence diagram
modeling is one of these models. That can show cardinality and ordinarily of relationships between
the different entities of the database.
WSU CSIT
Page 50
WSU CSIT
Page 51
4.9. User Interface Design

User interface for home page
WSU CSIT
Page 52
Committee login page
Manage account page
WSU CSIT
Page 53
CHAPTER FIVE
IMPLEMENTATION
5.1. Introduction
Implementation is the last part of our project phase. It is all about coding the client and server side
implementation concerned with the type of material or Hardware and software required, techniques to
develop the system.
5.2. Final Testing Of the System

For home page
<html>
<head>
<link rel="stylesheet" href="main.css" type="text/css" media="screen"/>
<link href="menu.css" rel="stylesheet" type="text/css" media="screen" />
<link href="themes/4/js-image-slider.css" rel="stylesheet" type="text/css" />
<script src="themes/4/js-image-slider.js" type="text/javascript"></script>
<link href="generic.css" rel="stylesheet" type="text/css" />
</head>
<body>
<table align="center" style="width:900px;border:1px solid
gray;background:whiteurl(img/tbg.png) repeat-x left top;border-radius:12px">
<tr style="height:auto;border-radius:12px;background: white url(img/tbg.png) repeat-x
left top;">
WSU CSIT
Page 54

<td colspan="3">
<imgsrc="img/logo.png" width="150px" height="150px" align="left" style="marginleft:10px">
<imgsrc="img/union.png"width="450px" style="margin-left:30px;margin-top:40px"
align="center">
<imgsrc="img/logo.jpg" width="150px" height="150px" align="right" style="marginleft:10px">
</td></tr>
<tr><td colspan="2" bgcolor="#51a351" id="Menus" style="height:auto;borderradius:12px;">
<ul>
<li class="active"><a href="index.html">Home</a></li>
<li><a href="about.html">About Us</a></li>
<li><a href="candidate.html">Candidates</a></li>
<li><a href="vote.html">Vote</a></li>
<li><a href="contacts.html">Contact Us</a></li>
<li><a href="login.html">Login</a></li>
</ul>
</td></tr></table>
<table align="center" style="border:1px solid gray;border-radius:12px;"><tr><td>
<div id="sliderFrame">
<div id="slider">
<imgsrc="images/slider-1.jpg" />
<imgsrc="images/slider-4.jpg"/>
</div></div></td></tr></table>
WSU CSIT
Page 55

<table align="center" style="width:900px;border:1px solid gray;border-radius:12px;"
height="500px">
<trvalign="top">
<td><div style="clear: both"></div>
<div id="left">
<ul>
<li><a href="index.html">Home</a></li>
<li><a href="help.html">Help</a></li>
<li><a href="comment.html">Comment</a></li>
<li><a href="login.html">Login</a></li>
</ul>
</div></td><td>
</table>
<table align="center" style="width:900px;border-radius:12px;border:1px solid
gray;background:whiteurl(img/tbg.png) repeat-x left top;" height="70px" >
<tr>
<p style="text-align:right;padding-right:30px;"><a href="index.html">Home</a>|<a
href="about.html">About Us</a>|<a href="contact.html">Contact Us</a></p>
<p ><hr width="350px" align="right"></p>
<p style="text-align:right;padding-right:30px;"><font color="#ffffff">Copyright ©
2007 Reserved.</font></p>
</td></tr></table>
</body>
</html>
For login
WSU CSIT
Page 56

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<script type="text/javascript">
functionchange_char(){
var pass = document.getElementById("pw");
var checkbox = document.getElementById("cb");
if(pass.type == "password"){
pass.type = "text";
checkbox.checked = true;
}else{
pass.type = "password";
checkbox.checked = false;
}}
</script>
</head>
<body>
<table align="center" style="width:900px;border:1px solid
gray;background:whiteurl(../img/tbg.png) repeat-x left top;border-radius:12px">
<tr style="height:auto;border-radius:12px;background: white url(../img/tbg.png) repeat-x left
top;">
<tr><td colspan="2" bgcolor="#51a351" id="Menus" style="height:auto;border-radius:12px;">
<ul>
<li><a href="index.html">Home</a></li>
WSU CSIT
Page 57

<li class="active"><a href="login.html">Login</a></li>
</ul>
</td></tr></table>
height="500px">
<trvalign="top">
<table class="log_table" align="center" >

<form action="" method="POST">
<trbgcolor="#51a351" ><thcolspan="2" ><font color="#ffffff">Login</font></th></tr>
<tr><td><label>User Name</label></td>
<td><input type="text" name="user" required x-moz-errormessage="Enter Username"/></td>
</tr>
<tr><td><label>Password</label></td>
<td><input type="password" name="pass" required x-moz-errormessage="Enter password"
id="pw"/></td></tr>
<tr><td></td><td><input type="checkbox" name="checkbox" id="cb"
onClick="change_char();"> Show Characters</td></tr>
<tr><td></td>
<td><input type="submit" name="log" value="Login" class="button_example"/><input
type="reset" value="Reset" class="button_example"/></td></tr>
<tr><td></td><td><a href="forget.html">Do yo forget your password?</a></td>
<tr><tr><td><br></td></tr></form></tr></table>
<tr><td id="link"><p style="text-align:right;padding-right:30px;"><a
href="index.html">Home</a>|<a href="about.html">About Us</a>|<a
href="contact.html">Contact Us</a></p>
WSU CSIT
Page 58

<p style="text-align:right;padding-right:30px;"><font color="#ffffff">Copyright © 2007
Reserved.</font></p></td></tr></table>
</body>
</html>
5.2.2
Code for php
For login
<?php
include("connection.php");
session_start();
?>
<script type="text/javascript">
functionchange_char(){
var pass = document.getElementById("pw");
var checkbox = document.getElementById("cb");
if(pass.type == "password"){
pass.type = "text";
checkbox.checked = true;
}else{
pass.type = "password";
checkbox.checked = false;
}}
</script>
</head>
WSU CSIT
Page 59

<body>
<tr>
<td colspan="2" bgcolor="#51a351" id="Menus" style="height:auto;border-radius:12px;">
<ul>
<li><a href="index.php">Home</a></li>
<li><a href="about.php">About Us</a></li>
<li><a href="candidate.php">Candidates</a></li>
<li><a href="vote.php">Vote</a></li>
<li><a href="contacts.php">Contact Us</a></li>
<li class="active"><a href="login.php">Login</a></li>
</ul></td></tr>
</table>
<td><div id="right">
<div class="desk">
<h1>Login page</h1
<?php
if (isset($_POST['log'])){
$username=$_POST['user'];
$password=$_POST['pass'];
$sql ="SELECT * FROM user WHERE username='$username' AND
password='$password'";
$result = mysql_query($sql);
// TO check that at least one row was returned
$rowCheck = mysql_num_rows($result);
$row=mysql_fetch_array($result);
$status=$row['status'];
if($row['role']=='admin'){
WSU CSIT
Page 60

if($status==1)
{
$_SESSION['u_id']=$row['u_id'];
echo "<script>window.location='system_admin.php';</script>";
}
else{
echo'<p class="wrong"> Your Account is not active Please contact the system Admin</p>';
echo' <meta content="15;login.php" http-equiv="refresh" />';
}}
else if($row['role']=='registrar'){
if($status==1)
{
}
else
{

}}
else if($row['role']=='admin'){
if($status==1)
{
}
WSU CSIT
Page 61

else{
echo'<p class="wrong"> Your Account is not active Please</p>
}}else {
echo'<br>';
echo' <p class="wrong">Check Your username or/and Password!</p>';
}}
mysql_close($conn);
?>
<form action="login.php" method="POST">
<trbgcolor="#51a351" ><thcolspan="2" ><font color="#ffffff">Login</font></th></tr>
<tr><td><label>User Name</label></td>
<td><input type="text" name="user" required x-moz-errormessage="Enter Username"/></td>
</tr>
<tr><td><label>Password</label></td>
<td><input type="password" name="pass" required x-moz-errormessage="Enter password"
id="pw"/></td></tr>
<tr><td></td><td>
<input type="checkbox" name="checkbox" id="cb" onClick="change_char();"> Show
Characters</td></tr>
<td><input type="submit" name="log" value="Login" class="button_example"/>
<input type="reset" value="Reset" class="button_example"/></td></tr>
<tr><td><a href="forget.php">Do yo forget your password?</a></td>
<br><br></tr>
</form>
</table><br><br></div></div>
WSU CSIT
Page 62

<tr><td id="link">
<p style="text-align:right;padding-right:30px;"><a href="index.php">Home</a>|<a
href="about.php">About Us</a>|<a href="contact.php">Contact Us</a></p>
<p style="text-align:right;padding-right:30px;"><font color="#ffffff">.</font></p>
</td></tr></table>
</body>
</html>
For add voter
<?php
include("connection.php");
session_start();
if(isset($_SESSION['u_id']))
{
$mail=$_SESSION['u_id'];
} else {
?><script>
alert('You are not logged In !! Please Login to access this page');
alert(window.location='login.php');
</script>
<?php }?>
<?php
$user_id=$_SESSION['u_id'];
$result=mysql_query("select * from user where u_id='$user_id'")or die(mysql_error);
$row=mysql_fetch_array($result);
$FirstName=$row['fname'];
WSU CSIT
Page 63

$middleName=$row['mname'];
?>
<head>
<SCRIPT language='Javascript'>
functionisNumberKey(evt)
{varcharCode = (evt.which) ? evt.which : event.keyCode
if (charCode> 31 && (charCode< 48 || charCode> 57))
return false;
return true;
}
</SCRIPT>
</head>
<body>
<tr><td colspan="2" bgcolor="#51a351" id="Menus" style="height:auto;border-radius:12px;">
<ul>
<li><a href="e_candidate.php">Candidates</a></li>
<li><a href="logout.php">Logout</a></li>
</ul>
</td></tr></table>
height="500px">
<trvalign="top">
<div id="left">
<ul>
WSU CSIT
Page 64

<li><a href="reg_voter.php">Voter</a></li>
<li><a href="e_result.php">Result</a></li>
<li><a href="e_generate.php">Generate Report</a></li>
<li><a href="ov_candidate.php">Candidates</a></li>
<li><a href="e_comment.php">View Comment</a></li>
<li><a href="logout.php">Logout</a></li>
</ul>
</div></td>
<td><div id="right"><div class="desk">
<h1 align="right"><?php
echo '<imgsrc="img/people.png" width="40px" height="30px"> '.'<font style="texttransform:capitalize;"face="times new roman" color="green" size="3">Hi, '.
$FirstName." ".$middleName." ".'</font>';?></h1>
<br><br>
<?php
if(isset($_POST['ok']))
{
$fname=$_POST['fname'];
$mname=$_POST['mname'];
$lname=$_POST['lname'];
$vid=$_POST['vid'];
$sex=$_POST['sex'];
$phone=$_POST['phone'];
$email=$_POST['email'];
$psname=$_POST['psname'];
$pass=$_POST['pass'];
$query="SELECT * FROM voter where vid='$vid'";
$resultw=mysql_query($query);
WSU CSIT
Page 65

$count=mysql_num_rows($resultw);
if($count>0)
{
echo' <p align="center"><font color="red" size="3">
<p class="wrong">Voter ID is used by another Voter</p>';
echo'<meta content="15;create.php" http-equiv="refresh"/>';
}
else{
$sql="INSERT INTO voter (vid,fname,mname,lname,sex,phone,email,password)
VALUES
('$vid','$fname','$mname','$lname','$sex','$phone','$email','$psname','$pass','0')";
if (!mysql_query($sql,$conn))
{
echo' <p class="wrong" style="text-decoration:blink;">Already Registered with this USER ID</p>';
echomysql_error();
echo'<meta content="10;add_voter.php" http-equiv="refresh" />';
}
else{
echo'<p style="text-decoration:blink;" class="success">Registered successfully!</p>';
echo' <meta content="6;add_voter.php" http-equiv="refresh" />';
}}}mysql_close($conn)
?>
<form action="add_voter.php" method="post">
<trbgcolor="#51a351" ><thcolspan="2" height='30px'><font color="#ffffff">Add new voter</font>
<a href="reg_voter.php"><img align="right"src="img/close_icon.gif" title="close"></a></th></tr>
<tr><td><font color="red">*</font><label>First Name</label></td>
WSU CSIT
Page 66

<td><input type="text" name="fname" required/></td></tr>
<tr><td><font color="red">*</font><label>Middle Name</label></td>
<td><input type="text" name="mname" required/></td></tr>
<tr><td><font color="red">*</font><label>Last Name</label></td>
<td><input type="text" name="lname" required/></td></tr>
<tr><td><font color="red">*</font><label>Voter ID</label></td>
<td><input type="text" name="vid" required maxlength='8'/></td></tr>
<tr><td><font color="red">*</font> Sex:</td>
<td><input type="radio" name="sex" value="male" title="choose either male by clicking here"
required />
Male
<input type="radio" name="sex" value="female" title='choose female by clicking here' required />
Female</td></tr>
<tr><td><input type="text" name="age" maxlength='2' onKeyPress="returnisNumberKey(event)"
required/></td></tr>
<tr><td> <label>Phone No</label></td>
<td><input type="text" name="phone" maxlength='10' onKeyPress="return isNumberKey(event)" />
</td></tr>
<tr><td> <label>Email</label></td>
<td><input type="text" name="email" /></td></tr>
<tr><td><font color="red">*</font><label>Job</label></td>
<td><select name="eduction" required><option></option>
<option value="student">Student</option>
</option>
<option value="other">other</option>
</select></td></tr>
<tr><td><font color="red">*</font><label>Password</label></td>
<td><input type="password" name="pass" maxlength='10' required/></td></tr>
WSU CSIT
Page 67

<tr><td><input type="submit" name="ok" value="Save" class="button_example"/>
<input type="reset" value="Reset" class="button_example"/>
</td></tr><tr><td><br></td><td>
<font color="red">*</font> is Manadatory Field.
</td></tr></form></table>
</div></div>
</td></tr></table>
5.3.Hardware Software Acquisition

For the proper functioning of the system the following hardware and software are required
Hardwares
Computer
CD
Softwares
Macromedia Dreamweaver ,notepad++
Browsers(one required ,client side):
Web application server(one required , server-side):
WampServer
Database(one required, server-side)
MYSQL Server
5.4. Installation Process

Install both Macromedia Dreamweaver, notepad++ and wamp server software on our computer and
local disk.
WSU CSIT
Page 68

5.5. Start-Up Strategy
Steps1
Activate Wampserver from the Desktop or Start up Menu if its not activated.
Click on start ->Wampserver.
Then Click on Wampserver these window and start server click on localhost or phpMyadmin.
In the run Dialog box type the URL of the page localhost/project/index.php after then enter.
WSU CSIT
Page 69
Chapter Six
6.1. Conclusions
So far we were intended in analyzing the existing system of Wolaita Sodo University Student Union
election up to proposing our automate system that solves the difficulties related to the existing
system.The developed website was advantage for the member of the university.
Online voting for Wolaita sodo university student union is wise to vote campus studentsat anywhere
WSU CSIT
Page 70

in every time through the use of internet and other additional technologies if they are only member of
campus. Through this project the voters can vote their representative by entering required
informations and the committee manages all the activities of the voters and candidates not only but
also manage time of election.
6.2. Recommendations
The team member has a recommendation towards the project for modification of some features to
make the systemperfect and more efficient. So anyone who has the intension to update, change or
modify this project can do.The features recommended to add are:
Erasing the voter can go back and make correction, if the correction is needed up to the day of
election end.
Upload student data from registrar.
Student registration.
Tools
In addition to these, any user to use this system, he/ she have to know some knowledge how to use this
system and any concerning organ have to connect internet for the use of system.
REFERENCE
A guide to the project management body of knowledge (PM BOOK GUIDE).project
management institute, Pennsylvania USA Edition 2000
https://www.cusu.cam.ac.uk/elections/system/
https://www.simplyvoting.com
https://www.f1sourcescode.com
https://www.coolmenu.com
WSU CSIT
Page 71
Project title: - Online Voting System for WSU Student Union

Submitted by
GROUP MEMBERS
1.
2.
3.
4.
5.
ID_NO
Hizbayush Dessalew------------------------------NCS/R/606/04
Bezawit Gizaw ..NCS/R/283/04
Bezawit Merihun.NCS/R/1317/04
Edilawit MebratuNCS/R/397/04
Kalab Mesfin NCS/R/636/04
Advisor Mr. Mesay Wana
In partial fulfillment for the award of the degree of BSc in Information

Technology
Wolaita Sodo University
Department of CSIT
Approval:
WSU CSIT
Signature:
Date:
Page 72

Advisor: _________________
________
________
Examiner 1:_______________
________
________
Examiner 2:_______________
________
________
WSU CSIT
Page 73
WSU CSIT
Page 74

Olline Voting System12

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Olline Voting System12

Încărcat de

Drepturi de autor:

Formate disponibile

WSUSU ONLINE VOTING SYSTEM

WOLAITA SODO UNIVERSITY

Advisor Mr. Mesay Wana

WSUSU ONLINE VOTING SYSTEM

WSUSU ONLINE VOTING SYSTEM

WSUSU ONLINE VOTING SYSTEM

2.3.2. Process of the existing system.......................................................................9

WSUSU ONLINE VOTING SYSTEM

State chart modeling.............................................................................................48

4.5 Collaboration modeling...........................................................................................50

WSUSU ONLINE VOTING SYSTEM

The current system

WSUSU ONLINE VOTING SYSTEM

2. Statement of the Problem

Online Voting System For WSU Student Union

WSUSU ONLINE VOTING SYSTEM

Implementation and testing

Advisor Mesay Wana

WSUSU ONLINE VOTING SYSTEM

4.2 Specific objective

Reduce voter duplication.

5. The Scope of the Project

6.1 Data Collection Methods

6.2 Tool to be used or development tools

WSUSU ONLINE VOTING SYSTEM

Client side coding __________________HTML

6.3 Design approach

7. Required Resource with Costs

Dell computer ,CD, flash disk ,

8. Limitation of the Project

WSUSU ONLINE VOTING SYSTEM

WSUSU ONLINE VOTING SYSTEM

2.2 Players in the existing system

Definition of players in the system:

Controls incase if one candidate leave before election.

WSUSU ONLINE VOTING SYSTEM

2.3 Major Functions of the Existing System

Candidates registration including candidates information like,

WSUSU ONLINE VOTING SYSTEM

2.3.2. Process of the existing system

2.4. Business rule

2.5 Report generated in the existing system

WSUSU ONLINE VOTING SYSTEM

2.6 Forms and other documents of the existing systems

The following form shows Executive committees form

WSUSU ONLINE VOTING SYSTEM

2.7 Bottlenecks of the existing system

WSUSU ONLINE VOTING SYSTEM

2.7.2 Security and Controls

2.8. Proposed Solution for the existing System

WSUSU ONLINE VOTING SYSTEM

2.8.1 Functional Requirement

WSUSU ONLINE VOTING SYSTEM

and retrieve data.

Backup and Recovery

WSUSU ONLINE VOTING SYSTEM

3.2 System Requirement Specifications (SRS)

3.2.1 Use case diagram

WSUSU ONLINE VOTING SYSTEM

WSUSU ONLINE VOTING SYSTEM

Candidate, committee, general assembles

This use case is used to authenticate users to the system