A value-based approach to prioritise non-functional requirements during software project development Online publication date: Fri, 10-May-2013
by Rahul Thakurta
International Journal of Business Information Systems (IJBIS), Vol. 12, No. 4, 2013
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.
Online publication date: Fri, 10-May-2013
If you are not a subscriber and you just want to read the full contents of this article, buy online access here.Complimentary Subscribers, Editors or Members of the Editorial Board of the International Journal of Business Information Systems (IJBIS):
Login with your Inderscience username and password:
Want to subscribe?
A subscription gives you complete access to all articles in the current issue, as well as to all articles in the previous three years (where applicable). See our Orders page to subscribe.
If you still need assistance, please email email@example.com