Skip to content

Information Systems Final Year Topic: Design and Evaluation of Student Association Budget Transparency

This Information Systems final year project examines linking planned activities to recorded expenditure and supporting documents, connecting organisational requirements with a bounded information-system design.

Why choose this project topic?

The topic addresses linking planned activities to recorded expenditure and supporting documents, a concrete information need with visible users, records and decisions. Evaluating variance accuracy, evidence completeness and report comprehension lets a student explain how the proposed workflow supports its users and where manual judgement is still necessary.

How can student association budget transparency improve linking planned activities to recorded expenditure and supporting documents when assessed using variance accuracy, evidence completeness and report comprehension?

Agree an accessible fictional or authorised organisational setting, the relevant user roles and a feasible evaluation workload for linking planned activities to recorded expenditure and supporting documents.

Proposed project objectives

  1. 01Map the users, records and decision requirements involved in linking planned activities to recorded expenditure and supporting documents.
  2. 02Create fictional budgets and transactions, implement approval and variance reports and test corrections, missing evidence and overspending.
  3. 03Compare variance accuracy, evidence completeness and report comprehension with a documented manual or baseline process.

A suggested research approach

Create fictional budgets and transactions, implement approval and variance reports and test corrections, missing evidence and overspending. Document the existing or fictional process before designing the information model. Test normal and exceptional cases, examine variance accuracy, evidence completeness and report comprehension, and retain an audit of assumptions so the evaluation distinguishes system behaviour from unverified organisational claims.

What you will need

  • Synthetic budgets
  • Fictional receipts
  • Approval policy

Keep your project scope clear

The tool does not audit real accounts or establish that recorded spending was legitimate. 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.