Episode Details

Requirements Engineering Fundamentals - Part 1

We kick off a multi-part series on requirements engineering by exploring what requirements actually are and why they matter - even for Agilists. Jeff shares his medical device expertise while Luca brings his automotive and aerospace background to discuss the different levels of requirements (from high-level user needs to testable system requirements), the importance of traceability, and why proper tooling beats Word and Excel every time.

We dig into practical aspects like the EARS format for writing requirements, the crucial distinction between requirements and design choices, and why glossaries aren't as boring as they sound. Along the way, we tackle the tension between regulatory compliance and actual engineering value, emphasizing that documentation should be an artifact of diligent work - not the work itself. Whether you're in safety-critical industries or just want to build better products, understanding requirements engineering helps manage complexity and prevent costly mistakes.

Key Topics

• [02:30] What is requirements engineering and why it matters beyond safety-critical industries
• [06:45] Don't Agilists hate requirements? Debunking the myth and discussing iteration vs. waterfall
• [11:20] The hierarchy of requirements: user needs, system requirements, and subsystem requirements
• [18:00] Requirements vs. design choices: where to draw the line and why it matters for testing
• [24:15] Writing good requirements: EARS format, must vs. shall vs. may, and the value of glossaries
• [32:40] Traceability: linking requirements across levels and to test cases
• [40:30] Why Word and Excel don't cut it: the case for proper requirements management tools
• [48:20] Risk analysis and mitigation in safety-critical development
• [52:00] Documentation as artifact of diligent work, not the work itself

Notable Quotes

"The whole agile movement was a reaction to the one time through the requirements specification build test loop that took several years. By the time you got to the end, the requirements no longer applied." — Jeff

"Do not use an LLM to manage requirements. Do use the LLM to write tools that help you manage requirements." — Luca

"I view any medical device that I work on as if it's going to be used on my child. What do I need to do to convince myself that it is safe and effective? Once I have done that, if there are remaining boxes to check to get it through FDA, I will check those boxes." — Jeff

Resources Mentioned

• EARS (Easy Approach to Requirements Syntax) - A grammar format for writing clear, verifiable requirements that constrains how requirements are written to reduce ambiguity
• FDA Guidance on Agile Development - Regulatory guidance describing how to do Agile development in medical device context
• ISO 26262 - Automotive safety standard mentioned as having similar traceability requirements to medical devices
• DO-178B - Aerospace software safety standard with similar requirements engineering principles

You can find Jeff at https://jeffgable.com.
You can find Luca at https://luca.engineer.

Want to join the agile Embedded Slack? Click here

Are you looking for embedded-focused trainings? Head to https://agileembedded.academy/
Ryan Torvik and Luca have started the Embedded AI podcast, check it out at

Listen Now