The Object Management Group's (OMG) Model Driven Architecture (MDA) strategy envisages a world where models play a more direct role in software production, being amenable to manipulation and transformation by machine. Model Driven Engineering (MDE) is wider in scope than MDA. MDE combines process and analysis with architecture. This article sets out a framework for model driven engineering, which can be used as a point of reference for activity in this area. It proposes an organisation of the modelling 'space' and how to locate models in that space. It discusses different kinds of mappings between models. It explains why process and architecture are tightly connected. It discusses the importance and nature of tools. It identifies the need for defining families of languages and transformations, and for developing techniques for generating/configuring tools from such definitions. It concludes with a call to align metamodelling with formal language engineering techniques.

Model Driven Engineering

Thank you for reading software product line engineering foundations principles and techniques. Maybe you have knowledge that, people have look numerous times for their favorite books like this software product line engineering foundations principles and techniques, but end up in malicious downloads. Rather than reading a good book with a cup of coffee in the afternoon, instead they are facing with some infectious bugs inside their desktop computer.

Software Product Line Engineering Foundations Principles And Techniques

Service Oriented Architecture Concepts Technology And Design

Feature models have been used since the 90s to describe software product lines as a way of reusing common parts in a family of software systems. In 2010, a systematic literature review was published summarizing the advances and settling the basis of the area of automated analysis of feature models (AAFM). From then on, different studies have applied the AAFM in different domains. In this paper, we provide an overview of the evolution of this field since 2010 by performing a systematic mapping study considering 423 primary sources. We found six different variability facets where the AAFM is being applied that define the tendencies: product configuration and derivation; testing and evolution; reverse engineering; multi-model variability-analysis; variability modelling and variability-intensive systems. We also confirmed that there is a lack of industrial evidence in most of the cases. Finally, we present where and when the papers have been published and who are the authors and institutions that are contributing to the field. We observed that the maturity is proven by the increment in the number of journals published along the years as well as the diversity of conferences and workshops where papers are published. We also suggest some synergies with other areas such as cloud or mobile computing among others that can motivate further research in the future.

/pdf/automated-analysis-of-feature-models-quo-vadis-2fcmkq1klx.pdf

Automated analysis of feature models: Quo vadis?

A Systematic Literature Review of iStar extensions

The reuse of goal models has received only limited attention in the goal modeling community and is mostly related to the use of goal catalogues, which may be imported into the goal model of an application under development. Two important factors need to be considered when reusing goal models. First, a key purpose of a goal model is its evaluation for trade-off analysis, which is often based on propagating the contributions of low-level tasks representing considered solutions to high-level goals as specified in the goal model. Second, goal models are rarely used in isolation, but are combined with other models that impose additional constraints on goal model elements, in particular on tasks. For example, workflow models describe causal relationships of tasks in goal models. Similarly, feature models describe further constraints on tasks, in terms of which tasks may be selected at the same time. This paper i argues that reusable goal models must be specified either with real-life measurements if available or with relative contributions, ii presents a novel evaluation mechanism that enables the reuse of goal models with relative contributions, while taking into account additional constraints on tasks in the goal model expressed with feature models, and iii discusses a proof-of-concept implementation of the novel evaluation mechanism.

On the Reuse of Goal Models

A fundamental task when reusing software artifacts is to determine the most appropriate artifact for the current reuse context. Goal modeling allows modelers to capture the advantages and disadvantages of reusable candidate artifacts, which in turn helps reason about the most appropriate candidate artifact. However, goal models are rarely used in isolation for the description of an artifact, but are combined with other models that impose additional constraints on the most appropriate candidate. Furthermore, reusable artifacts are assembled into reuse hierarchies to realize an application. This paper presents a novel goal model evaluation mechanism for the selection of the most appropriate candidate, which (i) takes into account additional configuration constraints expressed with feature models and run-time constraints expressed with workflow models that may affect the selection of reusable software artifacts, (ii) considers reuse hierarchies, and (iii) establishes a history of design decisions. Furthermore, a proof-of-concept implementation of the novel evaluation mechanism is discussed.

Investigation of feature run-time conflicts on goal model-based reuse

A new unit of encapsulation called the concern is at the center of Concern-Orientation. Building on techniques for advanced Separation of Concerns, from Model-Driven Engineering, and from Software Product Lines, Concern-Orientation is a reuse paradigm that stipulates the use of three interfaces to enable broad, generic reuse: the variation, customization, and usage interfaces. Higher-level concerns reuse lower-level concerns, resulting in concern hierarchies where lower-level concern models are composed with higher-level concern models. As part of the variation interface, goal models are used to describe the impact of features of a concern on system qualities. Consequently, goal models of lower-level concerns must be combined with goal models of higher-level concerns to enable reasoning about system qualities in concern hierarchies. However, existing propagation-based reasoning mechanisms for goal models still assume a monolithic goal model, which is not appropriate for concern-oriented reuse. To address this issue, this paper presents novel modeling constructs to enable the reuse of lower-level goal models in the context of Concern-Orientation, extends existing propagation-based reasoning mechanisms of goal models for use in concern hierarchies, and reports on a proof-of-concept implementation of the novel modeling constructs and the extended reasoning mechanism.

Evaluation of reusable concern-oriented goal models

Context: Goal modeling is an important instrument for the elicitation, specification, analysis, and validation of early requirements. Goal models capture hierarchical representations of stakeholder objectives, requirements, possible solutions, and their relationships to help requirements engineers understand stakeholder goals and explore solutions based on their impact on these goals. To reuse a goal model and benefit from the strengths of goal modeling, we argue that it is necessary (i) to make sure that analysis and validation of goal models is possible through reuse hierarchies, (ii) to provide the means to delay decision making to a later point in the reuse hierarchy, (iii) to take constraints imposed by other modeling notations into account during analysis, (iv) to allow context dependent information to be modeled so that the goal model can be used in various reuse contexts, and (v) to provide an interface for reuse. Objective: In this two-part systematic literature review, we (i) evaluate how well existing goal modeling approaches support reusability with our five desired characteristics of contextual and reusable goal models, (ii) categorize these approaches based on language constructs for context modeling and connection to other modeling formalisms, and then (iii) draw our conclusions on future research themes. Method: Following guidelines by Kitchenham, the review is conducted on seven major academic search engines. Research questions, inclusion criteria, and categorization criteria are specified, and threats to validity are discussed. A final list of 146 publications and 34 comparisons/assessments of goal modeling approaches is discussed in more detail. Results: Five major research themes are derived to realize reusable goal models with context dependent information. Conclusion: The results indicate that existing goal modeling approaches do not fully address the required capabilities for reusability in different contexts and that further research is needed to fill this gap in the landscape of goal modeling approaches.

Reusability in goal modeling: A systematic literature review

Trade-off analysis through goal model evaluation has been a valuable tool for requirements elicitation and analysis. This is also true in the context of reuse. When goal models are used to describe reusable artifacts and to represent the impacts of reusable artifacts on high-level goals and qualities, they can guide the selection of reusable artifacts to build reuse hierarchies. In previous work, we introduced the use of relative contribution values for reusable goal models, while considering constraints imposed by other modeling notations. In this paper, we expand the result of goal model evaluation from the typical single satisfaction value to a range of values that are still possible based on the current task selections. In the context of reuse hierarchies, we call the remaining task selections delayed decisions because they are postponed to a higher level in the reuse hierarchy when more is known about the system under development. The extended algorithm takes into account the delayed decisions and evaluates the best and worst possible results that can be obtained with the task selections that have been made in the entire reuse hierarchy. The distinct levels in the reuse hierarchy are leveraged to manage the computational complexity of this reuse hierarchy-wide evaluation. A proof-of-concept implementation of the novel evaluation algorithm is presented in the concern-oriented software design modeling tool TouchCORE.

Mustafa Berk Duran

Papers

On the Reuse of Goal Models

Investigation of feature run-time conflicts on goal model-based reuse

Evaluation of reusable concern-oriented goal models

Reusability in goal modeling: A systematic literature review

Evaluation of Goal Models in Reuse Hierarchies with Delayed Decisions