Skip to content

Computer Science Final Year Topic: Design and Evaluation of Versioned Coursework File Storage

This Computer Science final year project investigates tracking coursework revisions without duplicating unchanged file blocks, with an explicit prototype scope and a reproducible evaluation plan.

Why choose this project topic?

The practical value of this topic lies in tracking coursework revisions without duplicating unchanged file blocks. It gives a student a demonstrable computing problem, with deduplication ratio, restore time and corruption detection providing concrete evidence for a critical project discussion.

What storage savings and restoration costs result from content-addressed coursework versioning?

Agree the available tools, workload size and evaluation criteria with your supervisor; adapt tracking coursework revisions without duplicating unchanged file blocks to a clearly bounded institutional or laboratory setting.

Proposed project objectives

  1. 01Specify the requirements and assumptions for tracking coursework revisions without duplicating unchanged file blocks.
  2. 02Chunk synthetic document versions, store hashed blocks and reconstruct selected revisions while injecting missing blocks and corrupted manifests.
  3. 03Evaluate deduplication ratio, restore time and corruption detection against a documented baseline and discuss failure cases.

A suggested research approach

Chunk synthetic document versions, store hashed blocks and reconstruct selected revisions while injecting missing blocks and corrupted manifests. Record the chosen implementation, dataset construction and repeatable test conditions before comparing deduplication ratio, restore time and corruption detection. 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 versioned files
  • Local object store
  • Hash verification scripts

Keep your project scope clear

Content hashes detect some changes but do not provide encryption or authorship verification. 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.