Requirements analysis (IREB)
For organisations that want to base a software project, tender or system replacement on a solid requirements foundation.
Updated: 2026-11
We elicit, document and validate requirements following the IREB Certified Professional for Requirements Engineering method: identify stakeholders, elicit requirements in workshops, model processes in BPMN 2.0, write acceptance criteria and deliver a requirements catalogue the client can formally sign off. A basis for tenders, development or standard software.
Most software projects fail not on technology but on requirements that were unclear, contradictory or never agreed. They surface late, at acceptance or in operation, when changes cost most.
Requirements often exist only in fragments: in people’s heads, emails and old concepts. Without an agreed, signed-off catalogue there is no basis for a fair tender, a realistic estimate or an unambiguous acceptance.
What you get
Stakeholder and context analysis
Who is affected, who decides, which systems and interfaces set the scope.
Requirements catalogue
Functional and non-functional requirements, unambiguous, prioritised and with source.
BPMN 2.0 process models
Current and target processes that business and development read the same way.
Acceptance criteria
Verifiable criteria per requirement that later drive testing and acceptance.
Glossary and traceability
Consistent terms and a link from goal through requirement to test case.
Sign-off version
A catalogue in a form the client can formally approve.
How it runs
- 01
Clarify context
Record goals, system boundaries, stakeholders and constraints.
- 02
Elicit
Interviews, workshops and document analysis with the business units.
- 03
Document and model
Formulate requirements, model processes, resolve conflicts.
- 04
Validate and sign off
Review with stakeholders, clean-up and formal approval.
Price framing
Effort depends on the number of business units, processes and interfaces. After a free initial conversation you receive a fixed-scope proposal with clear outputs.
Indicative, not a binding quote — the frame is confirmed during scoping.
What drives the price? → Cost guide
Parent service: Custom Software Engineering
FAQ
What does “following IREB” mean?
We work to the International Requirements Engineering Board syllabus (CPRE): systematic elicitation, documentation, validation and management of requirements with consistent terminology.
Is the catalogue suitable for a public tender?
Yes, as the basis for a specification. Structuring the tender documents under procurement law remains the contracting authority’s responsibility.
Agile or traditional?
Both. In agile projects we produce epics and user stories with acceptance criteria; in HERMES or waterfall projects a catalogue ready for sign-off.
Do you also implement afterwards?
On request. The catalogue is written so that any supplier can build on it, without being tied to us.
Requirements analysis (IREB)
For organisations that want to base a software project, tender or system replacement on a solid requirements foundation.