Extracting core requirements for software product lines

被引:0
|
作者
Iris Reinhartz-Berger
Mark Kemelman
机构
[1] University of Haifa,Department of Information Systems
来源
Requirements Engineering | 2020年 / 25卷
关键词
Software Product Line Engineering; Systematic reuse; Requirements specification; Variability analysis;
D O I
暂无
中图分类号
学科分类号
摘要
Software Product Line Engineering (SPLE) is a promising paradigm for reusing knowledge and artifacts among similar software products. However, SPLE methods and techniques require a high up-front investment and hence are profitable if several similar software products are developed. Thus in practice adoption of SPLE commonly takes a bottom-up approach, in which analyzing the commonality and variability of existing products and transforming them into reusable ones (termed core assets) are needed. These time-consuming and error-prone tasks call for automation. The literature partially deals with solutions for early software development stages, mainly in the form of variability analysis. We aim for further creation of core requirements—reusable requirements that can be adapted for different software products. To this end, we introduce an automated extractive method, named CoreReq, to generate core requirements from product requirements written in a natural language. The approach clusters similar requirements, captures variable parts utilizing natural language processing techniques, and generates core requirements following an ontological variability framework. Focusing on cloning scenarios, we evaluated CoreReq through examples and a controlled experiment. Based on the results, we claim that core requirements generation with CoreReq is feasible and usable for specifying requirements of new similar products in cloning scenarios.
引用
收藏
页码:47 / 65
页数:18
相关论文
共 50 条
  • [1] Extracting core requirements for software product lines
    Reinhartz-Berger, Iris
    Kemelman, Mark
    [J]. REQUIREMENTS ENGINEERING, 2020, 25 (01) : 47 - 65
  • [2] Security requirements in software product lines
    Mellado, Daniel
    Fernandez-Medina, Eduardo
    Piattini, Mario
    [J]. SECRYPT 2008: PROCEEDINGS OF THE INTERNATIONAL CONFERENCE ON SECURITY AND CRYPTOGRAPHY, 2008, : 442 - +
  • [3] A Framework for Managing Requirements of Software Product Lines
    Arias, Maximiliano
    Buccella, Agustina
    Cechich, Alejandra
    [J]. ELECTRONIC NOTES IN THEORETICAL COMPUTER SCIENCE, 2018, 339 : 5 - 20
  • [4] Security requirements variability for software product lines
    Mellado, Daniel
    Fernandez-Medina, Eduardo
    Piattini, Mario
    [J]. ARES 2008: PROCEEDINGS OF THE THIRD INTERNATIONAL CONFERENCE ON AVAILABILITY, SECURITY AND RELIABILITY, 2008, : 1413 - +
  • [5] From Requirements to Architecture for Software Product Lines
    Coelho, Keivilany
    Batista, Thais
    [J]. 2011 9TH WORKING IEEE/IFIP CONFERENCE ON SOFTWARE ARCHITECTURE (WICSA), 2011, : 282 - 289
  • [6] A Semi-Automatic Approach for Extracting Software Product Lines
    Valente, Marco Tulio
    Borges, Virgilio
    Passos, Leonardo
    [J]. IEEE TRANSACTIONS ON SOFTWARE ENGINEERING, 2012, 38 (04) : 737 - 754
  • [7] Security requirements engineering framework for software product lines
    Mellado, Daniel
    Fernandez-Medina, Eduardo
    Piattini, Mario
    [J]. INFORMATION AND SOFTWARE TECHNOLOGY, 2010, 52 (10) : 1094 - 1117
  • [8] An Experimental Study on Requirements Engineering for Software Product Lines
    Santana Neiva, Danuza Ferreira
    de Almeida, Eduardo Santana
    de Lemos Meira, Silvio Romero
    [J]. 2009 35TH EUROMICRO CONFERENCE ON SOFTWARE ENGINEERING AND ADVANCED APPLICATIONS, PROCEEDINGS, 2009, : 251 - +
  • [9] Requirements Evolution in Software Product Lines: An Empirical Study
    de Oliveira, Raphael Pereira
    de Almeida, Eduardo Santana
    [J]. PROCEEDINGS 2015 NINTH BRAZILIAN SYMPOSIUM ON SOFTWARE COMPONENTS, ARCHITECTURES AND REUSE - SBCARS 2015, 2015, : 1 - 10
  • [10] Capturing consumer preferences as requirements for software product lines
    Zdravkovic, Jelena
    Svee, Eric-Oluf
    Giannoulis, Constantinos
    [J]. REQUIREMENTS ENGINEERING, 2015, 20 (01) : 71 - 90