ISSUES AND MODELS IN SOFTWARE PRODUCT LINES

2000 ◽  
Vol 10 (04) ◽  
pp. 527-539 ◽  
Author(s):  
JORGE L. DIAZ-HERRERA ◽  
PETER KNAUBER ◽  
GIANCARLO SUCCI
Keyword(s):  
Software Engineering ◽  
Development Process ◽  
Software Product Lines ◽  
Product Lines ◽  
Standard Format ◽  
Software Products ◽  
Systematic Process ◽  
Software Product ◽  
Business Analysis ◽  
Definition Of

Software product lines are one of the most promising fields in software engineering. They aim at the synergistic construction of software products. A successful introduction of software product lines requires three essential ingredients: a business analysis of the overall advantages that can come from product lines, the definition of a systematic process for product lines development, and the definition of general models, in a standard format, which can guide the development process.

scholarly journals CyberSPL: A Framework for the Verification of Cybersecurity Policy Compliance of System Configurations Using Software Product Lines

2019 ◽  
Vol 9 (24) ◽  
pp. 5364 ◽  
Author(s):  
Ángel Jesús Varela-Vaca  ◽  
Rafael M. Gasca ◽  
Rafael Ceballos ◽  
María Teresa Gómez-López ◽  
Pedro Bernáldez Torres
Keyword(s):  
Automated Analysis ◽  
Software Product Lines ◽  
Product Line ◽  
Feature Models ◽  
Product Lines ◽  
Software Products ◽  
Wide Range ◽  
Proposal A ◽  
Software Product ◽  
Real Scenario

Cybersecurity attacks affect the compliance of cybersecurity policies of the organisations. Such disadvantages may be due to the absence of security configurations or the use of default configuration values of software products and systems. The complexity in the configuration of products and systems is a known challenge in the software industry since it includes a wide range of parameters to be taken into account. In other contexts, the configuration problems are solved using Software Product Lines. This is the reason why in this article the framework Cybersecurity Software Product Line (CyberSPL) is proposed. CyberSPL is based on a methodology to design product lines to verify cybersecurity policies according to the possible configurations. The patterns to configure the systems related to the cybersecurity aspects are grouped by defining various feature models. The automated analysis of these models allows us to diagnose possible problems in the security configurations, reducing or avoiding them. As support for this proposal, a multi-user and multi-platform solution has been implemented, enabling setting a catalogue of public or private feature models. Moreover, analysis and reasoning mechanisms have been integrated to obtain all the configurations of a model, to detect if a configuration is valid or not, including the root cause of problems for a given configuration. For validating the proposal, a real scenario is proposed where a catalogue of four different feature models is presented. In this scenario, the models have been analysed, different configurations have been validated, and several configurations with problems have been diagnosed.

scholarly journals Software Product Lines in Value Based Software Engineering

2006 ◽  
Author(s):  
María Teresa Baldassarre ◽  
Danilo Caivano ◽  
Giuseppe Visaggio
Keyword(s):  
Software Engineering ◽  
Software Product Lines ◽  
Product Lines ◽  
Software Product

scholarly journals Statically Analyzing the Energy Efficiency of Software Product Lines

2021 ◽  
Vol 11 (1) ◽  
pp. 13
Author(s):  
Marco Couto ◽  
João Paulo Fernandes ◽  
João Saraiva
Keyword(s):  
Energy Consumption ◽  
Simulated Annealing Algorithm ◽  
Traditional Approach ◽  
Software Product Lines ◽  
Product Lines ◽  
Worst Case ◽  
Software Products ◽  
Important Concern ◽  
Software Product ◽  
Development Approach

Optimizing software to become (more) energy efficient is an important concern for the software industry. Although several techniques have been proposed to measure energy consumption within software engineering, little work has specifically addressed Software Product Lines (SPLs). SPLs are a widely used software development approach, where the core concept is to study the systematic development of products that can be deployed in a variable way, e.g., to include different features for different clients. The traditional approach for measuring energy consumption in SPLs is to generate and individually measure all products, which, given their large number, is impractical. We present a technique, implemented in a tool, to statically estimate the worst-case energy consumption for SPLs. The goal is to reason about energy consumption in all products of a SPL, without having to individually analyze each product. Our technique combines static analysis and worst-case prediction with energy consumption analysis, in order to analyze products in a feature-sensitive manner: a feature that is used in several products is analyzed only once, while the energy consumption is estimated once per product. This paper describes not only our previous work on worst-case prediction, for comprehensibility, but also a significant extension of such work. This extension has been realized in two different axis: firstly, we incorporated in our methodology a simulated annealing algorithm to improve our worst-case energy consumption estimation. Secondly, we evaluated our new approach in four real-world SPLs, containing a total of 99 software products. Our new results show that our technique is able to estimate the worst-case energy consumption with a mean error percentage of 17.3% and standard deviation of 11.2%.

Software Engineering for Technological Ecosystems

2017 ◽  
pp. 175-194
Author(s):  
Rajeshwar Vayyavur
Keyword(s):  
Software Engineering ◽  
Business Schools ◽  
Software Product Lines ◽  
Product Lines ◽  
Software Ecosystems ◽  
Software Product ◽  
Technological Ecosystems

Software engineering for technological ecosystems also referred as Software Ecosystems (SECOs) focuses on the concept of software engineering field. The study of SECOs started in early 90s under business schools, mainly focused on software engineering based on the software product lines approach that aimed to allow external designers and developers to contribute to hitherto closed platforms. The chapter gives background, various dimensions, framework, architectural challenges of SECOs, and explains various limitations and different recommendations and solutions to provide a better and conclusive platform for the technology ecosystems.

scholarly journals SPLMT-TE: A Software Product Lines System Test Case Tool

2012 ◽  
Author(s):  
Crescencio Rodrigues Lima Neto ◽  
Eduardo S. Almeida ◽  
Silvio R. L. Meira
Keyword(s):  
Software Testing ◽  
Software Product Lines ◽  
Test Case ◽  
Product Lines ◽  
Case Tool ◽  
Software Products ◽  
Test Execution ◽  
Testing Tools ◽  
Software Product ◽  
Testing Tool

The product lines approach requires specific testing tools that should help to manage reusable testing assets and automate the test execution. Despite of the increasing interest by the research community regarding software testing tools, Software Products Lines (SPL) still need tools to support the testing process. This work presents briefly the results of a mapping study on software testing tool and defines the requirements, design and implementation of a software product lines system test case tool, aiming at the creation and management of test assets. A controlled experiment was also conducted to evaluate the tool effectiveness.

scholarly journals Uma Linguagem de Modelagem de Domínio Específico para Linhas de Produto de Software Dinâmicas

2020 ◽  
Author(s):  
Helberth Borelli ◽  
Sérgio Teixeira de Carvalho
Keyword(s):  
Adaptive Systems ◽  
Development Time ◽  
Software Product Lines ◽  
Feature Models ◽  
Service Model ◽  
Product Lines ◽  
Software Products ◽  
Domain Specific ◽  
Software Product ◽  
Dynamic Software

Software Product Lines can be briefly defined as a family of productsthat share some commonalities. The feature models approach isused to represent the commonalities and variabilities among products.One possible way for the construction of these models is theuse of meta-models. However, the management of these features,traditionally performed at development time, is not sufficient forthe development of Adaptive Systems. One solution to this type ofdevelopment is the approach of Dynamic Software Product Lineswhich has as one of its aims to promote features input and outputat runtime allowing the product to be adapted after changes incontexts. This article proposes a Domain Specific Modelling Languagethat aims at modeling Dynamic Software Product Lines. Thislanguage describes dynamic adaptations promoted at runtime andthrough the use of the state machine approach. Such adaptations,based on state machines, must promote state features changes orfeatures exchanges at runtime, enabling these software products tomanage derivations in its life cycle. Our proposal was implementedwith the use of a Healthcare scenario and its development wasbased on the concept of the component service model.

Software Engineering for Technological Ecosystems

2021 ◽  
pp. 598-611
Author(s):  
Rajeshwar Vayyavur
Keyword(s):  
Software Engineering ◽  
Business Schools ◽  
Software Product Lines ◽  
Product Lines ◽  
Software Ecosystems ◽  
Software Product ◽  
Technological Ecosystems

Software engineering for technological ecosystems also referred as Software Ecosystems (SECOs) focuses on the concept of software engineering field. The study of SECOs started in early 90s under business schools, mainly focused on software engineering based on the software product lines approach that aimed to allow external designers and developers to contribute to hitherto closed platforms. The chapter gives background, various dimensions, framework, architectural challenges of SECOs, and explains various limitations and different recommendations and solutions to provide a better and conclusive platform for the technology ecosystems.

Sign in / Sign up

Export Citation Format

Share Document