Software product line scoping and requirements engineering in a small and medium-sized enterprise: An industrial case study

Silva, Ivonei Freitas da; Neto, Paulo Anselmo da Mota Silveira; O’Leary, Pádraig; Almeida, Eduardo Santana de; Meira, Sílvio Romero de Lemos

doi:10.1016/j.jss.2013.10.040

Cited by 16 publications

(11 citation statements)

References 41 publications

(56 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…From the set of 63 works, three of them are surveys/state-of-art studies [19,34,40] and two report experiences on adoption of SPL in small and medium enterprises [10,24]. …”

Section: Discussionmentioning

confidence: 99%

Feature location for software product line migration

Assunção

Vergílio

2014

Proceedings of the 18th International Software Product Line Conference: Companion Volume for Workshops, Demonstrations and Tool

View full text Add to dashboard Cite

Developing software from scratch is a high cost and errorprone activity. A possible solution to reduce time-to-market and produce high quality software is the reuse of existing software. But when the number of features in the system grows, the maintenance becomes more complex. In such cases, to adopt a systematic approach, such as Software Product Line Engineering, is necessary. Existing systems are generally migrated to a product line, allowing systematic reuse of artefacts and easing maintenance. To this end, some approaches have been proposed in the literature in the last years. A mapping of works on this subject and the identification of some research gaps can lead to an improvement of such approaches. This paper describes the main outcomes of a systematic mapping study on the evolution and migration of systems to SPL. The main works found are presented and classified according to adopted strategy, artefacts used, and evaluation conducted. Analysis of the evolution along the past years are also presented. At the end, we summarize some trends and open issues to serve as reference to new researches.

show abstract

“…From the set of 63 works, three of them are surveys/state-of-art studies [19,34,40] and two report experiences on adoption of SPL in small and medium enterprises [10,24]. …”

Section: Discussionmentioning

confidence: 99%

Feature location for software product line migration

Assunção

Vergílio

2014

Proceedings of the 18th International Software Product Line Conference: Companion Volume for Workshops, Demonstrations and Tool

View full text Add to dashboard Cite

show abstract

“…Furthermore, there is a high need to maintain version control, which depends on the feedback that came from the application engineering process. da Silva et al (2014) , Klünder et al (2019) , Kasauli et al (2021) and Camacho et al (2021) emphasized that there is currently no APLE model that completely provides all the details of the integrated process. To address the identified problem, researchers proposed a new, fully comprehensive APLE model with all necessary steps required to produce a new variant iteratively.…”

Section: Related Workmentioning

confidence: 99%

Towards a component-based system model to improve the quality of highly configurable systems

Abbasi

Hafeez

Asghar

et al. 2022

PeerJ Computer Science

View full text Add to dashboard Cite

Due to ever-evolving software developments processes, companies are motivated to develop desired quality products quickly and effectively. Industries are now focusing on the delivery of configurable systems to provide several services to a wide range of customers by making different configurations in a single largest system. Nowadays, component-based systems are highly demanded due to their capability of reusability and restructuring of existing components to develop new systems. Moreover, product line engineering is the major branch of the component-based system for developing a series of systems. Software product line engineering (SPLE) provides the ability to design several software modifications according to customer needs in a cost-effective manner. Researchers are trying to tailor the software product line (SPL) process that integrates agile development technologies to overcome the issues faced during the execution of the SPL process such as delay in product delivery, restriction to requirements change, and exhaustive initial planning. The selection of suitable components, the need for documentation, and tracing back the user requirements in the agile-integrated product line (APL) models still need to improve. Furthermore, configurable systems demand the selected features to be the least dependent. In this paper, a hybrid APL model, quality enhanced application product line engineering (QeAPLE) is proposed that provides support for highly configurable systems (HCS) by evaluating the dependency of features before making the final selection. It also has a documentation and requirement traceability function to ensure that the product meets the desired quality. Two-fold assessments are undertaken to validate the suggested model, with the proposed model being deployed on an active project. After that, we evaluated the proposed model performance and effectiveness using after implementing it in a real-world environment and compared the results with an existing method using statistical analysis. The results of the experimental study proofs that the proposed model is practically and statistically significant as compared to the existing method in terms of effectiveness and participants’ performance. Hence, the statistical results of the comparative analysis show that the proposed model improved ease of understanding and adaptability, required effort, high-quality achievement, and version management are significant i.e., more the 50% as compared to the exiting method i.e., less than 50%. The proposed model offers to assist in the development of a highly configurable system that achieves the needed quality. Therefore, the proposed model manages the variation identification, versions control, components dependency for correct selection of components, and validation activities from domain engineering to application engineering.

show abstract

“…Several other works report experiences of implementation, adoption, and scoping techniques for SPLE in practice (Böckle et al 2002;van der Linden et al 2007;da Silva et al 2014;Fogdal et al 2016;Ahmed et al 2007;Hetrick et al 2006;Krueger et al 2008;Northrop 2002;Jensen 2007;Bastos et al 2017;Buhrdorf et al 2003;Clements et al 2001;Ghanam et al 2012;García et al 2019;Berger et al 2014a). Unfortunately, none of these works reports how to best apply maturity evaluations.…”

Section: Planning Sple Adoptionmentioning

confidence: 99%

Software product-line evaluation in the large

et al. 2021

View full text Add to dashboard Cite

Software product-line engineering is arguably one of the most successful methods for establishing large portfolios of software variants in an application domain. However, despite the benefits, establishing a product line requires substantial upfront investments into a software platform with a proper product-line architecture, into new software-engineering processes (domain engineering and application engineering), into business strategies with commercially successful product-line visions and financial planning, as well as into re-organization of development teams. Moreover, establishing a full-fledged product line is not always possible or desired, and thus organizations often adopt product-line engineering only to an extent that deemed necessary or was possible. However, understanding the current state of adoption, namely, the maturity or performance of product-line engineering in an organization, is challenging, while being crucial to steer investments. To this end, several measurement methods have been proposed in the literature, with the most prominent one being the Family Evaluation Framework (FEF), introduced almost two decades ago. Unfortunately, applying it is not straightforward, and the benefits of using it have not been assessed so far. We present an experience report of applying the FEF to nine medium- to large-scale product lines in the avionics domain. We discuss how we tailored and executed the FEF, together with the relevant adaptations and extensions we needed to perform. Specifically, we elicited the data for the FEF assessment with 27 interviews over a period of 11 months. We discuss experiences and assess the benefits of using the FEF, aiming at helping other organizations assessing their practices for engineering their portfolios of software variants.

show abstract

Software product line scoping and requirements engineering in a small and medium-sized enterprise: An industrial case study

Cited by 16 publications

References 41 publications

Feature location for software product line migration

Feature location for software product line migration

Towards a component-based system model to improve the quality of highly configurable systems

Software product-line evaluation in the large

Contact Info

Product

Resources

About