TY - GEN
T1 - Exploiting a goal-decomposition technique to prioritize non-functional requirements
AU - Daneva, M.
AU - Kassab, M.
AU - Ponisio, M. L.
AU - Wieringa, R. J.
AU - Ormandjieva, O.
PY - 2007
Y1 - 2007
N2 - Business stakeholders need to have clear and realistic goals if they want to meet commitments in application development. As a consequence, at early stages they prioritize requirements. However, requirements do change. The effect of change forces the stakeholders to balance alternatives and reprioritize requirements accordingly. In this paper we discuss the problem of priorities to non-functional requirements subjected to change. We, then, propose an approach to help smooth the impact of such changes. Our approach favors the translation of nonoperational specifications into operational definitions that can be evaluated once the system is developed. It uses the goal-question-metric method as the major support to decompose non-operational specifications into operational ones. We claim that the effort invested in operationalizing NFRs helps dealing with changing requirements during system development. Based on this transformation and in our experience, we provide guidelines to prioritize volatile non-functional requirements.
AB - Business stakeholders need to have clear and realistic goals if they want to meet commitments in application development. As a consequence, at early stages they prioritize requirements. However, requirements do change. The effect of change forces the stakeholders to balance alternatives and reprioritize requirements accordingly. In this paper we discuss the problem of priorities to non-functional requirements subjected to change. We, then, propose an approach to help smooth the impact of such changes. Our approach favors the translation of nonoperational specifications into operational definitions that can be evaluated once the system is developed. It uses the goal-question-metric method as the major support to decompose non-operational specifications into operational ones. We claim that the effort invested in operationalizing NFRs helps dealing with changing requirements during system development. Based on this transformation and in our experience, we provide guidelines to prioritize volatile non-functional requirements.
UR - http://www.scopus.com/inward/record.url?scp=80051974591&partnerID=8YFLogxK
UR - http://www.scopus.com/inward/citedby.url?scp=80051974591&partnerID=8YFLogxK
M3 - Conference contribution
AN - SCOPUS:80051974591
SN - 9781550144833
T3 - Proceedings of the 10th Workshop on Requirements Engineering, WER 2007
SP - 190
EP - 196
BT - Proceedings of the 10th Workshop on Requirements Engineering, WER 2007
T2 - 10th Workshop on Requirements Engineering, WER 2007
Y2 - 17 May 2007 through 18 May 2007
ER -