QREME - Quality Requirements Management Model for Supporting Decision-Making

被引:0
作者
Olsson, Thomas [1 ]
Wnuk, Krzysztof [2 ]
机构
[1] RISE SICS AB, Lund, Sweden
[2] BTH, DIPT, Karlskrona, Sweden
来源
REQUIREMENTS ENGINEERING: FOUNDATION FOR SOFTWARE QUALITY (REFSQ 2018) | 2018年 / 10753卷
关键词
Requirements engineering; Quality requirements; Non-functional requirements; Requirements scoping; NONFUNCTIONAL REQUIREMENTS;
D O I
10.1007/978-3-319-77243-1_11
中图分类号
TP31 [计算机软件];
学科分类号
081202 ; 0835 ;
摘要
[Context and motivation] Quality requirements (QRs) are inherently difficult to manage as they are often subjective, context-dependent and hard to fully grasp by various stakeholders. Furthermore, there are many sources that can provide input on important QRs and suitable levels. Responding timely to customer needs and realizing them in product portfolio and product scope decisions remain the main challenge. [Question/problem] Data-driven methodologies based on product usage data analysis gain popularity and enable new (bottom-up, feedback-driven) ways of planning and evaluating QRs in product development. Can these be efficiently combined with established top-down, forward-driven management of QRs? [Principal idea/Results] We propose a model for how to handle decisions about QRs at a strategic and operational level, encompassing product decisions as well as business intelligence and usage data. We inferred the model from an extensive empirical investigation of five years of decision making history at a large B2C company. We illustrate the model by assessing two industrial case studies from different domains. [Contribution] We believe that utilizing the right approach in the right situation will be key for handling QRs, as both different groups of QRs and domains have their special characteristics.
引用
收藏
页码:173 / 188
页数:16
相关论文
共 34 条
[1]   A Survey on Software Release Planning Models [J].
Ameller, David ;
Farre, Carles ;
Franch, Xavier ;
Rufian, Guillem .
PRODUCT-FOCUSED SOFTWARE PROCESS IMPROVEMENT (PROFES 2016), 2016, 10027 :48-65
[2]  
[Anonymous], 2004, Agile project management with Scrum
[3]   The fundamental nature of requirements engineering activities as a decision-making process [J].
Aurum, A ;
Wohlin, C .
INFORMATION AND SOFTWARE TECHNOLOGY, 2003, 45 (14) :945-954
[4]   Speed, Data, and Ecosystems The Future of Software Engineering [J].
Bosch, Jan .
IEEE SOFTWARE, 2016, 33 (01) :82-88
[5]  
Carlshamre P, 2001, FIFTH IEEE INTERNATIONAL SYMPOSIUM ON REQUIREMENTS ENGINEERING, PROCEEDINGS, P84
[6]  
Chung L, 2012, Non-Functional Requirements in Software Engineering, V5, DOI DOI 10.1007/978-1-4615-5269-7
[7]   Nonfunctional requirements: From elicitation to conceptual models [J].
Cysneiros, LM ;
Leite, JCSD .
IEEE TRANSACTIONS ON SOFTWARE ENGINEERING, 2004, 30 (05) :328-350
[8]  
Davison RM, 2012, MIS QUART, V36, P763
[9]   Putting requirement management into praxis: dealing with nonfunctional requirements [J].
Ebert, C .
INFORMATION AND SOFTWARE TECHNOLOGY, 1998, 40 (03) :175-185
[10]  
Ernst NA, 2010, LECT NOTES COMPUT SC, V6182, P143, DOI 10.1007/978-3-642-14192-8_15