<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Requirements Management</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Requirements Management feed</description>
    <item>
      <title>Producing a Better Software Architecture with Residuality Theory</title>
      <link>https://www.infoq.com/news/2025/10/architectures-residuality-theory/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Requirements+Management</link>
      <description>&lt;img src="https://res.infoq.com/news/2025/10/architectures-residuality-theory/en/headerimage/architecture-residuality-theory-header-1759844199399.jpg"/&gt;&lt;p&gt;Software architecture is tough because it blends coding, math, and business systems. Due to surprises, architectures tend to become irrelevant over time, Barry O'Reilly said. He presented residuality theory, where he suggested stressing naive architectures to reveal hidden “attractors” in complex business systems. This allows designs to better survive change and uncertainty.&lt;/p&gt; &lt;i&gt;By Ben Linders&lt;/i&gt;</description>
      <category>Agile Conferences</category>
      <category>Requirements Management</category>
      <category>Change</category>
      <category>Methodologies</category>
      <category>Complex Systems</category>
      <category>Architecture</category>
      <category>Culture &amp; Methods</category>
      <category>news</category>
      <pubDate>Tue, 07 Oct 2025 14:02:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2025/10/architectures-residuality-theory/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Requirements+Management</guid>
      <dc:creator>Ben Linders</dc:creator>
      <dc:date>2025-10-07T14:02:00Z</dc:date>
      <dc:identifier>/news/2025/10/architectures-residuality-theory/en</dc:identifier>
    </item>
  </channel>
</rss>
