Date Added: Jul 2012
Software Development has started experiencing the need of consideration of NFR (Non Functional Requirements) for producing high quality acceptable software. Mostly software engineering literature has considered only for testing functional requirements. In context of such a need this paper attempts to consider NFR, resulting from quality concerns of stakeholder, along with their impact and effect on testing. The authors identify and bring out issues, in testing of NFR that warrant, purposeful and meaningful considerations. Testing happens to be an important phase in software development lifecycle. It consumes around 70% of resource required for developing a software system. According to Brian Lawrence, among the top 10 risks of requirement engineering is "Overlooking a crucial requirement" and "Modelling only Functional Requirements".