Why choose this project topic?
The focus on audit-log completeness for defined administrative actions in an isolated ballot-system prototype gives the project a specific question and a visible evidence trail. A field-by-field completeness check examines accountability and data minimisation together. A bounded design makes it possible to explain what the selected evidence supports without presenting a proposal as a completed study.
Which defined administration events are recorded with sufficient context in an isolated electronic-voting prototype?
Agree the administrative event types, retained fields and local storage design, the evidence window and the analysis plan with the supervisor before fixing the final title or recruiting participants.
Proposed project objectives
- 01Define the concepts and population needed to study audit-log completeness for defined administrative actions in an isolated ballot-system prototype.
- 02Document or measure the proposed evidence from synthetic administration events and generated system records.
- 03Interpret the evidence using the stated comparison and explain its limits.
A suggested research approach
Define required log fields such as event type, timestamp, actor role and outcome; generate each event through the prototype and preserve the original record Use synthetic administration events and generated system records only after confirming access, eligibility and a workable time window. Compare generated records against the event specification and test whether sensitive ballot choices or personal identifiers are unnecessarily written 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 prototype, a written event catalogue and synthetic action sequences
- A supervisor-agreed protocol defining audit-log completeness for defined administrative actions in an isolated ballot-system prototype 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 complete log for tested actions does not show that all attacks would be detected or that an election could be audited independently. Do not extend a local, simulated or self-reported result to a wider population without a design that supports that inference.
Information Systems project chapter outline
Use this outline as a starting point. You can edit the chapter titles to match your department’s format during setup.
- Chapter 1Introduction
- Chapter 2Literature Review
- Chapter 3System Analysis and Design
- Chapter 4System Implementation and Testing
- 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.