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

On Architecture: From Small to Gargantuan

In their innovative book A Pattern Language, Christopher Alexander and his colleagues describe the patterns that breathe life into civil architectures, from intimate spaces to buildings to entire towns. No matter where you look along this spectrum of size, you’ll find common structures and common behaviors. At each point in the spectrum, the patterns therein form the architecture of each instance. Across the software landscape, you’ll find a similar spread, from small programs to systems to systems of systems. Each instance has an architecture, be it intentional or accidental, and the forces that work upon each system—from small to gargantuan—vary accordingly.

This article is provided courtesy of" IEEE Software Magazine.

In their innovative book A Pattern Language, Christopher Alexander and his colleagues describe the patterns that breathe life into civil architectures, from intimate spaces to buildings to entire towns. No matter where you look along this spectrum of size, you'll find common structures and common behaviors. At each point in the spectrum, the patterns therein form the architecture of each instance.

Across the software landscape, you'll find a similar spread, from small programs to systems to systems of systems. Each instance has an architecture, be it intentional or accidental, and the forces that work upon each system—from small to gargantuan—vary accordingly.

Software development is ultimately an engineering activity, whose primary activity is to deliver executable artifacts in a manner that balances the forces on that system. The forces that swirl around a software-intensive system include not only its purely functional requirements but also a multitude of nonfunctional ones, such as reliability, portability, and scalability (often called a system's -ilities). Each of these forces is resolved systemically, meaning that no single part of a system can be responsible for responding to a force. Rather, the system as a whole, with its parts working in an architected union, must confront these forces. Indeed, the fact that these forces are dynamic and might change radically over a system's lifetime contributes to making software-intensive systems so complex.

Five forces at work

For these kinds of systems, we can group relevant forces into five basic categories: business, environment, development, operations, and values.

Business forces include cost and schedule. Obviously, it takes time, materials, and people to build and run a system, and the availability of each dictates what can and cannot be built. Ideally, these forces should press in just enough to motivate a maniacal focus on what's really important but not so much that the organization is always starving for resources (and not so little that the organization is sloppy and inefficient).

No interesting software-intensive system lives in isolation; it's shaped by the various forces in its environment. Resources such as computational power, electrical power, physical space, and personnel are limiting factors for some. For most embedded systems, these are unyielding constraints; in contrast, many enterprise systems thirst for more of every such resource. Compatibility with external elements might also warp a system: process and technical standards; demands for system interoperability; economic, historical, and political factors that stipulate using legacy parts; and the necessity for internationalization each represent some dimension of compatibility. A system's complexity also plays a critical role, perhaps the most important one. All interesting software-intensive systems are intrinsically complex, some more so than others. Sometimes, a system will push various software limits, rendering it far more difficult to build, run, and grow.

A system's development encompasses the forces that act during its creation, deployment, and evolution, including

  • Feasibility. Is the system novel and does it require technical breakthroughs to build it?
  • Manageability. A system whose sole user is also the sole developer is a wee bit easier to manage than one that spans countries, languages, and political systems.
  • Accountability (also known as traceability). If you jiggle one branch of a system, can you predict what distant leaves will shake?

Demands for secrecy can also impact development: a system classified for national-security reasons creates physical and social barriers that don't exist in open systems.

The need for resilience is also a critical development force. Resilience encompasses

  • Supportability. Is it an open source system or closed and tightly controlled (such as a system in deep space)?
  • Maintainability. Can we repair the system easily?
  • Adaptability. Can we reconfigure the system to accommodate an unanticipated use?
  • Scalability. Can we grow the system to accommodate greater capacity or throughput?
  • Portability. Can we move the system from one physical platform to another?
  • Extensibility. Can we add a new behavior to the system?
  • Churn. Can we modify the system to accommodate new technology?

Whereas developmental forces act during a system's development and growth, operational forces derive from the stakeholders who use the system. Functionality is the most important operational force: a system with hundreds of use cases from many different stakeholders' perspectives is far more complex than a system with only a few use cases and one class of users. As such, functionality involves a system's behavior and usability as seen through the eyes of each set of stakeholders. Performance and quality represent nonfunctional demands on a system. We can measure performance in terms of a system's required typical as well as peak throughput, capacity, and responsiveness. Quality demands such as precision and accuracy will also vary from system to system and in turn shape each system uniquely. A system's dependability reflects the degree to which its stakeholders have confidence in its operation. Each system will have different requirements for safety, reliability, availability, security, survivability, and degradability.

Software-intensive systems that directly or indirectly impinge on environmental, geopolitical, and human values will naturally be subject to more controls and scrutiny. Sometimes, legal issues dictate what we can and can't build: privacy laws; laws for medicine, commerce, and transportation; and intellectual property rights including patents and copyright laws can shape a system. Additionally, ethical and moral factors may weigh in. Building a given system might be technically possible, but a community's values can keep it from happening.

Three example systems

Let's consider some of the forces that weigh on three different software-intensive systems of varying size.

In my first column, I mentioned the Computer History Museum's efforts to preserve the source code and surrounding artifacts of classic, seminal pieces of software. The Museum has a software curator—the only such position I've ever seen in a museum—as well as a vibrant software collections committee. Through a connection with Tim O'Reilly and then with Bill Adkinson and Andy Herzfeld, the committee secured the original source code for Apple's MacPaint. MacPaint wasn't the first graphical image program, but it was the first widely available one, and its presence was important in the personal computer's launch and in the start of digital graphics. MacPaint was written in Object Pascal and consists of only a few thousand lines of code. Architecturally, it's a beautifully simple and elegant object-oriented program. The forces of size and speed (given that the original Mac and all PCs at the time were computationally constrained) and usability (given the general audience) governed the shape of this application.

Jump ahead a few years to the present, and you have Adobe Photoshop, the dominant 2D digital graphics program. (Maya holds the dominant position in 3D digital graphics.) Photoshop is a much larger program, consisting of several million lines of C and C++; it's also a far more capable program, able to conduct complex manipulations on very large images. Usability (for a range of artist skills), speed and capacity (it must be able to handle large images with rich properties and multiple layers of various types), compatibility (with several image format standards), and extensibility (via its plug-in mechanism) shape Photoshop's architecture.

Consider next the system of systems used in producing a contemporary animated motion picture. Artists commonly produce images with Photoshop and Maya and then apply various special effects tools (such as motion capture and lip synchronization programs, mob agents, and plug-ins for hair, clothing, water, fire, air, and particle simulations). Add to that a complex rendering pipeline, and you've got a complex system involving perhaps thousands of machines and hundreds of users. Capacity, speed, reliability, repeatability, and adaptability dominate these architectures.

One person's system is another person's subsystem. Each system has an architecture that serves to hold back the forces weighing in on that system. At each level of system, different kinds of forces dominate, thus lending themselves to different architectural styles.

Grady Booch is an IBM Fellow. He's one of the Unified Modeling Language's original authors. He also developed the Booch method of software development, which he presents in Object Oriented Analysis and Design. Contact him at architecture@booch.com.

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.


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.


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.


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.


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


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


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.


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.


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