STAGE 1: Elicit before prescribing
Concept: Ask about current decisions, exceptions and evidence.
Task: Draft six open interview questions for a learner and an administrator. Mark assumptions awaiting validation.
Acceptance: Questions do not presuppose that a new app is the solution.

My assumptions:

My work / file link:

My checks and results:

What I changed:


STAGE 2: Model the current process
Concept: A process map exposes handoffs and rework.
Task: Map request, eligibility check, approval and notification. Add the rejected and missing-information branches.
Acceptance: Every branch has a trigger and accountable role.

My assumptions:

My work / file link:

My checks and results:

What I changed:


STAGE 3: Specify testable needs
Concept: Requirements state a needed behavior or constraint.
Task: Write eight requirements with IDs, sources, priority and acceptance examples.
Acceptance: Replace words such as fast or easy with observable criteria.

My assumptions:

My work / file link:

My checks and results:

What I changed:


STAGE 4: Validate the proposal
Concept: Traceability connects a problem to its test.
Task: Create a requirement-to-test matrix and compare a process-only change with a software change.
Acceptance: Every high-priority requirement has a source and a verification method.

My assumptions:

My work / file link:

My checks and results:

What I changed:
