Home > Articles > Software Development & Management > Architecture and Design

Paradoxes of Software Architecture

Many of the ideals we strive for in software architecture ultimately contribute to the system's demise. Kirk Knoernschild, author of Java Application Architecture: Modularity Patterns with Examples Using OSGi, explores the paradoxes of software architecture, examining how "architecture all the way down" and modularity can help.
Like this article? We recommend

Software architecture is fraught with paradox, resulting in opposing forces that are counterintuitive and conflicting. As a result, we often don't realize the architectural goals we seek. Instead, we find ourselves dealing with the very issues we try to avoid.

Other paradoxes in software development clearly exist, though we're beginning to understand new ways to overcome them. Waterfall methodologies encouraged us to capture detailed requirements early in the development lifecycle. The sense of irony is fascinating. Teams who failed to gather accurate requirements on one project would increase the amount of time spent eliciting requirements on the next, only to find that didn't work either. This is foolhardy! We cannot solve a problem using the technique that is the problem's root cause; it's impossible to elicit a stable set of requirements up front. Agile methodologies have since steered us in the right direction.

Unfortunately, we continue to experience three paradoxes of architecture:

Paradox #1: Flexibility breeds complexity. We aim to design flexible software; yet, in doing so, we see an undesirable increase in complexity.

Paradox #2: Reuse complicates use. We strive to develop reusable software, only to impair the software's ease of use.

Paradox #3: Evolution impedes survival. We design a software system that can evolve, but in doing so hasten its death.

To overcome these paradoxes, we draw upon the wisdom of software giants, and we examine how "architecture all the way down" helps.

Paradox #1: Flexibility Breeds Complexity

We aim to design flexible software; yet, in doing so, we see an undesirable increase in complexity.

In fact, this first paradox leads us toward the other two. That is, we try to design flexible software for two reasons:

• So that we can reuse software entities

• So that a system can evolve as necessary

As Ralph Johnson explains, "[M]aking everything easy to change makes the entire system very complex." [1]

In this sense, we might say that the bane of software development is complexity, which certainly comes as no surprise. But perhaps the real bane of software development is that we aim to design software with too much flexibility—that flexibility is what leads us to the complexity we despise. Ironically, it's also flexibility that increases reuse and enables evolution, although the resulting complexity hinders use and decreases survival of these same systems, as shown in Figure 1.

Figure 1 Paradoxes of architecture.

This is not to say that we should avoid designing flexible software systems. But the key is to identify where the flexibility is warranted, in order to avoid unnecessary complexity. To understand how to do this, we turn to Grady Booch: [2]

Architecture is design, but not all design is architecture. Rather, architecture focuses on significant decisions, where significant is measured by the impact of changing that decision. For this reason, architectural decisions tend to concentrate upon identifying and controlling the seams in a system, which are described in terms of interfaces and mechanisms and so typically mark the units of change in the system.

Where are these seams of which Booch speaks? We'll see in a moment, but first let's explore the second paradox.

Paradox #2: Reuse Complicates Use

We strive to develop reusable software, only to impair the software's ease of use.

Reuse is software development's panacea. The ability to compose systems from reusable elements has long been our Achilles' heel. We want reuse badly, yet our failures are spectacular. Almost all major technology trends of the past 20 years (and probably before) tout reuse as the saving grace.

What happened? In the early 1990s, object orientation promised to save software development. It hasn't. In the late 1990s, component-based development promised to save software development. It didn't, and the movement died. In the early 2000s, service-oriented architecture (SOA) promised to save software development. It didn't, although SOA development teams are still trying. Why is reuse so difficult?

First, we turn to the wisdom of Robert Martin and his Reuse-Release Equivalence Principle [3] to understand why objects have failed in delivering on the promise of reuse:

The granule of reuse is the granule of release.

Think about how you release software. What is it that you create? Typically you create some physical entity, such as a JAR file or service that you deploy. These are your granules of release; subsequently, they're also your granules of reuse. Objects are too fine-grained to serve as a granule of release and make poor candidates for a granule of reuse.

Of course, objects do play a role in reuse. Through abstraction, objects allow us to design flexible software that's open for extension and can be tailored based on need. In other words, we reuse a piece of software by designing extension points that allow other developers to configure that piece of software to a new context. However, as we've noted previously, this flexibility breeds complexity. Clemens Szyperski gives us the use/reuse paradox: [4]

Maximizing reuse complicates use.

To discover how this complication occurs, we simply need to examine two attributes of a software entity that affect its reusability: granularity and weight.

Granularity

Granularity is the extent to which a system is broken down into parts. Coarse-grained entities offer richer behavior than fine-grained entities do. Because they do more, they also tend to be larger than fine-grained entities. To maximize reuse, we try to compose coarse-grained entities from fine-grained entities. Of course, this approach results in a lot of dependencies between the fine-grained entities, making those entities more difficult to use. In general, we can say the following:

Coarse-grained entities are easier to use, but fine-grained entities are more reusable.

Weight

Weight is the extent to which a software entity depends on its environment. A heavyweight entity depends on its operating environment; a lightweight entity avoids such dependencies. When creating an entity that runs in multiple environments, we're forced to move the environment-specific dependencies (that is, the context dependencies) from code to configuration. This change makes the entity more reusable, but it's also more difficult to use because the entity must be configured for each environment.

Designing and configuring a lightweight entity is more difficult than simply dropping in an entity that's programmed to operate in that specific environment. In general, we can say the following:

Lightweight modules are more reusable, but heavyweight modules are easier to use.

It's clear that the conflict between reuse and use, as explored through granularity and weight, will challenge even the most experienced developers.

Paradox #3: Evolution Impedes Survival

We desire a software system that can evolve, but in doing so hasten its death.

Software tends to rot over time. When you establish your initial vision for the software's design and architecture, you imagine a system that's easy to modify, extend, and maintain—that is, a software system that can evolve as change occurs.

Unfortunately, as time passes, changes trickle in that exercise your architecture in unexpected ways. The flexibility we seek contributes to hindering our ability to understand the impact of change. Each change begins to resemble nothing more than another hack, until finally the system becomes a tangled web of code through which few developers care to venture. Most of us have experienced this phenomenon. Ultimately, we violate our original architectural goals, and the interdependencies between different areas of the system increase. Sadly, design rot is self-inflicted, and technical debt describes the effect of rotting design.

Technical debt is a metaphor developed by Ward Cunningham, who uses the term to describe the design tradeoffs we make in order to meet schedules and customer expectations. [5] Martin Fowler helps us to understand technical debt by comparing it to financial debt: [6]

Like a financial debt, the technical debt incurs interest payments, which come in the form of the extra effort that we have to do in future development because of the quick and dirty design choice. We can choose to continue paying the interest, or we can pay down the principal by refactoring the quick and dirty design into the better design. Although it costs to pay down the principal, we gain by reduced interest payments in the future.

In some situations, leveraging suboptimal designs, and thereby incurring technical debt, is warranted to meet short-term demands. For instance, your schedule may not allow longer-term designs to be used. However, if we ignore technical debt, it continues to build over time, and incurring too much debt leads to significant inefficiencies surrounding our ability to change the software system effectively. Meir M. Lehman's Law of Increasing Complexity summarizes this phenomenon well: [7]

As [a] system evolves its complexity increases unless work is done to maintain or reduce it.

In Search of the Vaunted Silver Bullet

The paradoxes paint a gloomy picture. Is there any hope of designing software that's flexible enough to endure the test of time, while simultaneously offering us the opportunity of reuse? As an optimist, I'd like to believe so, and "architecture all the way down" is part of the solution.

The issue is not that the object-oriented paradigm has failed us, or that SOA has failed us. The issue is that neither of these two paradigms is enough on its own, and even together they're not enough. Objects are too fine-grained to solve many of the challenges, and services are too coarse. As Booch suggests, we need to emphasize the seams of the system. But where are the seams in a system of objects? There are far too many object interactions to fully understand, even in a moderately sized system. Though services expose an interface that represents these seams, they're too coarse-grained, leaving the underlying implementation of an individual service to suffer a paradoxical fate.

Something is missing.

The answer lies, at least partially, in the native deployment constructs of various platforms. On the Java platform, this is the JAR file. On .NET, it's the assembly. These deployment constructs offer the opportunity to modularize our software systems, as shown in Figure 2:

• Modularization gives us an alternative unit of granularity whereby focusing on the seams between modules informs us of the areas that need the greatest flexibility.

• Modularity gives us an alternative granule of reuse.

• Modularity allows us to encapsulate implementation details at a finer-grained level that increase the adaptability of the system by isolating change.

Wrapping Up

Software complexity is a terrible enemy that inhibits our ability to develop adaptable software that's easy to understand. To deal with complexity, we try designing flexible software. Sadly, too often the flexibility we hope will tame complexity and yield higher degrees of reuse and maintainability has a paradoxical effect. The complexity hinders use and decreases the ability of our software to survive long-term.

Overcoming these paradoxes isn't easy, but "architecture all the way down" can help. By focusing on different units of granularity, including objects, models, and services, we gain important information on areas of the system that require greater flexibility than others, while encapsulating other design details.

Did this article whet your appetite? Java Application Architecture: Modularity Patterns with Examples Using OSGi explores these ideas in greater detail and introduces 18 patterns to help you build better software.

(c)References

[1] Ralph Johnson, in an email message to Martin Fowler quoted in Fowler's article "Who Needs an Architect?" IEEE Software, 2003.

[2] Grady Booch. "The Handbook of Software Architecture."

[3] Robert C. Martin, "Design Principles and Design Patterns." January 2000.

[4] Clemens Szyperski, Component Software: Beyond Object-Oriented Programming, Second Edition. Addison-Wesley, 2002.

[5] Ward Cunningham, "Ward Explains Debt Metaphor" (video), Jan. 22, 2011.

[6] Martin Fowler, "Technical Debt." Feb. 26, 2009.

[7] Meir M. Lehman, "On Understanding Laws, Evolution, and Conservation in the Large-Program Life Cycle." Journal of Systems and Software Vol. 1, 1980, pp. 213

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020