Consolidated Product Line Variability Modeling

Bayer, Joachim; Gérard, Sébastien; Haugen, Øystein; Mansell, Jason Xabier; Møller-Pedersen, Birger; Oldevik, Jon; Tessier, Patrick; Thibault, Jean-Philippe; Widen, Tanya

doi:10.1007/978-3-540-33253-4_6

Cited by 34 publications

(24 citation statements)

References 9 publications

(11 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In the area of software product lines, the modeling languages need to enable the modeling of commonalities and variabilities. For this purpose, Bayer et al [4] present a consolidated variability meta-model with a unified terminology and representation that enables variability specification during domain engineering and variability resolution during application engineering. The model helps stakeholders to collaborate throughout the life cycles of software product lines and vendors to develop interoperable commercial and open-source modeling tools.…”

Section: Human To Human Communicationmentioning

confidence: 99%

“…It should thus be possible to manage models up to the element level that corresponds with the component in software. involves the modeling of a common view of product line architecture (see [4] and Section 2.1). When a team is working on a common view of the architecture through a model and a team member checks out the model, others cannot continue the work until the same person has completed the check-in.…”

Section: Evaluation Characteristicsmentioning

confidence: 99%

“…The first, traditional approach has been to integrate variability modeling in the systems modeling language such as Unified Modeling Language™ (UML) [12;27] by appropriately extending the metamodel of the language [4]. The second approach, orthogonal variability modeling, distinguishes between a variability model and a system model [30].…”

Section: Introductionmentioning

confidence: 99%

“…UML has become the most widely accepted software system modeling language [4]. It can also be used to model embedded, business, and real-time systems.…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Framework for Evaluating the Version Management Capabilities of a Class of UML Modeling Tools from the Viewpoint of Multi-Site, Multi-Partner Product Line Organizations

Koivulahti-Ojala

Käkölä

2010

2010 43rd Hawaii International Conference on System Sciences

View full text Add to dashboard Cite

UML models are widely used in software product line engineering for activities such as modeling the software product line reference architecture, detailed design, and automation of software code generation and testing. But in high-tech companies, modeling activities are typically distributed across multiple sites and involve multiple partners in different countries, thus complicating model management. Today's UML modeling tools support sophisticated version management for managing parallel and distributed modeling. However, the literature does not provide a comprehensive set of industrial-level criteria to evaluate the version management capabilities of UML tools. This article's contribution is a framework for evaluating the version management features of UML modeling tools for multi-site, multi-partner software product line organizations.

show abstract

Section: Human To Human Communicationmentioning

confidence: 99%

Section: Evaluation Characteristicsmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

“…UML has become the most widely accepted software system modeling language [4]. It can also be used to model embedded, business, and real-time systems.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Framework for Evaluating the Version Management Capabilities of a Class of UML Modeling Tools from the Viewpoint of Multi-Site, Multi-Partner Product Line Organizations

Koivulahti-Ojala

Käkölä

2010

2010 43rd Hawaii International Conference on System Sciences

View full text Add to dashboard Cite

show abstract

“…The BVR approach described in [143] was developed within the Families project [144]. The main focus in that work was variability models for base models in general purpose modelling languages like UML, so some of the variability mechanisms in the language for making variability models relied on the existence of certain base model language mechanisms.…”

Section: Approachesmentioning

confidence: 99%

Achieving Autonomic Computing through the Use of Variability Models at Run-time

Cetina¹

View full text Add to dashboard Cite

Increasingly, software needs to dynamically adapt its behavior at run-time in response to changing conditions in the supporting computing infrastructure and in the surrounding physical environment. Adaptability is emerging as a necessary underlying capability, particularly for highly dynamic systems such as context-aware or ubiquitous systems. These systems have reached a level of complexity where the human effort required to get the systems up and running and keeping them operational is getting out of hand. By automating tasks such as installation, adaptation, or healing, AutonomicComputing envisions computing environments that evolve without the need for human intervention. Even though there is a fair amount of work on architectures and their theoretical design, Autonomic Computing was criticised as being a "hype topic" because very little of it has been fully implemented. Furthermore, given that the autonomic system must change states at runtime and that some of those states may emerge and are much less deterministic, there is a great challenge to provide new guidelines, techniques and tools to help autonomic system development.This thesis shows that building up on the central ideas of Model Driven Development (Models as first-order citizens) and Software Product Lines (Variability Management) can play a significant role as we move towards implementing the key self-management properties associated with autonomic computing. The presented approach encompass systems that are capable of modifying their own behavior with respect to changes in their operating environment, by using variability models as if they were the policies that drive the system's autonomic reconfiguration at runtime.Under a set of reconfiguration commands, the components that make up the architecture dynamically cooperate to change the configuration of the architecture to a new configuration. v vi This work also provides the implementation of a Model-Based Reconfiguration Engine (MoRE) to blend the above ideas. Given a context event, MoRE queries the variability models to determine how the system should evolve, and then it provides the mechanisms for modifying the system architecture accordingly. The presented work has been validated from three different perspectives: (1) Scalability of the approach, (2) reliability-based risk of run-time reconfigurations and (3) degree of autonomic behavior achieved. This evaluation was performed with the participation of human subjects by means of a Smart Hotel case study which was deployed with real devices.Experimentation shows that our approach achieves satisfactory results with regard to scalability and reliability-based risk; nevertheless, we found some scenarios which required a greater level of detail to define the autonomic behaviour since these scenarios deal more directly with user preferences and tastes. However, even though this lack of coverage could be complemented by the development of specific components for the unsupported cases, it does not seem economically realistic to build indiv...

show abstract