A value-based approach to prioritise non-functional requirements during software project development

Rahul Thakurta

International Journal of Business Information Systems, 2013, vol. 12, issue 4, 363-382

Abstract: Non-functional requirements determine the characteristics of a software product or service as a whole. The research described in this paper presents an empirical framework involving respondents of both the project and the business organisation, in order to select and prioritise a list of non-functional requirements for implementation during software project development. The assessment process takes into consideration the extent of relative value addition while making trade-off in selection of non-functional requirements for inclusion in the project's requirement set. The final results are expected to be beneficial to both the business and the project organisation by identifying and implementing the desired non-functional requirements that contributes to business value in a cost effective manner.

Keywords: non-functional requirements; NFR; business value; software projects; software development; value addition; value-added; trade-offs. (search for similar items in EconPapers)
Date: 2013
References: Add references at CitEc
Citations:

Downloads: (external link)
http://www.inderscience.com/link.php?id=53213 (text/html)
Access to full text is restricted to subscribers.

Related works:
This item may be available elsewhere in EconPapers: Search for items with the same title.

Export reference: BibTeX RIS (EndNote, ProCite, RefMan) HTML/Text

Persistent link: https://EconPapers.repec.org/RePEc:ids:ijbisy:v:12:y:2013:i:4:p:363-382

Access Statistics for this article

More articles in International Journal of Business Information Systems from Inderscience Enterprises Ltd
Bibliographic data for series maintained by Sarah Parker ().