Skip to content

Computer Science Final Year Topic: Design and Evaluation of Event-Sourced Equipment Checkout

This Computer Science final year project investigates reconstructing borrowing history from an append-only equipment event log, with an explicit prototype scope and a reproducible evaluation plan.

Why choose this project topic?

The practical value of this topic lies in reconstructing borrowing history from an append-only equipment event log. It gives a student a demonstrable computing problem, with projection correctness, replay time and unresolved state conflicts providing concrete evidence for a critical project discussion.

Can event replay reproduce correct equipment availability after corrections and late returns?

Agree the available tools, workload size and evaluation criteria with your supervisor; adapt reconstructing borrowing history from an append-only equipment event log to a clearly bounded institutional or laboratory setting.

Proposed project objectives

  1. 01Specify the requirements and assumptions for reconstructing borrowing history from an append-only equipment event log.
  2. 02Model checkout and return events for fictional equipment, replay histories and compare projections after duplicate, out-of-order and compensating events.
  3. 03Evaluate projection correctness, replay time and unresolved state conflicts against a documented baseline and discuss failure cases.

A suggested research approach

Model checkout and return events for fictional equipment, replay histories and compare projections after duplicate, out-of-order and compensating events. Record the chosen implementation, dataset construction and repeatable test conditions before comparing projection correctness, replay time and unresolved state conflicts. Keep development and evaluation cases separate where possible, and retain failed cases in the analysis rather than reporting only successful demonstrations.

What you will need

  • Synthetic equipment event histories
  • Event-store prototype
  • Expected state transition cases

Keep your project scope clear

The prototype does not establish a real institution's asset ownership or borrower liability. A project write-up does not supply a working application.

Computer Science 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.