Dr. Dobb's is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Channels ▼

Andrew Koenig

Dr. Dobb's Bloggers

Recovering the architecture

October 25, 2009

Here's a situation that I've seen so many times that I've lost count. Someone builds a system with a clean architecture. After a while, users realize that there are important things that the system cannot do.  They ask for new features.  Those features do not fit well in the architecture, but they get shoehorned in anyway as a patch--because they're important.

Lather, rinse, repeat.  After a while, the system has so many patches on top of patches on top of patches that no one understands it any more.  By then, no one is left who understands the original architecture, so someone gets the unenviable task of "recovering the architecture" -- i.e. figuring out by inference how the original system must have been designed.

Of course, the next task, once the architecture has been recovered, is to come up with a new architecture that supports no only everything the original architecture did but also all the features that have been patched into the system in the meantime.  Sometimes that effort fails because it is so complicated that no one understands it.  However, the more usual outcome is a system that mostly works, but doesn't quite.

Such systems tend to fail in two ways.  First, every large system has bugs, which means that some users of the new system will find that things they were doing with it, which used to work, no longer do so.  Second, and perhaps more important, is that there are probably bugs in the architecture recovery itself: The new architecture is fundamentally incapable of doing something that the old architecture could do, and some users consider that capability to be important.  So the old capability is patched into the new system in the name of backward compatibility, and the cycle begins again.

This architectural process seems always to result in systems of ever-increasing complexity.  Not only do such systems require ever-increasing effort to keep working, but the chance of serious security problems keeps going up as well.  Food for thought:  Is there any way of avoiding this complexity creep in practice?  Some people will surely say "Don't worry about architecture!  Do the simplest thing that works and keep refactoring as you go!  Just be sure your tests cover all the bases."  But how can even the most systematic testing prove the absence of security problems?

Can anyone convince me that we have made any real progress toward solving this problem in the past few decades?

Related Reading

More Insights

Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.