Home > Store

Component Software: Beyond Object-Oriented Programming (paperback), 2nd Edition

Register your product to gain access to bonus material or receive a coupon.

Component Software: Beyond Object-Oriented Programming (paperback), 2nd Edition


  • Your Price: $59.99
  • List Price: $74.99
  • We're temporarily out of stock, but order now and we'll send it to you later.


  • Copyright 2003
  • Dimensions: 6-1/4" x 9-1/4"
  • Pages: 624
  • Edition: 2nd
  • Book
  • ISBN-10: 0-321-75302-X
  • ISBN-13: 978-0-321-75302-1

In Component Software, Second Edition, Clemens Szyperski has updated his definitive guide to software component technologies, their technical and business value, and their most effective use. Building on the book that earned the prestigious Software Development Magazine 1999 Jolt Award for Product Excellence, Szyperski has added thorough coverage of today's most compelling component-related technologies, including Enterprise JavaBeans, .NET, XML, and SOAP. He presents a unique blend of market and technology coverage, broad and fair coverage of all current component technologies, as well as a deep discussion of the key challenges faced by component developers, and the most effective solutions. The book has been updated throughout, with new and revised material on CORBA, COM+, XML, BizTalk, the state of the component market, standards, and more -- including an insightful preview of the future. The First Edition's Java and Component Pascal examples are updated and supplemented with new C# examples; and many key topics are now illuminated by UML class diagrams. For all software architects, developers, and project managers seeking to use software components more effectively -- now, and in the future.

Sample Content

Table of Contents

Preface to the second edition.


About the author.

About the contributing authors.



1. Introduction.

Components are for composition.

Components–custom-made versus standard software.

Inevitability of components.

The nature of software and deployable entities.

Components are units of deployment.

Lessons learned. 2. Market versus technology.

Creating a market.

Fundamental properties of component technology.

Market development.

Strategic Focus (January 1995).

Ovum (1995).

IDC (May 1996).

IDC (April 1999).

ComponentSource (2001).

Flashline (2001). 3. Standards.

The utmost importance of (quasi) standards.

Wiring standards are not enough.

Too many competing standards are not useful.

Where is software component technology today?

What's next?


4. What a component is and is not.

Terms and concepts.



Components and objects.


Whitebox versus blackbox abstractions and reuse.


Explicit context dependencies.

Component “weight”.

Standardization and normalization.

Horizontal versus vertical markets.

Standard component worlds and normalization. 5. Components, interfaces, and re-entrance.

Components and interfaces.

Direct and indirect interfaces.


Interfaces as contracts.

Contracts and extra-functional requirements.

Undocumented “features”.

What belongs to a contract?

Safety and progress.

Extra-functional requirements.

Specifying time and space requirements.

Dress code–formal or informal?

Callbacks and contracts.

Examples of callbacks and contracts.

A directory service.

A client of the directory service.

Same client, next release.

A broken contract.

Prevention is better than cure.

Proofing the directory service.

Test functions in action.

From callbacks to objects.

From interobject consistency to object re-entrance.

Self-interference and object re-entrance: a summary.

Processes and multithreading.


Specification statements. 6. Polymorphism.

Substitutability–using one for another.

Types, subtypes, and type checking.

More on subtypes.

Object languages and types.

Types, interfaces, and components.

The paradigm of independent extensibility.

Safety by construction–viability of components.

Module safety.

Module safety and metaprogramming.

Safety in a multilanguage environment.

Safety, security, trust.

Dimensions of independent extensibility.

Bottleneck interfaces.

Singleton configurations.

Parallel, orthogonal, and recursive extensions.

Evolution versus immutability of interfaces and contracts.

Syntactic versus semantic contract changes.

Contract expiry.

Overriding law.

Other forms of polymorphism. 7. Object versus class composition or how to avoid inheritance.

Inheritance–the soup of the day?

More flavors to the soup.

Multiple inheritance.


Back to basic ingredients.

The fragile base class problem.

The syntactic fragile base class problem.

The semantic fragile base class problem.

Inheritance–more knots than meet the eye.

Approaches to disciplined inheritance.

The specialization interface.

Typing the specialization interface.

Behavioral specification of the specialization interface.

Reuse and cooperation contracts.

Representation invariants and method refinements.

Disciplined inheritance to avoid fragile base class problems.

Creating correct subclasses without seeing superclass code.

From class to object composition.

Forwarding versus delegation (or making object composition as problematical as implementation inheritance).

A brief review of delegation and inheritance. 8. Aspects of scale and granularity.

Units of abstraction.

Units of accounting.

Units of analysis.

Units of compilation.

Units of delivery.

Units of deployment.

Units of dispute.

Units of extension.

Units of fault containment.

Units of instantiation.

Units of installation.

Units of loading.

Units of locality.

Units of maintenance.

Units of system management.

Summary. 9. Patterns, frameworks, architectures.

Forms of design-level reuse.

Sharing consistency–programming languages.

Sharing concrete solution fragments–libraries.

Sharing individual contracts–interfaces.

Sharing individual interaction fragments–messages and protocols.

Sharing individual interaction architecture–patterns.

Sharing architecture–frameworks.

Sharing overall structure–system architecture.

Systems of subsystems–framework hierarchies.

Interoperability, legacies, and re-engineering. 10. Programming–shades of gray.

Different programming methods for different programmers.

Programming to a system.

Connection-oriented programming.

Connection-oriented programming–advanced concepts.

Events and messages.

Message syntax and schema–XML.

Events versus calls.

Call syntax and protocol–SOAP.

Ordering of events–causality, races, and glitches.

Very late binding–dispatch interfaces and metaprogramming.

Degrees of freedom–sandboxing versus static safety.

Recording versus scripting. 11. What others say.

Grady Booch (1987).

Oscar Nierstrasz and Dennis Tsichritzis (1992 and 1995).

Gio Wiederhold, Peter Wegner, and Stefano Ceri (1992).

Ivar Jacobson (1993).

Meta Group (1994).

Jed Harris (1995).

Ovum Report on Distributed Objects (1995).

Robert Orfali, Dan Harkey, and Jeri Edwards (1995, 1996).

Johannes Sametinger (1997).

UML 1.3 Standard (1999).

Desmond D'Souza and Alan Wills (1999).

Krzysztof Czarnecki and Ulrich Eisenecker (2000).

Peter Herzum and Oliver Sims (2000).

CBSE Handbook (2001).


12. Object and component “wiring” standards.

Where it all came from.

From procedures to objects.

The fine print.

Specification of interfaces and object references.

Interface relationships and polymorphism.

Naming and locating services.

Compound documents.

On the wire–the rise of XML.

XML, XML Namespaces, XML Schema.

XML support standards.

XML document object and streaming models.


XML web services: WSDL, UDDI, WSFL, XLANG.

Web services and programming models.

Which way? 13. The OMG way: CORBA, CCM, OMA, and MDA.

At the heart–the object request broker.

From CORBA to OMA.

CORBA timeline.

A bit of history–system object model (SOM).

Common object service specifications (CORBAservices).

Services supporting enterprise distributed computing.

Services supporting architecture using fine-grained objects.

CORBA Component Model.

Portable object adapter.

CCM components.

CCM containers.

CORBA-compliant implementations.

BEA's WebLogic.

IBM's WebSphere.

IONA's Orbix E2A Application Server Platform.

Borland's Enterprise Server.

Non-for-profit implementations.


Application objects.


Meta-object facility.

Model-driven architecture (MDA). 14. The Sun way–Java, JavaBeans, EJB, and Java 2 editions.

Overview and history of Java component technologies.

Java versus Java 2.

Runtime environment and reference implementations.

Spectrum of editions–Micro, Standard, and Enterprise.

Java, the language.

Interfaces versus classes.

Exceptions and exception handling.

Threads and synchronization.

Garbage collection.


Events and connections.



JAR files–packaging of Java components.

Basic Java services.


Object serialization.

Java native interface.

Java AWT and JFC/Swing.

Advanced JavaBeans specifications.

Component variety–applets, servlets, beans, and Enterprise beans.

Java server pages (JSP) and servlets.

Contextual composition–Enterprise JavaBeans (EJB).

Data-driven composition–message-driven beans in EJB 2.0.

Advanced Java services.

Distributed object model and RMI.

Java and CORBA.

Enterprise service interfaces.

Java and XML.

Interfaces versus classes in Java, revisited.

JXTA and Jini.

Jini–federations of Java objects.

JXTA–peer-to-peer computing.

Java and web services–SunONE. 15. The Microsoft way: COM, OLE/ActiveX, COM+, and .NET CLR.

The first fundamental wiring model–COM.

COM object reuse.

Interfaces and polymorphism.


Interfaces and versioning.

COM object creation and the COM library.

Initializing objects, persistence, structured storage, monikers.

From COM to distributed COM (DCOM).

Meta-information and automation.

Other COM services.

Uniform data transfer.

Dispatch interfaces (dispinterfaces) and dual interfaces.

Outgoing interfaces and connectable objects.

Compound documents and OLE.

OLE containers and servers.

Controls–from Visual Basic via OLE to ActiveX.

Contextual composition and services.

COM apartments–threading and synchronization.

Microsoft transaction server–contexts and activation.

COM+–generalized contexts and data-driven composition.

Take two–the .NET Framework.

The .NET big picture.

Common language infrastructure.

COM and platform interoperation.

Exemplary .NET language–C#.

Visual Studio .NET.

Assemblies–the .NET components.

Common language frameworks.

AppDomains, contexts, reflection, remoting.

Windows Forms, data, management.

Web Forms, Active Server Pages (ASP) .NET.

XML and data.

Enterprise services.

Web services with .NET. 16. Some further technologies.

Computer Associates' Advantage Plex.

Hitachi Appgallery.

Groove Transceiver. 17. Strategic comparison.

Shared attributes.


Consequences for infrastructure vendors.

Consequences for component vendors. 18. Efforts on domain standards.

OMG Domain Technology Committee.



Business processes and documents.

OASIS and ebXML.

RosettaNet and PIPs.



Java domain standard efforts.

OLE for process control.

Industry associations.

Information technology industry groupings.

Trade associations.

User associations. 19. Ongoing concerns.

Domain standards.

Rethinking the foundations of software engineering.

But is it object-oriented?

Object mobility and mobile agents.

Foundations–better contracts for better components.

part four Components meet architecture and process.

20. Component architecture.

The roles of an architecture.

Conceptualization–beyond objects?

Definitions of key terms.

A tiered component architecture.

Components and middleware.

Components versus generative programming. 21. Component frameworks.

Contributions of contextual component frameworks.

Foundation and roots.

Component frameworks versus connectors.

Component frameworks versus metaprogramming.

Component frameworks versus aspect-oriented programming.

Frameworks for contextual composition.

COM+ contexts.

EJB containers.

CCM containers.

CLR contexts and channels.

Tuple and object spaces.

BlackBox component framework.

Carrier-rider-mapper design pattern.

Directory objects.

Hierarchical model view separation.

Container modes.

Cascaded message multicasting services.

Advanced applications based on compound documents.

BlackBox and OLE.

Portos–a hard realtime component framework and its IDE.

Structure of Portos.

Realtime scheduler.

Cross-development environment. 22. Component development.

The methodology–component-oriented programming.

Problems of asynchrony.


Learning from circuit design.

Living without implementation inheritance.

Nutshell classes.

Language support.

Dynamic base objects with forwarding semantics.

Caller encapsulation.

The environment–selecting target frameworks.

The tools–selecting programming languages. 23. Component distribution and acquisition.

Building what sells–applications not components?

Product cataloging and description.

Component location and selection.


Intermediaries. 24. Component assembly.

Systematic initialization and wiring.

Visual component assembly.

Compound documents to supersede visual assembly.

Components beyond graphical user interface environments.

Managed and “self-guided” component assembly.

End-user assembly.

Component evolution. 25. On the horizon.

Advanced object composition.


Split objects.

Environmental acquisition.

Dynamic inheritance.

New forms of object and component abstraction.

Subject-oriented programming.

Aspect-oriented programming.

XML components.

part five Markets and components.

26. Gamut of markets.


Component platforms and infrastructure.


Component design and implementation tools.

Component testing tools.

Component assembly tools.

Component system diagnosis and maintenance.

Professional services.

Component system and framework architects.

Component assembly consultants.

Component configuration management.

Component warehouses, marketing, and consulting.

Component operators, web services, application service providers. 27. New professions.

Component system architect.

Component framework architect.

Component developer.

Component assembler. 28. A component marketing paradox.


Pay per use.

Co-placement of advertisements.

Leveraging on newly created markets.

Leverage of integrative forces. Epilogue.
Appendix A Java versus C# versus Component Pascal.
Useful addresses and bibliography.


Submit Errata

More Information

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