Skip to content

Computer Engineering Final Year Topic: Cryptographic-Hash Chaining for Detecting Changes in Synthetic Voting Records

This Computer Engineering final year project examines detection of specified record changes through hash chaining in a synthetic voting-log demonstration through fictional event records created and altered inside a local teaching environment, with a defined comparison that can be adjusted to available access and supervisor guidance.

Why choose this project topic?

The focus on detection of specified record changes through hash chaining in a synthetic voting-log demonstration gives the project a specific question and a visible evidence trail. The project can demonstrate one integrity mechanism with repeatable tampering examples and visible assumptions. A bounded design makes it possible to explain what the selected evidence supports without presenting a proposal as a completed study.

Can a hash-chained synthetic event log identify the specified accidental record edits in a voting-system teaching prototype?

Agree the event format, change cases and assumptions about log checkpoints, the evidence window and the analysis plan with the supervisor before fixing the final title or recruiting participants.

Proposed project objectives

  1. 01Define the concepts and population needed to study detection of specified record changes through hash chaining in a synthetic voting-log demonstration.
  2. 02Document or measure the proposed evidence from fictional event records created and altered inside a local teaching environment.
  3. 03Interpret the evidence using the stated comparison and explain its limits.

A suggested research approach

Implement a documented hash-chain demonstration using a maintained cryptographic library and test controlled edits, deletions and reordering Use fictional event records created and altered inside a local teaching environment only after confirming access, eligibility and a workable time window. Compare verification outputs for each altered and unaltered dataset, record the exact change model and keep the key-management and trust assumptions explicit Keep the protocol, exclusions and measurement definitions in an audit trail; discuss missing or contradictory evidence instead of treating it as confirmation.

What you will need

  • A local development environment, an established library and synthetic event-log fixtures
  • A supervisor-agreed protocol defining detection of specified record changes through hash chaining in a synthetic voting-log demonstration and the relevant measures or coding rules
  • A dated evidence log and a plan for confidentiality, permissions and any required ethics review

Keep your project scope clear

The proposed design can describe or compare only the evidence it collects. A hash chain alone does not prove who created a record, prevent all edits or secure a real voting system. Do not extend a local, simulated or self-reported result to a wider population without a design that supports that inference.

Computer Engineering project chapter outline

Use this outline as a starting point. You can edit the chapter titles to match your department’s format during setup.

  1. Chapter 1Introduction
  2. Chapter 2Literature Review
  3. Chapter 3System Analysis and Design
  4. Chapter 4System Implementation and Testing
  5. Chapter 5Summary, Conclusion and Recommendations

Turn this topic into your own final year project.

Your title, department, research question and outline are ready. Add your institution, personalise the details and continue to your project workspace.

Generate the Complete Project Generation uses your word balance. Review the draft and supply your own verified research findings.