Home > Articles

Components Everywhere?

Industry is rushing pell-mell to adopt component-based development. But the challenges posed by a large and important class of component-based system, those comprised of commercial software components, have remained unaddressed, or certainly under-addressed.
This chapter is from the book

Water, Water everywhere, But Not a Drop to Drink.
—Samuel Taylor Coleridge
Ryme of the Ancient Mariner

The belief that using commercial components will simplify the design and implementation of systems is widely held, but is, unfortunately, belief in a compelling myth. Imagine you are the architect or chief engineer for a project that is developing a large, mission-critical information system. For whatever reason, it has been decided that the only practical means to this end—although a very promising means—is to build the system from commercially-available components. Before the project makes substantial progress, though, it is confronted by the following obstacles:

  • Many crucial design decisions revolve around component interfaces that are deficient in several respects, but are not subject to negotiation. Yet these same interfaces are often unexpectedly modified by their vendor, simultaneously invalidating previous design workarounds and introducing new integration difficulties.

  • The components have been designed to be easy to integrate with some vendors' components but difficult to integrate with others. Unfortunately, the best components reside in different vendor camps. You discover that the question of which components to use is more complex than anticipated, with each selection decision contingent on some set of other selection decisions.

  • The components that have been selected are sufficiently complex that no one on the project knows exactly how they work. When integrated, the component assembly exhibits baffling and incorrect emergent behavior. The vendors have never seen this behavior before, but they are certain the fault lies with another vendor's component.

Does this sound familiar? How did this state of affairs come about, and what can practicing designers and software engineers do about it? Can predictable and repeatable software engineering methods be established in the face of these challenges? We believe the answer is yes, and this book shows you how to do it.

1.1 The Software Component Revolution

Software components are everywhere—or perhaps we should say this about magazine articles, scholarly papers, market forecasts, and (yes) books about software components. Judging by all that has been written, and continues to be written, the software industry is quickly moving towards component-based development. Add to this the avalanche of commercial software methods and tools that support component-based development and the conclusion seems inevitable.

A closer look at the evidence, however, presents a picture that is far less clear. We do not argue against this trend. Instead, we propose that this trend, far from being unified and coherent, is a splintering of many trends, some competing, some reinforcing, and some wholly independent. Organizations interested in adopting component-based development for competitive or other reasons are immediately confronted by a nearly impenetrable and fast growing thicket of technological, methodological, and organizational options.

To state the conclusion first, software components are real and are already profoundly alterning the practice of software engineering. Despite signs of progress, though, the challenges posed by systems that are constructed predominantly from commercial off-the-shelf components have yet to be adequately addressed. Indeed, the more general challenges posed by large-scale reuse of existing components, regardless of their origin, have yet to be addressed. Further stipulating the commercial origin of components merely adds further complexity to these already unaddressed challenges.

To be sure, there are several accepted and well-defined component-based development methods, notably Cheesman and Daniels' UML Components [17], D'Souza and Wills' Catalysis [26], and Herzum and Sims' Business Component Factory [36], each recently published and each a truly excellent contribution in its own right. However, these methods assume that the design task is, predominantly, one of component specification for later implementation rather than one of component selection for later assembly. Only Herzum and Sims recognize this apparent contradiction between the premise of currently-published component-based development methods and the consequence of adopting a component-based paradigm; namely, that applications would be assembled from existing components rather than from custom-developed components. Herzum and Sims address this by describing a reuse process (the business component factory) which will shift, ever so gradually, the emphasis from custom development to reuse of existing components.

But surely this misses two key points. First, design methods that assume the freedom to define component interfaces are fundamentally different from methods that lack this freedom1. Defining a method for the former condition in the hopes of transitioning this same method to the latter condition is doomed to failure. Second, there are many systems being built today whose fundamental design challenge stems from an aggressive use of commercial software components. By commercial components we mean things such as Web browsers and servers, object request brokers, relational database management systems, message-oriented middleware, public key infrastructure, transaction monitors, geographic information systems, seemingly ad infinitum. Software engineers need design methods to deal with this class of component-based system now, not in some indefinite future.

Our book addresses this gap in software engineering methodology. In particular, we define concepts, techniques and processes to address the design challenges uniquely posed by the use of commercial software components. These challenges include but are not limited to:

  • Critical design decisions must be made in the face of incomplete and often mistaken understanding of the features and behavior of commercial software components. Knowledge gaps are inevitable and are a major source of design risk.

  • Whatever knowledge is obtained about one commercial software component does not to translate easily to components from different vendors, and all component knowledge tends to degrade quickly as components evolve through new releases.

  • Competitive pressures in the software marketplace force vendors to innovate and differentiate component features rather than stabilize and standardize them. This results in mismatches that inhibit component integration and inject significant levels of wholly artificial design complexity.

  • Use of commercial components imposes a predisposition on consumers to accept new releases despite disruptions introduced by changing component features. These disruptions take on a random quality across all phases of development as the number of components used grows.

These challenges all derive from the same root cause: a loss of design control to market forces. Perhaps the reason why no methods have yet been developed to address these challenges is that we have been trained to think of market forces as beyond the scope of software engineering methods. But it is a poor engineering method that fails to accommodate practical reality. These market forces play as much a part in software engineering as friction plays in mechanical engineering.

Before delving into details we must first set some context. We describe the class of design problem addressed by this book, especially with respect to different conceptions of software component and component-based development. Then, we outline our assumptions about the software engineering methods and processes that we expect to already be in place. Last, we deal with terminology.

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