<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Traceability on Embedded Leadership</title><link>https://embedded-leadership.com/tags/traceability/</link><description>Recent content in Traceability on Embedded Leadership</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Christophe Le Douarec</copyright><lastBuildDate>Sat, 11 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://embedded-leadership.com/tags/traceability/index.xml" rel="self" type="application/rss+xml"/><item><title>Getting Started with SARA: Requirements as Code</title><link>https://embedded-leadership.com/posts/sara-getting-started/</link><pubDate>Sat, 11 Apr 2026 00:00:00 +0000</pubDate><guid>https://embedded-leadership.com/posts/sara-getting-started/</guid><description>&lt;p&gt;In complex organizations, requirements and architecture documents are often
scattered across teams, tools, and repositories. Keeping everything aligned is a
constant struggle. What if your requirements could live as plain Markdown files
in Git, versioned, reviewed, and interconnected like code?&lt;/p&gt;
&lt;p&gt;That&amp;rsquo;s exactly what &lt;strong&gt;SARA&lt;/strong&gt; does.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;SARA&lt;/strong&gt; (&lt;strong&gt;S&lt;/strong&gt;olution &lt;strong&gt;A&lt;/strong&gt;rchitecture &lt;strong&gt;R&lt;/strong&gt;equirement for &lt;strong&gt;A&lt;/strong&gt;lignment) is a
command-line tool that manages architecture documents and requirements as an
interconnected knowledge graph. No databases, no servers, no subscriptions. Just
Markdown files with YAML frontmatter and a powerful CLI to validate, query, and
report on them.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://embedded-leadership.com/posts/sara-getting-started/featured.webp"/></item><item><title>Introducing SARA: Requirements traceability for the modern age</title><link>https://embedded-leadership.com/posts/sara-launch/</link><pubDate>Fri, 10 Apr 2026 00:00:00 +0000</pubDate><guid>https://embedded-leadership.com/posts/sara-launch/</guid><description>&lt;div class="lead text-neutral-500 dark:text-neutral-400 !mb-9 text-xl"&gt;
 Throughout my career in embedded systems, I&amp;rsquo;ve watched teams struggle with the
same problem over and over: requirements traceability.
&lt;/div&gt;

&lt;p&gt;You know the drill: ASPICE audits, CMMI assessments, ISO 26262 compliance, etc.
Everyone needs traceability, and the options are always the same: expensive
enterprise tools like DOORS that feel like they were designed in another era,
or JIRA-based workarounds that integrate poorly with actual code and slow
everything down.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://embedded-leadership.com/posts/sara-launch/featured.webp"/></item></channel></rss>