Skip to content

Software Engineering Final Year Topic: Investigation of Architecture Decision Record Use

This Software Engineering final year project investigates checking whether fictional design records explain later maintenance choices, focusing on software lifecycle evidence, reproducible verification and the limits of the chosen engineering method.

Why choose this project topic?

The topic gives checking whether fictional design records explain later maintenance choices a measurable software-engineering purpose beyond building another application. Comparing decision comprehension, missing assumptions and task time 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 decision comprehension, missing assumptions and task time when checking whether fictional design records explain later maintenance choices?

Choose an owned or permissively licensed teaching codebase, agree the controlled changes and validation plan, and narrow the evidence for checking whether fictional design records explain later maintenance choices.

Proposed project objectives

  1. 01Define the software artifact, expected behaviour and evidence needed for checking whether fictional design records explain later maintenance choices.
  2. 02Create mock decisions with varied rationale detail, run approved retrieval tasks and assess uncertainty recognition.
  3. 03Compare decision comprehension, missing assumptions and task time and document limitations and reproducibility.

A suggested research approach

Create mock decisions with varied rationale detail, run approved retrieval tasks and assess uncertainty recognition. Confirm repository licences and use owned or disposable environments for mutations. Record versions, fixtures and reference outcomes, compare decision comprehension, missing assumptions and task time with a documented baseline, and distinguish a passing bounded check from evidence about all possible software behaviour.

What you will need

  • Fictional decision records
  • Maintenance scenarios
  • Consent-based protocol

Keep your project scope clear

Document quality does not establish that the original architecture was correct.

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.