General Navigation Buttons - Home | Search | Contact Us | Site Map | Whats New
products graphic
white space
products
Software Technology Roadmap
What's New
Background & Overview
Technology Descriptions
Defining Software Technology
Technology Categories
Template for Technology Descriptions
Taxonomies
Glossary & Indexes
Feedback & Participation
Software Engineering Information Repository (SEIR)
white space
About SEI|Mgt|Eng|Acq|Collaboration|Prod.& Services|Pubs
pixel
Rollover Popup Hints for Topic Navigation Buttons above
pixel
Distributed/Collaborative Enterprise Architectures


Status

Advanced

Note

We recommend Client/Server Software Architectures as prerequisite reading for this technology description.

Purpose and Origin

The distributed/collaborative enterprise architecture emerged in 1993. This software architecture is based on Object Request Broker (ORB) technology, but goes further than the Common Object Request Broker Architecture (CORBA) by using shared, reusable business models (not just objects) on an enterprise-wide scale.1 The benefit of this architectural approach is that standardized business object models and distributed object computing are combined to give an organization flexibility, scalability, and reliability and improve organizational, operational, and technological effectiveness for the entire enterprise. This approach has proven more cost effective than treating the individual parts of the enterprise. For detailed information on distributed/collaborative enterprise architectures see Shelton and Adler [Shelton 93, Adler 95].

Technical Detail

The distributed/collaborative enterprise architecture allows a business to analyze its internal processes in new ways that are defined by changing business opportunities instead of by preconceived systems design (such as monolithic data processing applications). In this architectural design, an object model represents all aspects of the business; what is known, what the business does, what are the constraints, and what are the interactions and the relationships. A business model is used to integrate and migrate parts of legacy systems to meet the new business profile.

Distributed/collaborative enterprise builds its new business applications on top of distributed business models and distributed computing technology. Applications are built from standard interfaces with "plug and play" components. At the core of this infrastructure is an off-the-shelf, standards-based, distributed object computing, messaging communication component such as an Object Request Broker (ORB) that meets Common Object Request Broker Architecture (CORBA) standards.

This messaging communication hides the following from business applications:

  • the implementation details of networking and protocols
  • the location and distribution of data, process, and hosts
  • production environment services such as transaction management, security, messaging reliability, and persistent storage
The message communication component links the organization and connects it to computing and information resources via the organization's local or wide area network (LAN or WAN). The message communication component forms an enterprise-wide standard mechanism for accessing computing and information resources. This becomes a standard interface to heterogeneous system components.

Usage Considerations

The distributed/collaborative enterprise architecture is being applied in industries and businesses such as banking, investment, trading, credit-granting, insurance, policy management and rating, customer service, transportation and logistics management, telecommunications (long distance, cellular, and operating company), customer support, billing, order handling, product cross-selling, network modeling, manufacturing equipment, and automobiles [Shelton 93].

The most common implementations of objects and object models are written in C++ or Smalltalk. Another popular language for implementing object and object models is Java.

Available for use in a distributed/collaborative enterprise architecture are products being built to open system standards, operating systems, database management systems, transaction processor monitors, and ORBs. These products are increasingly interchangeable.

Maturity

Since 1993 a number of companies have built and used distributed/collaborative architectures to address their long-term business needs because this model adapts to change and is built according to open system standards [Adler 95].

Costs and Limitations

Distributed/collaborative enterprise architectures are limited by the lack of commercially-available, object-oriented analysis and design method tools that focus on applications (rather than large scale business modeling).

Dependencies

The evolution of CORBA (see Common Object Request Broker Architecture) and COM/DCOM (see Component Object Model (COM), DCOM, and Related Capabilities), and the results of standards bodies such as X/Open [X/Open 96] and Object Management Group (OMG) [OMG 96] will affect the evolution of distributed/collaborative architectures.

Alternatives

Three tier client/server architectures (see Three Tier Software Architectures) are an alternative approach to distributed/collaborative architectures. However, they do not address the need to evolve the business model over time as well as the distributed/collaborative architecture does.

Complementary Technologies

Distributed/collaborative enterprise architectures are enhanced by object-oriented design technologies (see Object-Oriented Design).

Index Categories

This technology is classified under the following categories. Select a category for a list of related topics.

Name of technology

Distributed/Collaborative Enterprise Architectures

Application category

Client/Server (AP.2.1.2.1)

Quality measures category

Scalability (QM.4.3)
Reliability (QM.2.1.2)
Maintainability (QM.3.1)

Computing reviews category

Distributed Systems (C.2.4)
Software Engineering Design (D.2.10)

References and Information Sources

[Adler 95] Adler, R. M. "Distributed Coordination Models for Client/Sever Computing." Computer 28, 4 (April 1995): 14-22.
[Lewis 95] Lewis, T. G. "Where is Client/Server Software Headed?" Computer 28, 4 (April 1995): 49-55.
[OMG 96] Object Management Group home page [online]. Available WWW
<URL: http://www.omg.org> (1996).
[Shelton 93] Shelton, Robert E. "The Distributed Enterprise (Shared, Reusable Business Models the Next Step in Distributed Object Computing)." Distributed Computing Monitor 8, 10 (October 1993): 1.
[X/Open 96] X/Open Web Site [online]. Available WWW
<URL: http://www.rdg.opengroup.org/> (1996).

Current Author/Maintainer

Darleen Sadoski, GTE

External Reviewers

Larry Stafford, GTE

Modifications

25 June 97: modified/updated OLE/COM reference to COM/DCOM
20 June 97: updated URLs for [OMG 96] and [X/Open 96]
10 Jan 97 (original)

Footnotes

1 An enterprise is defined as a system comprised of multiple business systems or multiple subsystems.



The Software Engineering Institute (SEI) is a federally funded research and development center sponsored by the U.S. Department of Defense and operated by Carnegie Mellon University.

Copyright 2007 by Carnegie Mellon University
Terms of Use
URL: http://www.sei.cmu.edu/str/descriptions/distcoll_body.html
Last Modified: 11 January 2007