Design and Implementation of a Secure Online Voting System for Student Elections (Project Guide)

By EngrHenryTech Publishing · Computer Science

DESIGN AND IMPLEMENTATION OF A SECURE ONLINE VOTING SYSTEM FOR STUDENT UNION ELECTIONS: A COMPLETE PROJECT GUIDE

Departments: Computer Science, Information Technology, Software Engineering, Cyber Security, Computer Engineering, Information Systems

ABOUT THIS GUIDE

This is a detailed project guide and framework for a system design and implementation project, not a finished project or a ready-made system. It gives you a ready-to-adapt Chapter One, a map for your literature review, a full systems analysis and design plan (requirements, the security properties a voting system needs, use cases, database design and architecture), an implementation and testing plan, and guidance for writing your documentation. You build the system yourself and document what you actually built and tested. You will be asked to demonstrate it and explain your code at your defence.

SECTION 1: TOPIC AND ALTERNATIVE TITLES

Main topic:
Design and Implementation of a Secure Web-Based Voting System for Student Union (or Departmental Association) Elections in [Institution]

Alternative titles:
1. A Mobile-Based Voting System with One-Time Password (OTP) Verification for Campus Elections.
2. Design and Implementation of a Voting System with Real-Time Result Collation and Audit Trail.
3. A Biometric (Fingerprint) Voter Authentication Prototype for Student Elections. (Requires hardware)
4. A Web-Based Opinion Poll and Survey System with Anonymous Responses.
5. Design of a Blockchain-Based Voting Prototype: Feasibility and Limitations. (Advanced; discuss with your supervisor)

Important scope note: this project is for small, low-stakes elections, such as student union or departmental elections. Secure national elections involve far more complex legal, technical and security requirements. Experts widely caution that internet voting for public elections carries serious security risks. Say this clearly in your project.

SECTION 2: MODEL CHAPTER ONE

1.1 Background to the Study (model text, rewrite in your own words)

Elections are central to democratic governance, whether in a country, a trade union or a student association. In many Nigerian tertiary institutions, student union and departmental elections are still conducted with paper ballots. Students queue at polling points, ballot papers are counted by hand, and results are collated manually. This process can be slow, expensive and open to disputes over irregularities, such as multiple voting, ballot stuffing, lost ballot papers and errors in counting. Turnout may also be low, because students are busy with lectures, live off campus, or are away on industrial training.

Electronic voting systems use technology to record, store and count votes. Nigeria's Independent National Electoral Commission (INEC) has introduced technology into national elections, including the Bimodal Voter Accreditation System (BVAS) for voter accreditation and the INEC Result Viewing Portal (IReV) for uploading polling-unit results, provided for in the Electoral Act 2022. For smaller elections, such as those of student associations, web-based voting systems can allow eligible voters to vote securely from their phones or computers, count votes automatically, and publish results quickly.

However, a voting system must satisfy demanding requirements. Only eligible voters should be able to vote; each voter should vote only once; votes should be secret, so that no one can link a vote to a voter; votes should not be altered after they are cast; results should be accurate and verifiable; and the system should be available and resistant to attack. Balancing secrecy with verifiability is one of the hardest problems in voting system design. This project designs and implements a secure web-based voting system for student union elections in [Institution], addressing these requirements as far as possible for a small-scale election.

1.2 Statement of the Problem (model)

Student elections in [Institution] are conducted manually, and they face the following problems (confirm each one by interviewing the electoral committee and students, rather than copying this list):
1. Long queues and inconvenience lead to low turnout.
2. Manual counting is slow and prone to error, and results are often disputed.
3. There are opportunities for multiple voting and ballot manipulation.
4. Students on industrial training or living off campus cannot vote.
5. There is no easy way for candidates and observers to verify the process.

1.3 Aim and Objectives

The aim is to design and implement a secure web-based voting system for student union elections in [Institution]. The objectives are to:
1. analyse the existing election process and its weaknesses;
2. design a system that authenticates eligible voters and ensures that each votes only once;
3. preserve ballot secrecy, by separating voters' identities from their votes;
4. implement automatic, accurate vote counting and result publication;
5. maintain an audit log of administrative actions, without compromising ballot secrecy;
6. test the system for correctness, security and usability.

WHAT THE FULL GUIDE CONTAINS

The complete guide continues with:
- significance, scope, limitations and definitions of terms;
- a literature review map: the security requirements of voting systems, technology in Nigerian elections, authentication and web security, and how to review related systems;
- a full systems analysis and design plan: requirements, a design that keeps votes secret while enforcing one person one vote, use cases, the database design and the architecture;
- an implementation plan: technology choices, security essentials (OTPs, transactions, rate limiting) and a test plan including security and load tests;
- a Chapter Five guide, source-code advice, real starting references, and a checklist of common supervisor corrections.

Please note: this is a research guide and framework to help you plan and write your own project. It does not contain invented data or results. You build the system yourself and document what you actually built and tested.