<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Boris Holzer on Medium]]></title>
        <description><![CDATA[Stories by Boris Holzer on Medium]]></description>
        <link>https://medium.com/@holzer?source=rss-ebc41f252c5a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*7fMfjnHeLRVAuFHF.jpg</url>
            <title>Stories by Boris Holzer on Medium</title>
            <link>https://medium.com/@holzer?source=rss-ebc41f252c5a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 16:56:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@holzer/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How two match XML nodes having similar attributes]]></title>
            <link>https://medium.com/@holzer/how-two-match-xml-nodes-having-similar-attributes-59c25b2b94b3?source=rss-ebc41f252c5a------2</link>
            <guid isPermaLink="false">https://medium.com/p/59c25b2b94b3</guid>
            <category><![CDATA[xml]]></category>
            <category><![CDATA[xpath]]></category>
            <dc:creator><![CDATA[Boris Holzer]]></dc:creator>
            <pubDate>Tue, 25 Aug 2020 09:15:58 GMT</pubDate>
            <atom:updated>2020-08-27T11:34:23.954Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to match XML nodes having similar attributes</h3><p>This is about how to utilize XPath to match XML nodes having similar attributes. You may want to consider a database foreign key as metaphor.</p><p>Here’s an example:<br>Given the following XML</p><pre><em>&lt;team&gt;<br>  &lt;positions&gt;<br>   &lt;position id=”1&quot; name=”</em>offense<em>”/&gt;<br>   &lt;position id=”2&quot; name=”defense”/&gt;<br>  &lt;/positions&gt;<br> &lt;players&gt;<br>   &lt;player name=”Jim” position=”1&quot;/&gt; <br>   &lt;player name=”John” position=”1&quot;/&gt;<br>   &lt;player name=”Joe” position=”2&quot;/&gt;<br>   &lt;player name=”Josef” position=”2&quot;/&gt;<br> &lt;/players&gt; <br>&lt;/team&gt;</em></pre><p>I want one single XPath-Expression which gives me both the defense and the offense row. Here it is:</p><pre>/team/positions/position/concat(<a href="http://twitter.com/name">@name</a>,’: ‘, string-join(for $ID in ./@id return /team/players/player[<a href="http://twitter.com/position">@position</a>=$ID]/@name,’,’))</pre><p>The result of this XPath expression is:</p><pre>String=’offense: Jim,John’<br>String=’<em>defense</em>: Joe,Josef’</pre><p>Explanation:</p><ul><li>find all positions: /team/positions/position/@name</li><li>prepare to concat: <br>/team/positions/position/concat(@name,&#39;: &#39;,&#39;list of players&#39;)</li><li>find all matching players. Base idea is to iterate over all players and filter them based on ther position. We use a variable $ID and a loop for...return for this.<br>for $ID in ./@id return /team/players/player[@position=$ID]/@name</li><li>We now add the loop to the concat:¹<br>/team/positions/position/concat(@name,&#39;: &#39;,for $ID in ./@id return /team/players/player[@position=$ID]/@name)<br><strong>Oops</strong>: This results in an error!<br><em>A sequence of more than one item is not allowed as the third argument of concat()</em></li><li>Overcome the error: Use string-join(&lt;list&gt;,separator)to join the sequence to a string before adding it to the concat:¹<br>/team/positions/position/concat(@name,&#39;: &#39;,string-join(for $ID in ./@id return /team/players/player[@position=$ID]/@name,&#39;,&#39;))</li></ul><p>TADA — There we are!<br>Please: If you have an easier solution or a solution that guarantees good performance on large XML files: Add a comment.</p><p>¹Footnote: For some reason, it is not possible to copy the code from Medium to an external editor. This affects the explanation section only: If I copy from there to … let’s say local notepad++, the space character directly behind $ID is not a space character. Reason seems to be that inline code format. Anyhow, Medium’s the block code format (section before the explanations) seems to be fine.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=59c25b2b94b3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Requirements Traceability — what is it (good for)?]]></title>
            <link>https://medium.com/@holzer/requirements-traceability-what-is-it-good-for-e8b187fbc13?source=rss-ebc41f252c5a------2</link>
            <guid isPermaLink="false">https://medium.com/p/e8b187fbc13</guid>
            <category><![CDATA[traceability-matrix]]></category>
            <category><![CDATA[requirements-traceability]]></category>
            <category><![CDATA[impact-analyses]]></category>
            <category><![CDATA[traceability-tool]]></category>
            <category><![CDATA[project-progress]]></category>
            <dc:creator><![CDATA[Boris Holzer]]></dc:creator>
            <pubDate>Fri, 06 Dec 2019 11:38:35 GMT</pubDate>
            <atom:updated>2019-12-06T15:11:03.643Z</atom:updated>
            <content:encoded><![CDATA[<h3>Requirements Traceability — what is it (good for)?</h3><p>I want to explain requirements traceability: What is it? What are today’s challenges? What are the potential benefits?<br>The management summary is: It is so much more than a matrix which relates requirements and test cases.</p><p>According to Wikipedia, traceability is the capability to trace something. According to uncounted publications, requirements traceability is about links between requirements and test cases. The common suggestion is to create a matrix consisting of e.g. one row per requirement, one column per test case (or the other way around). In this matrix, you can tick those cells representing a requirement which is verified by a test case. Wonderful Terry Pratchett would have called this explanation “a lie for children”, i.e. it gives a simple explanation which may be wrong, but is understood and accepted even by complete laymans.</p><h3>Today’s challenges</h3><p>There are two drivers in modern software or systems development which make things a little more complicated. To stay in Pratchett’s picture, I will now tell a “lie for students”.</p><p><strong>One driver is the complexity</strong> of modern systems. To master this complexity, we use derivations and refinements. A software test may e.g. verify a software requirement which is implied by a software architecture decision which is based on the system design which has been decided to meet a given customer requirement. To which requirement should the software test now be traced? The answer is simple: It should be traceable to each requirement, design element, etc. which has an impact on it. The solution is to create traceability links between pairs of artifacts. By doing so, a trace can be regarded as a chain of traceability links. This idea of consistent traceability is so powerful.</p><p>That is why several standards declare it as mandatory for the development of safety-critical systems.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XytJHdIBZr2nd9Dg" /><figcaption><strong>An example for the specification of traceability — in this case as part of theAutomotive SPICE Process Assessment / Reference Mode</strong></figcaption></figure><p>By the way, in <a href="https://blogs.itemis.com/en/5-reasons-why-a-requirements-traceability-matrix-is-not-enough">this post</a> Florian explains, why a multi-dimensional trace matrix will hardly solve the problem.</p><p><strong>The other driver is the amount of data. </strong>In the field of safety-critical systems, projects comprise hundreds of thousands of artifacts. Current projects in the area of autonomous driving expect millions of artifacts. The resulting matrix won’t probably fit into an Excel file.</p><h3>Potential benefits</h3><p>Imagine the benefits you can get from a good traceability tool. It should not only be able to recognize all relevant artifacts but also to maintain the trace links between them. The tool should also be able to analyze the resulting graph of development artifacts. They are your project.</p><p>The low hanging fruits provided by such tools are answers to the questions “What is linked?” and “What is not linked?”. These so-called <strong>impact- and coverage-analyses </strong>are state-of-art in the field of requirements traceability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qIX0TYMl2GNXDX8Y" /><figcaption><strong>Impact analysis: What is linked to Stakeholder Requirement 2.1.5</strong></figcaption></figure><p>The <strong>change analysis </strong>is a little bit more challenging. Imagine you want to compare different versions of requirements or complete specification documents. You may even want to compare the entirety of artifacts in your project. Given that your traceability tool provides historization of data, such a comparison should be possible, too.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KuuJxQxNijcG43dU" /><figcaption><strong>Delta Report: A requirement changed and there are some new integration tests</strong></figcaption></figure><p>Now let’s go one step further. You don’t want to get only the low-hanging fruits. You want the whole cake. The data provided by a traceability tool can contain so much more information than “pure” traceability.</p><p>You could, for instance, check your project’s <strong>KPIs </strong>based on these data. As an example, we define the <em>implementation status for customer requirements </em>as follows:</p><p>A requirement is considered to be…<br>… New - if is not linked at all<br>… Analyzed - if it has at least one link to an internal requirement<br>… Implemented - If all traces (i.e. link chains) are complete<br>… Work in Progress - if none of the above cases matches</p><p>You can then run your analysis regularly and get a project progress monitor.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PEylTjbu9i7pYSwe" /><figcaption><strong>Requirement Implementation Status in Traceability Dashboard</strong></figcaption></figure><p>You also could create <strong>smooth tool integrations</strong> which e.g. provide navigation support for your engineers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SDVaUb_bNQVKDFa9" /><figcaption><strong>Navigation from code to software design model to test case</strong></figcaption></figure><p>Finally, I want to draw your attention to an <a href="https://blogs.itemis.com/en/benefits-from-requirements-traceability-when-maintaining-software-systems">empirical evaluation</a> done by Prof. Dr. Patrick Mäder et.al. The findings show that subjects utilizing traceability performed on average 24% faster on a given task and created on average 50% more correct solutions. That means that traceability does not only save effort but can profoundly improve the quality of software maintenance.</p><p>Do you have comments or ideas? Please let me know.</p><p>The screenshots in this post show the tool <a href="https://www.itemis.com/en/yakindu/traceability/">YAKINDU Traceability.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e8b187fbc13" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>