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.