Dashofy, E. M., van der Hoek, A., Taylor, R. N.: A highly-extensible, XML-based architecture description language, Proceedings of WICSA'01, Amsterdam, Netherlands, August 2001  Home/Search   Document Not in Database   Summary   Related Articles   Check

....and representation schemes for architectures, we adopt a simple scheme in which an architectural model is represented as a graph of interacting components. This is the core architectural representation scheme adopted by a number of architecture description languages, including Acme [11] xADL [8], and SADL [23] Nodes in the graph are termed components. They represent the principal computational elements and data stores of the system: clients, servers, databases, user interfaces, etc. Arcs are termed connectors, and repre sent the pathways of interaction between the components. A given ....

Dashofy, E., van der Hoek, A., and Taylor, R.N. A Highly-Extensible, XML-Based Architecture Description Language. Proceedings of the Working IEEE/IFIP Conference on Software Architecture, Amsterdam, The Netherlands, August 2001.

....a support environment to manage its evolving structure an area of research that has largely been ignored to date. This paper introduces Mnage, an environment that is specifically designed to fill this void. Mnage builds upon our existing representation for product line architectures, xADL 2. 0 [9,10], to provide a software architect with three capabilities that are explicitly geared towards managing an evolving product line architecture. First, Mnage supports the specification of a product line architecture as a set of core architectural elements that is augmented with variation points. These ....

E.M. Dashofy, A. van der Hoek, and R.N. Taylor. A Highly-Extensible, XML-Based Architecture Description Language. Proceedings of the Working IEEE/IFIP Conference on Software Architecture, 2001.

....must be checked and enforced with external semantically aware tools. This is not different from traditional language development. 3.2 xADL 2.0 The second part of our infrastructure is a set of reusable schemas that can be used as the basis for developing new ADLs, collectively known as xADL 2. 0 [12]. To maximize the reusability and applicability of these schemas, we have endeavored to make them as generic as possible. For instance, our schemas define components and connectors, but not their behaviors or how they can be linked together. These aspects are an important part of many ADLs, and we ....

....links. Architectural Evolution Management Product Line Architectures Variant design time component and connector types. Table 2. xADL 2.0 schemas and features. The VERSIONS schema adds versioning constructs to xADL 2.0. In xADL 2. 0, architecture element types are the versioned entities [12]. The VERSIONS schema defines version graphs for component, connector, and interface types. These version graphs capture the evolution of individual elements in an architecture, and, using the subarchitectures mechanism defined in the STRUCTURE TTYPES schema, can capture the evolution of groups ....

[Article contains additional citation context not shown here]

E. Dashofy, A. van der Hoek, and R. N. Taylor. A HighlyExtensible, XML-Based Architecture Description Language. In Proceedings of the Working IEEE/IFIP Conference on Software Architectures (WICSA 2001), Amsterdam, Netherlands.

....changes. Nonetheless, these algorithms form a solid basis upon which our approach is based. Specifically, we have adapted them in making three contributions to the field of software architecture. First, we have enhanced an existing representation for product line architectures, xADL 2. 0 [5], with a representation in which the exact difference between two products in a product line architecture can be captured. Second, we have created a differencing algorithm that uses the representation to create an understanding of the exact set of architectural changes that constitute a difference ....

....related changes that constitute a replacement are not detected unless the changes happen to be in a consecutive part of the XML file. Nonetheless, the algorithms described in this paper fall in the same class as these semantic algorithms and build upon the results to date. 3. xADL 2.0 xADL 2. 0 [5,7] is an extensible representation for product line architectures that was born out of the observation that, while each new architecture description language usually contributes some kind of unique feature, most share a relatively large set of common modeling concepts [15] To leverage this ....

Dashofy, E., van der Hoek, A., and Taylor, R.N. A Highly-Extensible, XML-Based Architecture Description Language. In Proceedings of the The Working IEEE/IFIP Conference on Software Architecture (WICSA

....for capturing product family aspects of those architectures. 3. XML [2] schemas provide a useful platform upon which to build extensible, modular representations. In this paper, we describe our efforts in building an extensible, XML based representation for product family architectures, xADL 2. 0 [4]. Key contributions of xADL 2.0 are its set of modular XML schemas that provide a basic framework for modeling product family architectures, its extensibility to allow future additions to (and modifications of) elements in the representation, and its associated tool support to automatically ....

....can only co exist if the sets of component types covered by the extensions are mutually exclusive. This means that a component type cannot have both a subtype and style, weakening our extensibility through modularity argument. We, thus, have introduced artificial dependencies as a solution (see [4]) For instance, in the above case, we could make the subtype extension an extension of the style extension, or vice versa. Because both the style and subtype tags are optional, it is possible to have a component type with a subtype, a style, or both. Nonetheless, this is not an ideal solution and ....

Dashofy, E.M., van der Hoek, A., and Taylor, R.N., A Highly-Extensible, XML-Based Architecture Description Language,inWorking IEEE/IFIP Conference on Software Architecture. 2001 (to appear).

....composition of a system out of other partial systems and components, for managing the versions and variants in which a component may exist, and for capturing behaviors and constraints such that they can be analyzed at composition time. A software architecture description language such as xADL 2. 0 [5] provides these facilities and, thus, is an ideal platform to serve as a system model for component based software. Events: Because of the decentralized nature of component based software development and the high likelihood of participating organizations having different configuration ....

Dashofy, E.M., van der Hoek, A., and Taylor, R.N., A Highly-Extensible, XML-Based Architecture Description Language, in Working IEEE/IFIP Conference on Software Architecture. 2001 (to appear).

No context found.

Dashofy, E. M., van der Hoek, A., Taylor, R. N.: A highly-extensible, XML-based architecture description language, Proceedings of WICSA'01, Amsterdam, Netherlands, August 2001

No context found.

E. Dashofy, A. van der Hoek, and R. Taylor. A Highly-Extensible, XML-Based Architecture Description Language. In Proceedings of the Working IEEE/IFIP Conference on Software Architectures (WICSA 2001.

No context found.

E. Dashofy, A. van der Hoek, and R. Taylor. A Highly-Extensible, XML-Based Architecture Description Language. In Proceedings of the Working IEEE/IFIP Conference on Software Architectures (WICSA 2001.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC