Results 1 - 10
of
31
Classification of Model Transformation Approaches
, 2003
"... The Model-Driven Architecture (MDA) [Fra03] is an initiative by the Object Management Group (OMG) to define an approach to software development based on modeling and automated mapping of models to implementations. The basic MDA pattern involves defining a platformindependent model (PIM) and its auto ..."
Abstract
-
Cited by 274 (3 self)
- Add to MetaCart
(Show Context)
The Model-Driven Architecture (MDA) [Fra03] is an initiative by the Object Management Group (OMG) to define an approach to software development based on modeling and automated mapping of models to implementations. The basic MDA pattern involves defining a platformindependent model (PIM) and its automated mapping to one or more platform-specific models
Feature-based survey of model transformation approaches
, 2006
"... Model transformations are touted to play a key role in Model Driven Developmente. Although well-established standards for creating metamodels such as the Meta-Object Facility exist, there is currently no mature foundation for specifying transformations among models. We propose a framework for the cl ..."
Abstract
-
Cited by 196 (4 self)
- Add to MetaCart
Model transformations are touted to play a key role in Model Driven Developmente. Although well-established standards for creating metamodels such as the Meta-Object Facility exist, there is currently no mature foundation for specifying transformations among models. We propose a framework for the classification of several existing and proposed model transformation approaches. The classification framework is given as a feature model that makes explicit the different design choices for model transformations. Based on our analysis of model transformation approaches, we propose a few major categories in which most approaches fit.
Software factories: assembling applications with patterns, models, frameworks and tools
, 2004
"... The confluence of component based development, model driven development and software product lines forms an approach to application development based on the concept of software factories. This approach promises greater gains in productivity and predictability than those produced by incremental impro ..."
Abstract
-
Cited by 182 (0 self)
- Add to MetaCart
(Show Context)
The confluence of component based development, model driven development and software product lines forms an approach to application development based on the concept of software factories. This approach promises greater gains in productivity and predictability than those produced by incremental improvements to the current paradigm of object orientation, which have not kept pace with innovation in platform technology. Software factories promise to make application assembly more cost effective through systematic reuse, enabling the formation of supply chains and opening the door to mass customization. Categories and Subject Descriptors D.2.2 [Design Tools and Techniques], D.2.11 [Software
Formalizing cardinality-based feature models and their specialization
- Software Process: Improvement and Practice
, 2005
"... Abstract Feature modeling is an important approach to capture the commonalities and variabilities in system families and product lines. Cardinality-based feature modeling integrates a number of existing extensions of the original feature-modeling notation from Feature-Oriented Domain Analysis. Stage ..."
Abstract
-
Cited by 169 (18 self)
- Add to MetaCart
(Show Context)
Abstract Feature modeling is an important approach to capture the commonalities and variabilities in system families and product lines. Cardinality-based feature modeling integrates a number of existing extensions of the original feature-modeling notation from Feature-Oriented Domain Analysis. Staged configuration is a process that allows the incremental configuration of cardinality-based feature models. It can be achieved by performing a step-wise specialization of the feature model. In this paper, we argue that cardinality-based feature models can be interpreted as a special class of context-free grammars. We make this precise by specifying a translation from a feature model into a context-free grammar. Consequently, we provide a semantic interpretation for cardinalitybased feature models by assigning an appropriate semantics to the language recognized by the corresponding grammar. Finally, we give an account on how feature model specialization can be formalized as transformations on the grammar equivalent of feature models.
Staged configuration using feature models
- SOFTWARE PRODUCT LINES: THIRD INTERNATIONAL CONFERENCE, SPLC 2004
, 2004
"... Feature modeling is an important approach to capturing commonalities and variabilities in system families and product lines. In this paper, we propose a cardinality-based notation for feature modeling, which integrates a number of existing extensions of previous approaches. We then introduce and mot ..."
Abstract
-
Cited by 108 (4 self)
- Add to MetaCart
Feature modeling is an important approach to capturing commonalities and variabilities in system families and product lines. In this paper, we propose a cardinality-based notation for feature modeling, which integrates a number of existing extensions of previous approaches. We then introduce and motivate the novel concept of staged configuration. Staged configuration can be achieved by the stepwise specialization of feature models. This is important because in a realistic development process, different groups and different people eliminate product variability in different stages. We also indicate how cardinality-based feature models and their specialization can be given a precise formal semantics.
Overview of generative software development
- In Proceedings of Unconventional Programming Paradigms (UPP) 2004, 15-17 September, Mont Saint-Michel, France, Revised Papers
, 2004
"... Abstract. System family engineering seeks to exploit the commonalities among systems from a given problem domain while managing the variabilities among them in a systematic way. In system family engineering, new system variants can be rapidly created based on a set of reusable assets (such as a comm ..."
Abstract
-
Cited by 53 (4 self)
- Add to MetaCart
(Show Context)
Abstract. System family engineering seeks to exploit the commonalities among systems from a given problem domain while managing the variabilities among them in a systematic way. In system family engineering, new system variants can be rapidly created based on a set of reusable assets (such as a common architecture, components, models, etc.). Generative software development aims at modeling and implementing system families in such a way that a given system can be automatically generated from a specification written in one or more textual or graphical domainspecific languages. This paper gives an overview of the basic concepts and ideas of generative software development including DSLs, domain and application engineering, generative domain models, networks of domains, and technology projections. The paper also discusses the relationship of generative software development to other emerging areas such as Model Driven Development and Aspect-Oriented Software Development. 1
A document-oriented paradigm for the construction of content-intensive applications
- The Computer Journal
, 2006
"... In this paper we describe our work on the formulation of a document-oriented paradigm for improving the construction and maintenance of content-intensive applications (i.e. applications that make intensive use of the information provided by the experts in a given domain: the contents). According to ..."
Abstract
-
Cited by 12 (8 self)
- Add to MetaCart
(Show Context)
In this paper we describe our work on the formulation of a document-oriented paradigm for improving the construction and maintenance of content-intensive applications (i.e. applications that make intensive use of the information provided by the experts in a given domain: the contents). According to this paradigm, the development of a content-intensive application must be the result of close collaboration between two kinds of actors: domain experts and developers. The goal of this collaboration is the authoring of (i) a set of documents describing the most relevant aspects of the application (i.e. the contents and other relevant customizable features); (ii) a grammar describing a domain-specific markup language that will be used to make the structure and the data in these documents explicit and (iii) a suitable processor for this language. The final running application will be automatically produced by processing the marked documents with this processor. The use of this paradigm in the development of content-intensive applications can increase the initial cost of application production, but in the long run it can substantially improve maintenance and portability, and promote information and software reuse as well. We have successfully applied this paradigm to the development of educational and hypermedia applications, and knowledge-based systems. From these experiences, we have found that the feasibility of the paradigm depends to a
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
Pattern-Based Tool Support for Frameworks: Towards Architecture-Oriented Software Development Environment
, 2005
"... Software engineering aims at techniques for producing better software products with less resources. A central concept for achieving this goal is a product line architecture. Frameworks are a popular object-oriented way to implement product line architectures. However, frameworks are often difficult ..."
Abstract
-
Cited by 7 (0 self)
- Add to MetaCart
Software engineering aims at techniques for producing better software products with less resources. A central concept for achieving this goal is a product line architecture. Frameworks are a popular object-oriented way to implement product line architectures. However, frameworks are often difficult to learn and their specializations consist of small and crosscutting logical entities that overlap with other design solutions of the software product. Implementation becomes fragmented, difficult to trace, and the original reasoning of the design is easily forgotten. Thus, the essential problems to be solved are the following: • How to teach the software developer to understand different frameworks and design principles in the context of her software product? • How to guide the software developer to use frameworks and product line architectures? • How to maintain and document implemented design solutions and framework specializations? In this
A Component Assembly Architecture with Two-Level Grammar Infrastructure
- Proc. of OOPSLA’2002 Workshop Generative Techniques in the Context of Model Driven Architecture, 2002. http://www.softmetaware.com/oopsla2002/zhaow.pdf engineering: Model Transformations Requirements Requirement Model in GME Architecture Model in GME Sea
"... Being able to generate a concrete software product from domain specifications, upon an order requirement 5, still remains a mirage using most modern software engineering techniques. To provide a systematic way to automate software engineering process, formal models should be constructed beforehand t ..."
Abstract
-
Cited by 5 (5 self)
- Add to MetaCart
(Show Context)
Being able to generate a concrete software product from domain specifications, upon an order requirement 5, still remains a mirage using most modern software engineering techniques. To provide a systematic way to automate software engineering process, formal models should be constructed beforehand to capture the various aspects of engineering knowledge for any
