Skip to content

Software Engineering Final Year Topic: Investigation of Software Defect Prediction Leakage

This Software Engineering final year project investigates measuring evaluation bias when related code versions cross train-test splits, focusing on software lifecycle evidence, reproducible verification and the limits of the chosen engineering method.

Why choose this project topic?

The topic gives measuring evaluation bias when related code versions cross train-test splits a measurable software-engineering purpose beyond building another application. Comparing prediction error, optimism gap and split sensitivity 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 prediction error, optimism gap and split sensitivity when measuring evaluation bias when related code versions cross train-test splits?

Choose an owned or permissively licensed teaching codebase, agree the controlled changes and validation plan, and narrow the evidence for measuring evaluation bias when related code versions cross train-test splits.

Proposed project objectives

  1. 01Define the software artifact, expected behaviour and evidence needed for measuring evaluation bias when related code versions cross train-test splits.
  2. 02Use a permitted repository dataset, compare random and chronological grouping and evaluate untouched releases.
  3. 03Compare prediction error, optimism gap and split sensitivity and document limitations and reproducibility.

A suggested research approach

Use a permitted repository dataset, compare random and chronological grouping and evaluate untouched releases. Confirm repository licences and use owned or disposable environments for mutations. Record versions, fixtures and reference outcomes, compare prediction error, optimism gap and split sensitivity with a documented baseline, and distinguish a passing bounded check from evidence about all possible software behaviour.

What you will need

  • Licensed defect dataset
  • Version metadata
  • Modelling tools

Keep your project scope clear

Predictions do not establish code quality or justify judging individual developers.

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 4Presentation and Analysis of Results
  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.