<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>TraceUnified Guides</title>
    <link>https://traceunified.com/guides/</link>
    <description>Guides on requirements traceability, compliance, and lifecycle engineering for regulated, safety-critical teams.</description>
    <language>en-us</language>
    <item>
      <title>The Design History File (DHF) in 2026: what QMSR changed</title>
      <link>https://traceunified.com/guides/design-history-file-qmsr/</link>
      <guid>https://traceunified.com/guides/design-history-file-qmsr/</guid>
      <pubDate>Fri, 26 Jun 2026 00:00:00 GMT</pubDate>
      <description>What a Design History File is, what belongs in it, and how the FDA's QMSR transition (effective February 2026) renames it to the Design and Development File under ISO 13485 — with the underlying design-control requirement unchanged.</description>
    </item>
    <item>
      <title>What is Application Lifecycle Management (ALM)?</title>
      <link>https://traceunified.com/guides/what-is-application-lifecycle-management/</link>
      <guid>https://traceunified.com/guides/what-is-application-lifecycle-management/</guid>
      <pubDate>Fri, 26 Jun 2026 00:00:00 GMT</pubDate>
      <description>A clear introduction to Application Lifecycle Management — what ALM covers, how it differs from project or just requirements management, why traceability is its backbone, and what ALM means for regulated, safety-critical development.</description>
    </item>
    <item>
      <title>ISO 26262 traceability: from safety goals to verification</title>
      <link>https://traceunified.com/guides/iso-26262-traceability/</link>
      <guid>https://traceunified.com/guides/iso-26262-traceability/</guid>
      <pubDate>Thu, 25 Jun 2026 00:00:00 GMT</pubDate>
      <description>How ISO 26262 builds functional safety into automotive development — ASILs, the safety lifecycle and V-model, and the traceability that links safety goals through requirements to verification evidence.</description>
    </item>
    <item>
      <title>DO-178C requirements management and traceability, explained</title>
      <link>https://traceunified.com/guides/do-178c-requirements-traceability/</link>
      <guid>https://traceunified.com/guides/do-178c-requirements-traceability/</guid>
      <pubDate>Wed, 24 Jun 2026 00:00:00 GMT</pubDate>
      <description>How DO-178C structures airborne software assurance — design assurance levels, the requirements hierarchy, bidirectional traceability, and requirements-based testing — and why trace data is the backbone of certification.</description>
    </item>
    <item>
      <title>How to write clear requirements with the EARS notation</title>
      <link>https://traceunified.com/guides/writing-clear-requirements-ears/</link>
      <guid>https://traceunified.com/guides/writing-clear-requirements-ears/</guid>
      <pubDate>Wed, 24 Jun 2026 00:00:00 GMT</pubDate>
      <description>A practical guide to writing clear, testable requirements using EARS (Easy Approach to Requirements Syntax) — the five patterns, examples of each, and how structured requirements make verification and traceability far easier.</description>
    </item>
    <item>
      <title>IEC 62304: the medical device software lifecycle, explained</title>
      <link>https://traceunified.com/guides/iec-62304-software-lifecycle/</link>
      <guid>https://traceunified.com/guides/iec-62304-software-lifecycle/</guid>
      <pubDate>Tue, 23 Jun 2026 00:00:00 GMT</pubDate>
      <description>How IEC 62304 structures medical device software development — software safety classes A, B, and C, the lifecycle processes it requires, its link to ISO 14971 risk, and why traceability ties the whole thing together.</description>
    </item>
    <item>
      <title>Choosing requirements and traceability software: an evaluation guide</title>
      <link>https://traceunified.com/guides/choosing-requirements-traceability-software/</link>
      <guid>https://traceunified.com/guides/choosing-requirements-traceability-software/</guid>
      <pubDate>Mon, 22 Jun 2026 00:00:00 GMT</pubDate>
      <description>A vendor-neutral framework for evaluating requirements and traceability tools for regulated, safety-critical work — the criteria that matter, the architectural question behind them, and the questions to ask every vendor.</description>
    </item>
    <item>
      <title>FDA 21 CFR Part 11: a practical guide to electronic records and signatures</title>
      <link>https://traceunified.com/guides/fda-21-cfr-part-11-guide/</link>
      <guid>https://traceunified.com/guides/fda-21-cfr-part-11-guide/</guid>
      <pubDate>Mon, 22 Jun 2026 00:00:00 GMT</pubDate>
      <description>What 21 CFR Part 11 requires — electronic records, electronic signatures, audit trails, validation, and access controls — how the QMSR transition affects it, and what &quot;Part 11 compliant&quot; software really means.</description>
    </item>
    <item>
      <title>SBOM and FDA cybersecurity: what Section 524B requires</title>
      <link>https://traceunified.com/guides/sbom-fda-cybersecurity-524b/</link>
      <guid>https://traceunified.com/guides/sbom-fda-cybersecurity-524b/</guid>
      <pubDate>Sun, 21 Jun 2026 00:00:00 GMT</pubDate>
      <description>What a software bill of materials is, why FDA Section 524B now requires one for cyber devices, what a compliant SBOM contains, and how connecting it to your requirements and risk turns it from a list into a vulnerability-impact tool.</description>
    </item>
    <item>
      <title>What is a requirements traceability matrix (RTM)?</title>
      <link>https://traceunified.com/guides/what-is-a-requirements-traceability-matrix/</link>
      <guid>https://traceunified.com/guides/what-is-a-requirements-traceability-matrix/</guid>
      <pubDate>Sat, 20 Jun 2026 00:00:00 GMT</pubDate>
      <description>A plain-English guide to the requirements traceability matrix — what it is, what belongs in it, the forward and backward links that make it work, and why it matters for regulated, safety-critical development.</description>
    </item>
  </channel>
</rss>
