Results 1 - 10
of
10
A Highly-Extensible, XML-Based Architecture Description Language
- Proceedings of the Working IEEE/IFIP Conference on Software Architecture
, 2001
"... Software architecture research focuses on models of software architectures as specified in architecture description languages (ADLs). As research progresses in specific areas of software architectures, more and more architectural information is created. Ideally, this information can be stored in the ..."
Abstract
-
Cited by 109 (17 self)
- Add to MetaCart
(Show Context)
Software architecture research focuses on models of software architectures as specified in architecture description languages (ADLs). As research progresses in specific areas of software architectures, more and more architectural information is created. Ideally, this information can be stored in the model. An extensible modeling language is crucial to experimenting with and building tools for novel modeling constructs that arise from evolving research. Traditional ADLs typically support a small set of modeling constructs very well, but adapt to others poorly. XML provides an ideal platform upon which to develop an extensible modeling language for software architectures. Previous XML-based ADLs successfully leveraged XML’s large base of off-the-shelf tool support, but did not take advantage of its extensibility. To give software architecture researchers more freedom to explore new possibilities and modeling techniques while maximizing reuse of tools and modeling constructs, we have developed xADL 2.0, a highly extensible XML-based ADL. xADL 2.0 supports run-time and design time modeling, architecture configuration management and model-based system instantiation. Additionally, xADL 2.0 has a set of extensible infrastructure tools that support the creation, manipulation, and sharing of xADL 2.0 documents.
Towards Testing Product Line Architectures
- In: International Workshop on Testing and Analysis of Component Based Systems
, 2003
"... A product line architecture is a single specification capturing the overall architecture of a series of closely related products. Its structure consists of a set of mandatory elements and a set of variation points. Whereas mandatory elements are part of the architecture of every product in the produ ..."
Abstract
-
Cited by 14 (1 self)
- Add to MetaCart
(Show Context)
A product line architecture is a single specification capturing the overall architecture of a series of closely related products. Its structure consists of a set of mandatory elements and a set of variation points. Whereas mandatory elements are part of the architecture of every product in the product line architecture, variation points precisely define the dimensions along which the architectures of individual products di#er from each other.
Representing Product Family Architectures in an Extensible Architecture Description Language
- In Proceedings of the International Workshop on Product Family Engineering (PFE-4
, 2001
"... . Product family architectures need to be captured much like "regular " software architectures. Unfortunately, representations for product family architectures are scarce and a deep understanding of all of the necessary features of such representations is still lacking. In this paper, w ..."
Abstract
-
Cited by 12 (2 self)
- Add to MetaCart
(Show Context)
. Product family architectures need to be captured much like "regular " software architectures. Unfortunately, representations for product family architectures are scarce and a deep understanding of all of the necessary features of such representations is still lacking. In this paper, we introduce an extensible XML-based representation that is suitable as a basis for rapidly defining new representations for product family architectures. We describe some of the details of this representation and present how Koala and Mae, two early representations for product family architectures, can be mapped onto our XML-based representation with relatively little effort. 1
Managing Variability Using Heterogeneous Feature Variation Patterns
- In FASE
"... Abstract. Feature-driven variability is viewed as an instance of multi-dimensional separation of concerns. We argue that feature variation con-cerns can be presented as pattern-like entities- called feature variation patterns- cross-cutting heterogeneous artifacts. We show that a feature variation p ..."
Abstract
-
Cited by 9 (0 self)
- Add to MetaCart
(Show Context)
Abstract. Feature-driven variability is viewed as an instance of multi-dimensional separation of concerns. We argue that feature variation con-cerns can be presented as pattern-like entities- called feature variation patterns- cross-cutting heterogeneous artifacts. We show that a feature variation pattern, covering a wide range of artifact types from a feature model to implementation, can be used to manage feature-driven vari-ability in a software development process. A prototype tool environment has been developed to demonstrate the idea, supporting the specifica-tion and use of heterogeneous feature variation patterns. We illustrate the idea with a small example taken from J2EE, and further study the practical applicability of the approach in an industrial product-line. 1
Modelling Configurable Products and Software Product Families
- in Proc. of the International Joint Conference on Artificial Intelligence (IJCAI-2001) - Workshop on Configuration
, 2001
"... Software product families are an emerging and important area of software engineering, whereas product configuration of traditional products, i.e., mechanical and electronic, has a slightly longer history as a specific area of research and business. This paper presents a preliminary comparison o ..."
Abstract
-
Cited by 2 (0 self)
- Add to MetaCart
Software product families are an emerging and important area of software engineering, whereas product configuration of traditional products, i.e., mechanical and electronic, has a slightly longer history as a specific area of research and business. This paper presents a preliminary comparison of concepts for modelling variety and evolution in both fields.
A Brief Survey of Software Architecture
, 2002
"... Software of today is becoming larger and more complex. More powerful ways of structuring complexity are consequently required, whether it is about development methodologies, structural programming, naming conventions, configuration management, or, as is discussed in this report, software architectur ..."
Abstract
-
Cited by 2 (0 self)
- Add to MetaCart
Software of today is becoming larger and more complex. More powerful ways of structuring complexity are consequently required, whether it is about development methodologies, structural programming, naming conventions, configuration management, or, as is discussed in this report, software architecture.
A Technique to Identify Component Interfaces
"... To understand a component and how it is used in a system, an engineer must understand the externally visible properties and relationships with other components. We applied a technique, Interface Identification, to a product's source code to identify all of the interfaces between a component and ..."
Abstract
-
Cited by 1 (0 self)
- Add to MetaCart
To understand a component and how it is used in a system, an engineer must understand the externally visible properties and relationships with other components. We applied a technique, Interface Identification, to a product's source code to identify all of the interfaces between a component and the system. This permitted us to quickly harvest a component from one product for reuse in a new one. The technique relies on source code and knowledge of what source files make up a component. A reverse engineering tool aids the process.
A Marriage of MDD and Early Aspects in Software Product Line Development Thais Batista SETE — Software Engineering Team
"... Model-driven development (MDD) shifts the development focus from code to models, allowing automatic or assisted transformations that are able to generate more refined, detailed or complete models. In Software Product Line (SPL) development, variation point implementation might inevitable lead to (cr ..."
Abstract
-
Cited by 1 (0 self)
- Add to MetaCart
(Show Context)
Model-driven development (MDD) shifts the development focus from code to models, allowing automatic or assisted transformations that are able to generate more refined, detailed or complete models. In Software Product Line (SPL) development, variation point implementation might inevitable lead to (crosscutting) concerns that are tangled and spread with other concerns, suggesting the use of aspect-oriented (AO) approaches. In this context, Early Aspects techniques can be applied to identify crosscutting concerns at early development process stages, positively affecting the application models as soon as possible. In this work we propose a marriage of MDD and early aspects for the development of SPL. Our approach takes an AO feature model and automatically transforms it into an AO early design model and this model into an AO architecture specification. We applied our proposal to a real-life SPL to better exemplify its use. 1.
2 OVERVIEW OF VARIABILITY MANAGEMENT.........................................2 2.1 FAMILY BASED DEVELOPMENT PROCESS..........................................................2 2.2 EXPRESSING REQUIREMENTS IN TERMS OF FEATURES................................
"... ..."
(Show Context)
