Areas of Expertise

Advisory Areas

Four domains where I have the deepest experience. If any of these match a challenge you're facing — in requirements quality, traceability, process design, or team structure — I'm happy to think through it with you.

Software & System Requirements Development

After 14 years writing requirements for ADAS ECUs, in-cabin sensing, and safety-critical rail HMI, I have a strong view on what good looks like at every level of the requirements chain. Whether you're rethinking your elicitation approach, improving spec quality, or navigating SYS.2/SWE.1 for the first time — this is where I can offer the most direct perspective.

  • Elicitation approaches and workshop design
  • SYS.2 / SWE.1 quality and structure
  • Requirements specifications, use cases, interface definitions
  • ADAS, in-cabin sensing, and rail HMI domains

Traceability & Tooling

Traceability architectures and requirements tool configurations are something I've built from scratch across multiple programmes. If your team is fighting DOORS customisations, struggling with Codebeamer setup, or needs a coherent metrics story — I know these environments well and can help you think through what an effective architecture looks like.

  • Traceability architecture and coverage strategies
  • Tool environments: DOORS, DOORS NG, PTC Integrity, Reqtify, Codebeamer, EA
  • Custom dashboards, metrics, and Python-based reporting
  • Change control and impact analysis approaches

ASPICE & Functional Safety Process Design

I've designed requirements processes aligned with ASPICE 3.1/4.0, ISO 26262, EN 50128, and GS95014 — and sat in the room during assessments. If you're facing a gap analysis, a process tailoring exercise, or an upcoming audit and want a senior view on what assessors actually look for, this is a useful conversation to have.

  • ASPICE 3.1/4.0 requirements process design
  • ISO 26262 / EN 50128 / GS95014 alignment and tailoring
  • Gap analysis and audit preparation approach
  • Review workflows, document release, and quality gate design

Requirements Team Leadership

Leading an RE team of 6+ engineers across multiple active programmes taught me where team-level process breaks down under real project pressure. If you're scaling an RE function, rolling out a new process, or mentoring someone into a lead role — I'm glad to share what worked and what didn't.

  • Team structure and task distribution strategies
  • Progress tracking and process adherence at scale
  • Mentoring engineers and leads into new processes
  • RE function setup for growing teams