Skip to content

Software Engineering Final Year Topic: Investigation of Code Review Checklist Coverage

This Software Engineering final year project investigates comparing detection of planted defects using different review guides, focusing on software lifecycle evidence, reproducible verification and the limits of the chosen engineering method.

Why choose this project topic?

The topic gives comparing detection of planted defects using different review guides a measurable software-engineering purpose beyond building another application. Comparing defect recall, review time and reviewer agreement supports a defensible account of maintainability, testing or delivery trade-offs, with concrete examples of both useful findings and cases the method misses.

How do the selected software-engineering methods affect defect recall, review time and reviewer agreement when comparing detection of planted defects using different review guides?

Choose an owned or permissively licensed teaching codebase, agree the controlled changes and validation plan, and narrow the evidence for comparing detection of planted defects using different review guides.

Proposed project objectives

  1. 01Define the software artifact, expected behaviour and evidence needed for comparing detection of planted defects using different review guides.
  2. 02Use original small patches, conduct approved review tasks and separate correctness, maintainability and security observations.
  3. 03Compare defect recall, review time and reviewer agreement and document limitations and reproducibility.

A suggested research approach

Use original small patches, conduct approved review tasks and separate correctness, maintainability and security observations. Confirm repository licences and use owned or disposable environments for mutations. Record versions, fixtures and reference outcomes, compare defect recall, review time and reviewer agreement with a documented baseline, and distinguish a passing bounded check from evidence about all possible software behaviour.

What you will need

  • Original teaching patches
  • Known defect labels
  • Consent-based protocol

Keep your project scope clear

The study must not rank real employees or infer general developer competence.

Software 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 3Research Methodology
  4. Chapter 4Data Presentation, Analysis and Discussion of Findings
  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.