HSC Enterprise Computing study materials
HSC Enterprise Computing study resources

HSC Enterprise Computing: The Enterprise Computing Project: Managing Scope, Risk and Evidence

HSC Enterprise Computing · Work through your exam, one topic at a time.

All guide sections

The Enterprise Computing Project: Managing Scope, Risk and Evidence

What you must understand

The enterprise computing project is assessed as a process, not only a product. You must be able to describe and justify each phase: initiation and feasibility, requirements gathering, planning, design, development or acquisition, implementation, testing, training, and evaluation with maintenance.

Key concepts to name and apply:

  • Project management – scope, time, cost and quality constraints; work breakdown structures; Gantt and critical path scheduling.
  • Methodologies – waterfall versus iterative or agile approaches, and why an enterprise context often mixes them.
  • Requirements – functional versus non-functional, and how they are validated with stakeholders.
  • Risk management – identifying, assessing likelihood and impact, and planning mitigation.
  • Change and training – user acceptance testing, documentation, support models and resistance to change.
  • Evaluation – success criteria set early, measured against the original need, not just whether the system runs.

Traps in questions

  1. Listing phases without explaining why each matters or what its outputs are.
  2. Ignoring non-functional requirements such as performance, security and usability.
  3. Treating testing as a single final step rather than continuous and layered (unit, integration, system, acceptance).
  4. Forgetting post-implementation review and ongoing maintenance.
  5. Describing risks without a mitigation or owner.

Rule of thumb

For any project question, trace one requirement from stakeholder need → requirement → design decision → test → evaluation evidence. If you can complete that chain, you demonstrate understanding rather than recall.

Worked example

A school plans an integrated student management system. A strong response defines success criteria (e.g. reduced duplicate data entry), identifies risks (data migration errors, staff resistance), proposes mitigation (staged migration, pilot testing, training), and specifies acceptance testing and a post-implementation review.