Skip to content

Computer Science Final Year Topic: Design and Evaluation of Loss-Tolerant Messaging Prototype

This Computer Science final year project investigates delivering classroom announcements despite intermittent connections, with an explicit prototype scope and a reproducible evaluation plan.

Why choose this project topic?

The practical value of this topic lies in delivering classroom announcements despite intermittent connections. It gives a student a demonstrable computing problem, with duplicate displays, delivery delay and retry traffic providing concrete evidence for a critical project discussion.

Which acknowledgement and retry scheme avoids duplicate display after connection failure?

Agree the available tools, workload size and evaluation criteria with your supervisor; adapt delivering classroom announcements despite intermittent connections to a clearly bounded institutional or laboratory setting.

Proposed project objectives

  1. 01Specify the requirements and assumptions for delivering classroom announcements despite intermittent connections.
  2. 02Implement message identifiers and delivery acknowledgements, simulate lost responses and repeated sends and compare client-visible histories with the intended event log.
  3. 03Evaluate duplicate displays, delivery delay and retry traffic against a documented baseline and discuss failure cases.

A suggested research approach

Implement message identifiers and delivery acknowledgements, simulate lost responses and repeated sends and compare client-visible histories with the intended event log. Record the chosen implementation, dataset construction and repeatable test conditions before comparing duplicate displays, delivery delay and retry traffic. 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 announcements
  • Network fault simulator
  • Two local message clients

Keep your project scope clear

Delivery in a laboratory does not guarantee emergency communication reliability. 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.