Skip to content

Information Systems Final Year Topic: Design and Evaluation of University Procurement Approval Trail

This Information Systems final year project examines making procurement requests, reviews and fulfilment status auditable, connecting organisational requirements with a bounded information-system design.

Why choose this project topic?

The topic addresses making procurement requests, reviews and fulfilment status auditable, a concrete information need with visible users, records and decisions. Evaluating approval traceability, incomplete requests and workflow duration lets a student explain how the proposed workflow supports its users and where manual judgement is still necessary.

How can university procurement approval trail improve making procurement requests, reviews and fulfilment status auditable when assessed using approval traceability, incomplete requests and workflow duration?

Agree an accessible fictional or authorised organisational setting, the relevant user roles and a feasible evaluation workload for making procurement requests, reviews and fulfilment status auditable.

Proposed project objectives

  1. 01Map the users, records and decision requirements involved in making procurement requests, reviews and fulfilment status auditable.
  2. 02Use fictional requisitions and supplier offers, implement approval stages and test split requests, missing quotations and amended specifications.
  3. 03Compare approval traceability, incomplete requests and workflow duration with a documented manual or baseline process.

A suggested research approach

Use fictional requisitions and supplier offers, implement approval stages and test split requests, missing quotations and amended specifications. Document the existing or fictional process before designing the information model. Test normal and exceptional cases, examine approval traceability, incomplete requests and workflow duration, and retain an audit of assumptions so the evaluation distinguishes system behaviour from unverified organisational claims.

What you will need

  • Fictional requisitions
  • Approval matrix
  • Synthetic fulfilment records

Keep your project scope clear

The prototype cannot determine procurement legality or endorse a supplier. 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.