scholarly journals On the use of model transformation for the automation of product derivation process in SPL

2018 ◽  
Vol 10 (1) ◽  
pp. 43-57
Author(s):  
Nesrine Lahiani ◽  
Djamal Bennouar
Keyword(s):  
Model Transformation ◽  
Software Product Line ◽  
Domain Engineering ◽  
Product Line ◽  
Model Transformations ◽  
Transformation Language ◽  
Software Product ◽  
Application Engineering ◽  
Model Transformation Language ◽  
Derivation Process

Abstract Product Derivation represents one of the main challenges that Software Product Line (SPL) faces. Deriving individual products from shared software assets is a time-consuming and an expensive activity. In this paper, we (1) present an MDE approach for engineering SPL and (2) propose to leverage model-to-model transformations (MMT) and model-to-text (MTT) transformations for supporting both domain engineering and application engineering processes. In this work, we use ATL as a model-to-model transformation language and Acceleo as a model-to-text transformation language.The proposed approach is discussed with e-Health product line applications.

scholarly journals Properties of a Feature in Code-Assets: An Exploratory Study

2021 ◽  
Vol 12 (5) ◽  
pp. 41-53
Author(s):  
Armaya’u Zango Umar ◽  
Jaejoon Lee
Keyword(s):  
Software Product Line ◽  
Domain Engineering ◽  
Product Line ◽  
Product Line Engineering ◽  
Software Products ◽  
Software Product Line Engineering ◽  
Software Product ◽  
Application Engineering ◽  
Usage Context ◽  
Line Engineering

Software product line engineering is a paradigm for developing a family of software products from a repository of reusable assets rather than developing each individual product from scratch. In featureoriented software product line engineering, the common and the variable characteristics of the products are expressed in terms of features. Using software product line engineering approach, software products are produced en masse by means of two engineering phases: (i) Domain Engineering and, (ii) Application Engineering. At the domain engineering phase, reusable assets are developed with variation points where variant features may be bound for each of the diverse products. At the application engineering phase, individual and customized products are developed from the reusable assets. Ideally, the reusable assets should be adaptable with less effort to support additional variations (features) that were not planned beforehand in order to increase the usage context of SPL as a result of expanding markets or when a new usage context of software product line emerges. This paper presents an exploration research to investigate the properties of features, in the code-asset implemented using Object-Oriented Programming Style. In the exploration, we observed that program elements of disparate features formed unions as well as intersections that may affect modifiability of the code-assets. The implication of this research to practice is that an unstable product line and with the tendency of emerging variations should aim for techniques that limit the number of intersections between program elements of different features. Similarly, the implication of the observation to research is that there should be subsequent investigations using multiple case studies in different software domains and programming styles to improve the understanding of the findings.

scholarly journals Validation of RP-SPF Framework: A Systematic Method for Requirements Reuse in Software Product Lines

2019 ◽  
Vol 9 (1) ◽  
pp. 3423-3426
Keyword(s):  
Software Development ◽  
Requirements Engineering ◽  
Domain Engineering ◽  
Product Line ◽  
Product Lines ◽  
Systematic Method ◽  
Product Families ◽  
Software Product ◽  
Application Engineering ◽  
Line Engineering

Reuse of requirements is crucial activity in software development especially across software product line engineering (SPLE), which involves two main processes known as domain engineering and application engineering. With these two processes SPLE enables systematic reuse of requirements through proper planning and development. This paper presents methodology and result of survey of experts for validating a proposed systematic requirement reuse approach named requirements pattern for software product families (RP-SPF) framework. During the survey, 14 experts in requirements engineering (RE), SPLE and software development responded and gave their opinions on RP-SPF framework. The result of the survey shows that RP-SPF approach is suitable and can effectively improve requirements engineering activities of SPLE.

Evolution in Model-Driven Software Product-Line Architectures

2009 ◽  
pp. 1280-1312 ◽  
Author(s):  
Gan Deng ◽  
Jeff Gray ◽  
Douglas C. Schmidt ◽  
Yuehua Lin ◽  
Aniruddha Gokhale ◽  
...  
Keyword(s):  
Model Transformation ◽  
Software Product Line ◽  
Product Line ◽  
Domain Model ◽  
Modeling Language ◽  
Model Driven ◽  
Transformation Rules ◽  
Domain Evolution ◽  
Software Product

This chapter describes our approach to modeldriven engineering (MDE)-based product line architectures (PLAs) and presents a solution to address the domain evolution problem. We use a case study of a representative software-intensive system from the distributed real-time embedded (DRE) systems domain to describe key challenges when facing domain evolution and how we can evolve PLAs systematically and minimize human intervention. The approach uses a mature metamodeling tool to define a modeling language in the representative DRE domain, and applies a model transformation tool to specify model-tomodel transformation rules that precisely define metamodel and domain model changes. Our approach automates many tedious, time consuming, and error-prone tasks of model-to-model transformation, thus significantly reducing the complexity of PLA evolution.

scholarly journals Implementing QVT-R via semantic interpretation in UML-RSDS

2020 ◽  
Author(s):  
K. Lano ◽  
S. Kolahdouz-Rahimi
Keyword(s):  
Model Transformation ◽  
Semantic Interpretation ◽  
Model Transformations ◽  
Tool Support ◽  
Transformation Language ◽  
Efficient Code ◽  
Model Transformation Language ◽  
Multiple Languages ◽  
Mathematical Semantics ◽  
Qvt Relations

Abstract The QVT-Relations (QVT-R) model transformation language is an OMG standard notation for model transformation specification. It is highly declarative and supports (in principle) bidirectional (bx) transformation specification. However, there are many unclear or unsatisfactory aspects to its semantics, which is not precisely defined in the standard. UML-RSDS is an executable subset of UML and OCL. It has a precise mathematical semantics and criteria for ensuring correctness of applications (including model transformations) by construction. There is extensive tool support for verification and for production of 3GL code in multiple languages (Java, C#, C++, C, Swift and Python). In this paper, we define a translation from QVT-R into UML-RSDS, which provides a logically oriented semantics for QVT-R, aligned with the RelToCore mapping semantics in the QVT standard. The translation includes variation points to enable specialised semantics to be selected in particular transformation cases. The translation provides a basis for verification and static analysis of QVT-R specifications and also enables the production of efficient code implementations of QVT-R specifications. We evaluate the approach by applying it to solve benchmark examples of bx.

scholarly journals Evaluation of Test Case Generation based on a Software Product Line for Model Transformation

2018 ◽  
Vol 14 (1) ◽  
pp. 108-121
Author(s):  
Alexandre Augusto Giron ◽  
Itana Maria de Souza Gimenes ◽  
Edson OliveiraJr
Keyword(s):  
Model Transformation ◽  
Software Product Line ◽  
Product Line ◽  
Test Case Generation ◽  
Test Case ◽  
Software Product

Adding More Agility to Software Product Line Methods

2018 ◽  
pp. 1294-1311
Author(s):  
Kun Tian
Keyword(s):  
Cost Effective ◽  
Software Product Line ◽  
Product Line ◽  
Time To Market ◽  
Engineering Software ◽  
Software Product ◽  
Agile Practices ◽  
Application Engineering ◽  
Market Needs ◽  
Development Methods

Software Product Line Methods (SPLMs) have been continuously gaining attention, especially in practice, for on one hand, they address diverse market needs while controlling costs by planned systematic reuse in core assets development (domain engineering), and on another hand, they reduce products' time-to-market, achieving a certain level of agility in product development (application engineering). More cost-effective and agile as they are than traditional development methods for producing families of similar products, SPLMs still seem to be heavy weight in nature. In SPLMs, significant up-front commitments are involved in development of a flexible product platform, which will be modified into a range of products sharing common features. Agile Methods (AMs) share similar goals with SPLMs, e.g., on rapidly delivering high quality software that meets the changing needs of stakeholders. However, they appear to differ significantly practices. The purpose of this work is to compare Agile and Software Product line approaches from fundamental goals/principles, engineering, software quality assurance, sand project management perspectives, etc. The results of the study can be used to determine the feasibility of tailoring a software product line approach with Agile practices, resulting in a lighter-weight approach that provides mass customization, reduced time-to-market, and improved customer satisfaction.

Sign in / Sign up

Export Citation Format

Share Document