Skip to content

Information Systems Final Year Topic: Design and Evaluation of Building Maintenance Request Lifecycle

This Information Systems final year project examines tracking maintenance requests from initial report to verified closure, connecting organisational requirements with a bounded information-system design.

Why choose this project topic?

The topic addresses tracking maintenance requests from initial report to verified closure, a concrete information need with visible users, records and decisions. Evaluating closure completeness, response intervals and reopened cases lets a student explain how the proposed workflow supports its users and where manual judgement is still necessary.

How can building maintenance request lifecycle improve tracking maintenance requests from initial report to verified closure when assessed using closure completeness, response intervals and reopened cases?

Agree an accessible fictional or authorised organisational setting, the relevant user roles and a feasible evaluation workload for tracking maintenance requests from initial report to verified closure.

Proposed project objectives

  1. 01Map the users, records and decision requirements involved in tracking maintenance requests from initial report to verified closure.
  2. 02Create fictional property requests, implement assignment and closure evidence and test reopened faults and competing priority rules.
  3. 03Compare closure completeness, response intervals and reopened cases with a documented manual or baseline process.

A suggested research approach

Create fictional property requests, implement assignment and closure evidence and test reopened faults and competing priority rules. Document the existing or fictional process before designing the information model. Test normal and exceptional cases, examine closure completeness, response intervals and reopened cases, and retain an audit of assumptions so the evaluation distinguishes system behaviour from unverified organisational claims.

What you will need

  • Synthetic maintenance requests
  • Fictional asset list
  • Service workflow rules

Keep your project scope clear

Priority categories are administrative assumptions and do not replace qualified safety inspection. Project writing does not provide an operational system.

Information Systems 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.