Variability management

Setyautami, Maya Retno Ayu; Fadhlillah, Hafiyyan Sayyid; Adianto, Daya; Affan, Ichlasul; Azurat, Ade

doi:10.1145/3382025.3414981

Cited by 4 publications

(1 citation statement)

References 17 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…May et al[26] conducted an exploration of features in the code-assets of micro-service-based implementation of a webshop. They even took a step further and re-engineered the code-assets and produced product line architecture; introduced variations using the principles of deltaoriented software product line[27].…”

mentioning

confidence: 99%

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

Umar¹,

Lee²

2021

IJSEA

View full text Add to dashboard Cite

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.

show abstract

mentioning

confidence: 99%