Conference Paper
Plastic Partial Components: A solution to support variability in architectural components.
E.U.Inf., Univ. Politec. de Madrid, Madrid, Spain
DOI: 10.1109/WICSA.2009.5290808 Conference: Joint Working IEEE/IFIP Conference on Software Architecture 2009 and European Conference on Software Architecture 2009, WICSA/ECSA 2009, Cambridge, UK, 1417 September 2009 Source: DBLP

Conference Paper: Deltaoriented architectural variability using MontiCore.
[Show abstract] [Hide abstract]
ABSTRACT: Modeling of software architectures is a fundamental part of software development processes. Reuse of software components and early analysis of software topologies allow the reduction of development costs and increases software quality. Integrating variability modeling concepts into architecture description languages (ADLs) is essential for the development of diverse software systems with high demands on software quality. In this paper, we present the integration of delta modeling into the existing ADL MontiArc. Delta modeling is a languageindependent variability modeling approach supporting proactive, reactive and extractive product line development. We show how ΔMontiArc, a language for explicit modeling of architectural variability based on delta modeling, is implemented as domainspecific language (DSL) using the DSL development framework MontiCore. We also demonstrate how MontiCore's language reuse mechanisms provide efficient means to derive an implementation of ΔMontiArc tool implementation. We evaluate ΔMontiArc by comparing it with annotative variability modeling.Software Architecture, 5th European Conference, ECSA 2011, Essen, Germany, September 13  16, 2011. Companion Volume; 01/2011 
Conference Paper: Firstclass variability modeling in Matlab/Simulink
[Show abstract] [Hide abstract]
ABSTRACT: Modern cars exist in an vast number of variants. Thus, variability has to be dealt with in all phases of the development process, in particular during modelbased development of softwareintensive functionality using Matlab/Simulink. Currently, variability is often encoded within a functional model leading to so called 150%models which easily become very complex and do not scale for larger product lines. To counter these problems, we propose a modular variability modeling approach for Matlab/Simulink based on the concept of delta modeling. A functional variant is described by a delta encapsulating a set of modifications. A sequence of deltas can be applied to a core product to derive the desired variant. We present a prototypical implementation, which is integrated into Matlab/Simulink and offers graphical editing of delta models.Proceedings of the Seventh International Workshop on Variability Modelling of Softwareintensive Systems; 01/2013 
Conference Paper: Evolving Deltaoriented Software Product Line Architectures
[Show abstract] [Hide abstract]
ABSTRACT: Diversity is prevalent in modern software systems. Several system variants exist at the same time in order to adapt to changing user requirements. Additionally, software systems evolve over time in order to adjust to unanticipated changes in their application environment. In modern software development, software architecture modeling is an important means to deal with system complexity by architectural decomposition. This leads to the need of architectural description languages that can represent spatial and temporal variability. In this paper, we present delta modeling of software architectures as a uniform modeling formalism for architectural variability in space and in time. In order to avoid degeneration of the product line model under system evolution, we present refactoring techniques to maintain and improve the quality of the variability model. Using a running example from the automotive domain, we evaluate our approach by carrying out a case study that compares delta modeling with annotative variability modeling.LargeScale Complex IT Systems. Development, Operation and Management, 17th Monterey Workshop 2012, Oxford, UK, March 1921, 2012; 01/2012
Data provided are for informational purposes only. Although carefully collected, accuracy cannot be guaranteed. The impact factor represents a rough estimation of the journal's impact factor and does not reflect the actual current impact factor. Publisher conditions are provided by RoMEO. Differing provisions from the publisher's actual policy or licence agreement may be applicable.