Business Analysis
A requirement set that is complete, traceable and testable — so the system that gets built is the system that was needed.
Requirements elicitation, process mapping and specification that turn what stakeholders describe into something a team can actually build and test.
What this service is usually brought in to fix
Requirements captured as wishes, not specifications
Statements like 'the system should be user friendly' cannot be built, estimated or tested, yet they end up in contracts.
The documented process is not the real process
Teams have local workarounds that never reach the specification, so the delivered system fails on day one of real use.
No traceability from need to test
When acceptance testing starts, nobody can prove which requirement a given test covers, or which requirements are untested.
What the service covers
- Stakeholder identification and structured elicitation workshops
- As-is process mapping and gap analysis
- Functional and non-functional requirement specification
- User stories, use cases and acceptance criteria
- Data modelling and integration requirements
- Requirements traceability matrix through to test cases
What you receive
- Stakeholder and process maps
- Business requirements and software requirements specification
- Prioritised backlog with acceptance criteria
- Requirements traceability matrix
- Wireframes or journey maps where they aid agreement
How the work runs
Each stage produces something reviewable, so scope, risk and progress stay visible to your team throughout.
Elicit
Run workshops and interviews with the people who do the work, not only those who describe it, and observe the process in place.
Model
Document the as-is process, data and integrations, and identify gaps, exceptions and volumes.
Specify
Write requirements that are unambiguous, prioritised and testable, with non-functional needs stated explicitly.
Validate
Walk the specification back through stakeholders and sign it off before build, then maintain traceability through delivery.
Where we apply it
- Government service delivery
- Healthcare administration
- Education and academic administration
- Financial services operations
The controls that apply
- Requirements are versioned and change-controlled after baseline.
- Data-protection and retention requirements are captured up front, not retrofitted.
- Accessibility requirements are specified as testable criteria.
Frequently asked
If your question is not here, ask it directly — we would rather answer it before a proposal than after a contract.
Ask a questionYes, and that is often the better sequence. Understanding the process first frequently changes the conclusion about what — or whether — to build.
What this is usually combined with
Discuss your Business Analysis requirement
Tell us the outcome you need and the constraints you are working within. We will respond with a scoped approach and the documentation your evaluation process requires.