Codifying architecture knowledge to support online evolution of software product lines

2011 Ninth Working IEEE/IFIP Conference on Software Architecture

Helleboogh

et al. 2011

Self Cite

Despite the successes of software product lines (SPL), managing the evolution of a SPL remains difficult and error-prone. Our focus of evolution is on the concrete tasks integrators have to perform to update deployed SPL products, in particular products that require runtime updates with minimal interruption. The complexity of updating a deployed SPL product is caused by multiple interdependent concerns, including variability, traceability, versioning, availability, and correctness. Existing approaches typically focus on particular concerns while making abstraction of others, thus offering only partial solutions. An integrated approach that takes into account the different stakeholder concerns is lacking. In this paper, we present an architectural approach for updating SPL products that supports multiple concerns. The approach comprises of two complementary parts: (1) an update viewpoint that defines the conventions for constructing and using architecture views to deal with multiple update concerns; and (2) a supporting framework that provides an extensible infrastructure supporting integrators of a SPL. We evaluated the approach for an industrial SPL for logistic systems providing empirical evidence for its benefits and recommendations.

Section: Overviewmentioning

confidence: 99%

An Architectural Approach to Support Online Updates of Software Product Lines

2011 Ninth Working IEEE/IFIP Conference on Software Architecture

Helleboogh

et al. 2011

Self Cite

“…The analyzer uses the collected data to provide models M3 and M4 of a product. Model M3 results from the comparison of the as-is and to-be models [19]. Model M4 is obtained by verifying whether there are any unresolved dependencies between system resources.…”

Section: Architecture-centric Approachmentioning

confidence: 99%

Supporting Online Updates of Software Product Lines: A Controlled Experiment

2011 International Symposium on Empirical Software Engineering and Measurement

Boucké

et al. 2011

Self Cite

Abstract-The evolution of Software Product Lines (SPL) is challenging because stakeholders have to deal with both regular evolution and the co-existence of different products. Our focus of product evolution is on the tasks integrators have to perform to update deployed SPL products with minimal interruption of services. In case of Egemin, our industrial partner, the updates of SPL products is further hampered as a consequence of outdated and imprecise architectural knowledge of deployed products. To facilitate the updates of products, we have developed the architecture-centric approach which comprises two complementary parts: an update viewpoint and a supporting tool.In this paper we present an evaluation of the architecturecentric approach. The approach is compared with the Egemin's current update approach in a controlled experiment. In the experiment 17 professionals were asked to perform 68 updates of logistic systems. The results obtained from the experiment show that the architecture-centric approach significantly improves the correctness of updates and reduces the interruption of services during updates of Egemin's SPL products.

“…The collected knowledge is analysed and visualized. Model M3 is obtained by comparison of the models M1 and M2 [12]. Second type of analysis identifies inconsis- Figure 3 shows a snapshot of the EvoLine tool.…”

Section: Product-specific Evolutionmentioning

confidence: 99%

On the problems with evolving Egemin's software product line

Proceedings of the 2nd International Workshop on Product Line Approaches in Software Engineering

Betsbrugge³

2011

Self Cite

Egemin, an industrial manufacturer of logistic systems is adopting a Software Product Line (SPL) approach to manage the development of their product portfolio. However, due to the intrinsic complexity of the logistic systems and lack of explicitly documented architectural knowledge evolution of the products is error-prone. Faulty updates increase maintenance costs and harm the company's reputation. Therefore, Egemin searches for a systematic solution that can improve their SPL evolution strategy.