By Topic

Software support for configuring distributed object based systems

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$33 $33
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

1 Author(s)
J. Kramer ; Dept. of Comput., Imperial Coll., London, UK

There is some consensus on the set of techniques and mechanisms which should be used to construct distributed systems. However, none of these mechanisms help in the design process of decomposing an overall application into a set of components nor in its subsequent construction. They are rather the `glue' used to compose components such that they may communicate and interact. What is missing is any motion of structure. The premise of the author's approach is that a separate, explicit structural (configuration) description is essential for all phases in the software development process for distributed systems, from system specification as a configuration of component specifications to evolution as changes to a system configuration. Descriptions of the constituent software components and their interconnection patterns provide a clear and concise level at which to specify and design systems, and can be used directly by construction tools to generate the system itself. The author uses the neutral term `component' to mean a software entity which encapsulates some resources and provides a well defined interface in terms of the operations it provides to access the resources and the operations it requires to implement its functionality. Further, these components must be `context independent' in that they use only local names to communicate with their environment, thereby allowing them to be developed independently of the context in which they execute

Published in:

Distributed Object Management, IEE Colloquium on

Date of Conference:

14 Jan 1994