scholarly journals Integrated Specification of Quality Requirements in Software Product Line Artifacts

2021 ◽  
Author(s):  
Mworia Daniel ◽  
Nderu Lawrence ◽  
Kimwele Michael
Keyword(s):  
Data Storage ◽  
Analytical Description ◽  
Software Product Line ◽  
Product Line ◽  
Functional Requirements ◽  
System Quality ◽  
Quality Requirements ◽  
Software Product ◽  
Definition Of

There are many calls from software engineering scholars to incorporate non-functional requirements as first-class citizens in the software development process. In Software Product Line Engineering emphasis is on explicit definition of functional requirements using feature models while non-functional requirements are considered implicit. In this paper we present an integrated requirements specification template for common quality attributes alongside functional requirements at software product line variation points. This approach implemented at analytical description phase increases the visibility of quality requirements obliging developers to consider them in subsequent phases. The approach achieves weaving of quality requirements into associated functional requirements through higher level feature abstraction method. This work therefore promotes achievement of system quality by elevating nonfunctional requirement specification. The approach is illustrated with an exemplar mobile phone family data storage requirements case study.

scholarly journals Embedding Quality into Software Product Line Variability Artifacts

2021 ◽  
Vol 12 (3) ◽  
pp. 11-25
Author(s):  
Mworia Daniel ◽  
Nderu Lawrence ◽  
Kimwele Michael
Keyword(s):  
Data Storage ◽  
Analytical Description ◽  
Software Product Line ◽  
Poor Quality ◽  
Development Project ◽  
Product Line ◽  
Functional Requirements ◽  
Functional Quality ◽  
Software Product ◽  
Variability Management

The success of any software product line development project is closely tied to its domain variability management. Whereas a lot of effort has been put into functional variability management by the SPL community, non-functional variability is considered implicit. The result has been dissatisfaction among clients due to resultant poor quality systems. This work presents an integrated requirement specification template for quality and functional requirements at software product line variation points. The implementation of this approach at the analytical description phase increases the visibility of quality requirements obliging developers to implement them. The approach proposes the use of decision tree classification techniques to support the weaving of functional quality attributes at respective variation points. This work, therefore, promotes software product line variability management objectives by proposing new functional quality artifacts during requirements specification phase. The approach is illustrated with an exemplar mobile phone family data storage requirements case study.

scholarly journals MULTI ATTRIBUTE ARCHITECTURE DESIGN DECISION FOR CORE ASSET DERIVATION

2015 ◽  
Vol 77 (9) ◽  
Author(s):  
Shahliza A. Halim ◽  
Dayang N. A. Jawawi ◽  
Noraini Ibrahim ◽  
M. Zulkifli M. Zaki ◽  
Safaai Deris
Keyword(s):  
Decision Making ◽  
Software Reuse ◽  
Product Line ◽  
Architecture Design ◽  
Design Decision ◽  
Functional Requirements ◽  
Detail Design ◽  
Software Product ◽  
Study Implementation

Software Product Line (SPL) is an effective approach in software reuse in which core assets can be shared among the members of the product line with an explicit treatment of variability. Core assets, which are developed for reuse in domain engineering, are selected for product specific derivation in application engineering. Decision making support during product derivation is crucial to assist in making multiple decisions during product specific derivation. Multiple decisions are to be resolved at the architectural level as well as the detailed design level, address the need for assisting the decision making process during core asset derivation. Architectural level decision making is based on imprecise, uncertain and subjective nature of stakeholder for making architectural selection based on non- functional requirements (NFR). Furthermore, detail design level involves the selection of suitable features which have the rationale behind each decision. The rationale for the selection, if not documented properly, will also result in loss of tacit knowledge. Therefore, a multi-attribute architecture design decision technique is proposed to overcome the above mentioned problem. The technique combines Fuzzy Analytical Hierarchy Process (FAHP) with lightweight architecture design decision documentation to support the decision making during core asset derivation. We demonstrate our approach using the case study of Autonomous Mobile Robot (AMR). The case study implementation shows showed that the proposed technique supports software engineer in the process of decision making at the architecture and detail design levels.

scholarly journals Feature Model Configuration Based on Two-Layer Modelling in Software Product Lines

2019 ◽  
Vol 9 (4) ◽  
pp. 2648
Author(s):  
Elham Darmanaki Farahani ◽  
Jafar Habibi
Keyword(s):  
Product Line ◽  
Feature Model ◽  
Functional Requirements ◽  
Product Lines ◽  
Software Products ◽  
Model Configuration ◽  
Software Product ◽  
Software And Hardware ◽  
Application Requirements

The aim of the Software Product Line (SPL) approach is to improve the software development process by producing software products that match the stakeholders’ requirements. One of the important topics in SPLs is the feature model (FM) configuration process. The purpose of configuration here is to select and remove specific features from the FM in order to produce the required software product. At the same time, detection of differences between application’s requirements and the available capabilities of the implementation platform is a major concern of application requirements engineering. It is possible that the implementation of the selected features of FM needs certain software and hardware infrastructures such as database, operating system and hardware that cannot be made available by stakeholders. We address the FM configuration problem by proposing a method, which employs a two-layer FM comprising the application and infrastructure layers. We also show this method in the context of a case study in the SPL of a sample E-Shop website. The results demonstrate that this method can support both functional and non-functional requirements and can solve the problems arising from lack of attention to implementation requirements in SPL FM selection phase.

Assessing software product line potential: an exploratory industrial case study

2015 ◽  
Vol 21 (2) ◽  
pp. 411-448 ◽  
Author(s):  
Heiko Koziolek ◽  
Thomas Goldschmidt ◽  
Thijmen de Gooijer ◽  
Dominik Domis ◽  
Stephan Sehestedt ◽  
...  
Keyword(s):  
Software Product Line ◽  
Product Line ◽  
Industrial Case Study ◽  
Software Product

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

2014 ◽  
Vol 88 ◽  
pp. 189-206 ◽  
Author(s):  
Ivonei Freitas da Silva ◽  
Paulo Anselmo da Mota Silveira Neto ◽  
Pádraig O’Leary ◽  
Eduardo Santana de Almeida ◽  
Silvio Romero de Lemos Meira
Keyword(s):  
Requirements Engineering ◽  
Software Product Line ◽  
Product Line ◽  
Industrial Case Study ◽  
Software Product
Sign in / Sign up

Export Citation Format

Share Document