Hardware Podcasts

E94 Requirements Engineering, part 1: Fundamentals

The Pragmatic Embedded Podcast · 15 Apr 2026 · 47m

What this episode covers

Jeff Gable, a medical device consultant, and Luca, with automotive and aerospace experience, discuss the fundamentals of requirements engineering for safety-critical products. They explain the hierarchy from user needs to system requirements, emphasizing the EARS format and the critical distinction between verifiable requirements and design choices. The hosts argue against using Word or Excel for complex traceability, advocating instead for dedicated requirements management tools to ensure regulatory compliance and engineering rigor.

Most relevant to

early-stage companies and companies scaling up

Topics

Mentioned

Also
FDA, EARS, ISO 26262, DO-178B, Claude Opus, Notion, Oshlin

Related episodes from other shows

Other shows on the same ground, closest first.

  • Embedded.fm · 1h 09m

    67: Software for Things That Can Kill People

    Hosts Chris White and Elecia White discuss the rigorous regulatory processes for safety-critical software, drawing on their experiences with the FAA (DO-178B) and FDA (510k, PMA) for medical devices and avionics. They explain how hazard analysis determines certification levels, the necessity of extensive documentation and traceability, and the tension between agile development and waterfall compliance. The conversation highlights the ethical responsibility of engineers to push back against unsafe deadlines, the use of hardware compartmentalization (FPGAs, voting systems) to ensure safety, and the legal liabilities associated with product failures.

    Certification & complianceMechanical engineering
    8 chapters

  • OnTrack · 44m

    Altium Requirements Portal: Simplifying Engineering Docs

    Marco Witzmann, Head of Requirements Portal at Altium, explains how the Requirements Portal integrates with Altium Develop to solve engineering documentation chaos. He details the tool's ability to manage complex requirements, trace them to specific PCB components, and verify compliance through structured workflows. Witzmann highlights the shift from manual spreadsheet tracking to a unified platform that supports parametric requirements and seamless design reviews.

    EDA & CAD toolsDesign for manufacturing & NPI
    9 chapters

  • Global Medical Device Podcast · 32m

    V&V Activities from a Verification Engineer POV - How Hard Could It Be?

    Niki Price, a Medical Device Guru at Greenlight Guru with 15 years of experience, explains the critical distinction between design verification (testing design inputs) and design validation (testing user needs). She details the verification engineer's workflow, including managing complex trace matrices, writing protocols, and handling anomalies, while contrasting the inefficiencies of manual Excel-based systems with the automation of Greenlight Guru. Price highlights common pitfalls such as ambiguous requirements, version control errors, and the emotional toll of field failures, advocating for rigorous checks and balances in the design assurance process.

    Validation & product-market fitQuality & yield
    8 chapters

  • Embedded.fm · 1h 03m

    53: Being a Grownup Engineer

    Jack Ganssle, author of 'The Art of Designing Embedded Systems' and long-time embedded industry expert, argues that firmware engineers must adopt disciplined engineering practices rather than relying on 'heroic' hacking. He discusses the necessity of requirements gathering, design reviews, code inspections, and rigorous testing to ensure safety and reliability, citing the Toyota unintended acceleration case as a failure of process. Ganssle advocates for measuring metrics like bug rates and lines of code to benchmark performance, and critiques the misuse of Linux in deeply embedded systems and the confusion between the maker movement and professional engineering.

    Embedded firmwareCareers & education
    10 chapters

  • Global Medical Device Podcast · 36m

    Setting the Record Straight on Usability & Human Factors

    Mike Drues, a regulatory consultant for Vascular Sciences, joins host Jon Speer to clarify the distinction between usability and human factors in medical device development. They discuss how engineers often fail to test devices on actual end-users, leading to design flaws, and argue that FDA regulations are inconsistent, requiring extensive testing for simple devices while ignoring complex ones. The conversation emphasizes that usability testing should be risk-based, distinguishing between formative testing during development and summative testing after design freeze. Drues highlights the importance of realistic testing scenarios and warns against the 'tick-box' mentality that ignores off-label use risks.

    Medical & health devicesValidation & product-market fit
    8 chapters

The summary, chapters and topics are generated from the episode’s audio by this directory, not written by The Pragmatic Embedded Podcast. The episode itself belongs to its publisher.