Home > Articles

Components Everywhere?

  • Print
  • + Share This
This chapter is from the book

1.2 Component Space

The term "component-based development" does not refer to the development of just one type of system, or to the use of just one type of component. Most conceptions of component-based development share a few fundamental concepts. Foremost of these is that components are software implementations that have interfaces and that are units of independent substitution. But beyond this, there are numerous variations, both large and small. We have found three dimensions of variation to be particularly apt for describing the big picture.

The first dimension concerns the source of software components. As we earlier noted, published component-based software methods share a premise: that the principle task of the design effort is to produce component specifications. This premise is clearly invalid in situations where most or all of the components already exist. The distinction we make, then, is between development efforts that specify their own custom components and efforts that are constrained to use only preexisting components. Today, the most important source of preexisting components is the software component marketplace. It is the marketplace that will lead to economies of scale and that will truly differentiate component-based development from other software engineering paradigms.

The second dimension concerns the environments into which components are deployed and in which they execute. Again, there are two major distinctions. Some components are deployed directly onto a native operating system. This class of component need only comply with the interfaces and conventions imposed by that operating system. Other components are deployed into a higher-level environment that is variably referred to as a component framework [3][85], business component virtual machine[36], or component standard[17]. Whatever it is called, the distinction between framework-based and operating system-based components is an important one, since a component framework constrains component developers and simplifies component integration.

The third dimension concerns the use of components to implement application versus infrastructure. Obviously this distinction is subjective: the best definition of infrastructure that we know of is "whatever it is that I need to do my job."2 Consequently, one engineer's infrastructure may well be another engineer's application. Nevertheless, the idea of infrastructure does have substantive meaning for one very large class of system—the enterprise information system. Enterprise systems tend to be, among other things, large, heterogeneous, distributed, multi-user, persistent, transactional, and secure. By infrastructure we mean the software that implements this functionality. In contrast, enterprise applications use the infrastructure to implement and deliver business services to users.

Some people refer to infrastructure dismissively as "plumbing" as a way of suggesting that this functionality should be assumed to exist within a component framework, that the problems of infrastructure are by and large solved, and that the real software engineering problems reside elsewhere. We agree that one of the benefits of component frameworks is that they bundle infrastructure services [80]. In principle, we agree with Herzum and Sims (and many others) that component technology will evolve in the direction of more complete and robust frameworks. However, we do not expect one standard framework to emerge, but rather a variety of component frameworks, each tailored to its own requirements. Such frameworks will themselves need to be integrated, and new releases of frameworks must be installed and integrated. There is no escaping infrastructure, and building and sustaining an enterprise infrastructure is an excruciatingly complex undertaking. Software engineering methods are needed here, too.

Figure 1-1 depicts these as three orthogonal dimensions in a Cartesian coordinate system. We of course understand that the world of components is far more complex than can be accommodated by these three dimensions. But the resulting picture of "component method space" adequately situates the subject matter of this book with respect to different classes of component-based system and their related development methods.

As mentioned earlier, Cheesman and Daniels' UML Components targets the design of applications built using frameworks (upper right rear). Although their method includes a step to search for existing components, doing so after defining component interfaces practically guarantees that no components will be found. Herzum and Sims' are even more aggressive in postulating component frameworks than Cheesman and Daniels. They assume frameworks exist at each conceptual layer (user, workstation, enterprise, and resource) in their canonical system design. Both of these methods focus on application rather than infrastruc

Figure 1-1 The Structure of Component Method Space

The region of framework-based commercial components used for applications (upper left rear) represents an important emerging market. It includes, for example, markets in commercial off-the-shelf Enterprise JavaBeans™. Such components are already available in the commercial marketplace as stand-alone components, and as product-lines of components. While the component framework used in such applications will distill away much of the integration complexity that is tackled by this book, the market forces that drive the component market will ensure that a considerable residue of mismatch among components will remain. As a result, we expect that engineering methods that address this class of application will need to combine elements described in this book and what is described by Cheesman and Daniels. In any event, work is needed in this area, and soon.

We have dash-outlined the two uncharted regions of space corresponding to framework-based components for infrastructure. There are research projects (sometimes referred to as "programmable middleware") that are underway in this area of space. While these efforts might produce industrial-grade results, currently these regions are essentially unexplored. Note one area of space that should be avoided at all hazards: enterprise infrastructures built from custom software. There may be some justification for this for military applications or other highly specialized domains, but otherwise there is little justification for avoiding commercial technologies.

The remaining regions of component-method space—applications and infrastructure constructed predominantly from commercial-of-the-shelf (COTS) components—are the subject of this book.

  • + Share This
  • 🔖 Save To Your Account

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