01 · Requirements

Turning stakeholder needs into contractual design and build specifications.

Working with stakeholders — client, operator, regulator, supplier — until the need is unambiguous, then baselining it under formal change control. The output: a requirements specification that can be used to contract a designer or constructor.

From the field

Produced the Client Requirements Document Satisfaction Report for TRU Digital, the ETCS resignalling of the Transpennine Route.

Capability

  • Requirements capture & elicitation
  • Requirements analysis & derivation
  • Baseline & formal change management
  • Client, Route & Detailed Route Requirements Documents
  • Stakeholder & supplier requirements management
  • End-to-end traceability

Tools

IBM DOORS Next DOORS Classic IBM ELM

Capability

  • V&V Management Plans
  • Use-case & acceptance validation
  • Stage-gate & progressive assurance reviews
  • Real-environment validation testing
02 · Validation

Build the right thing.

  • Are the requirements correct?
  • Has the stakeholder reviewed and agreed them?
  • Are they unambiguous? Are they achievable?
  • Has the contractor reviewed and accepted them?
  • Acceptance criteria drive cost too — have they been articulated and agreed with the contractor?
  • Have all use cases and test scenarios been identified and coverage checked?
  • Do you have a master deliverables list, setting out all the documentation the contractor must provide to prove they meet the requirements?
Why it matters

If you can't answer these questions, get ready for contract variations in the delivery phase.

03 · Verification

Did we build the thing right?

As a minimum, verification must be done at the end of detailed design, before starting construction, and after construction, to prove it was built right.

Failing to verify the detailed design against the requirements leads to exponentially more expensive rework once metal has been cut and concrete has been poured. In the worst cases, non-compliances are simply too expensive to fix, your customers are furious, and your company's reputation is in the dirt.

But a compliant design doesn't automatically give you a compliant construction. Deliberate or accidental deviations from the design can have unintended but serious consequences for the safety, functionality and performance of the emergent system. Verifying the construction against the requirements — by inspection, test, demonstration and analysis, against agreed acceptance criteria — is a crucial input to assurance before the system can go into service.

From the field

Built and ran the V&V function for Ottawa's Light Rail Transit System, supporting its C$60M and C$202M milestone payments.

Capability

  • Requirements Verification Matrices
  • Interface verification
  • Technical compliance reporting
  • Test coverage & traceability reporting

Tools

IBM Test Manager DOORS traceability

Capability

  • Requirements changes
  • Compliance changes
  • Top-down and bottom-up impact assessment
  • Cost challenges
  • Contract variations
04 · Change Management

It's ok if things change, as long as it's under control.

Mistakes are made, opportunities arise, risks materialise, technology advances, people move on, budgets are cut (rarely increased). Engineers and project managers face these challenges on a daily basis. How they deal with them makes or breaks careers.

Change must be acknowledged and controlled within the engineering discipline as well as co-ordinated with project management, commercial departments and suppliers. In practice, this means clearly identifying change proposals, having an efficient decision-making process to quickly approve or reject them, and working with contract managers to vary supplier contracts as necessary.

From the field

Implemented a Requirements Change Request process on TRU Digital, detailed within the Scope Management Plan.

05 · Assurance

Compiling the evidence into a case that stands up to independent scrutiny.

Structuring everything requirements and V&V have produced against a recognised standard, so an independent assessor can trust the conclusion without redoing the work — built in through stage-gate reviews, not bolted on at the end.

From the field

Ensured TRU Digital was compliant with UK ETCS standards under the GB Generic Requirements Suite.

Standards

EN 50126 EN 50128 EN 50129 ISO/IEC/IEEE 15288

Capability

  • Systems Engineering Management Plans
  • Progressive & stage-gate assurance
  • Interface & Technical Interface Register management
  • Model-Based Systems Engineering (SysML/UML)
How it fits together

Five stage gates, the same way every time.

01

Capture

Stakeholder and system requirements, captured at source.

02

Baseline

Structured and under formal change management in DOORS.

03

Verify

Matrices confirm the design meets every requirement.

04

Validate

Confirmation, in the real environment, that it's what was needed.

05

Assure

Evidence compiled into a case that stands up to scrutiny.

Not sure which discipline your programme needs?

Most programmes need more than one. A short call will tell you where the risk sits.