Treating NFR as First Grade for Its Testability

Abstract

<p> <span>Practitioners and researchers in the field of software engineering have realized that Non Functional requirement have not received due attention and second grade (or no) treatment has been meted out to Non Functional Requirements. Many software products/systems are finally not acceptable because of such an approach. This casual approach of treating NFR has moved on to Testing also. Testing of NFR has never been taken seriously. Here in this work, we attempt to under</span><span>- </span><span>stand what needs to be done for proper consideration of NFR, so that they are treated as seriously as the Functional Requirements. In an attempt to treat NFR as seriously as FR we work on the testability of NFR by refining an abstract quality concern into concrete NFR statements. We show that quality concerns needs to be analyzed, for identifying and finally converting them into appropriate and unambiguous NFR. Once a high quality of NFR is ensured then the con</span><span>se</span><span>quent testing of these NFRs will become as effective as that of Functional Requirement. We finally propose a revised model of Problem Analysis and Requirement Specification. A step wise refinement model for quality concern into test</span><span>- </span><span>able Non Functional Requirement is also proposed.</span><span></span> </p> <p> <span></span> </p> <p> <span></span> </p&gt

Characterizing Software Quality Assurance Practices in Kenya

“…Non-Functional Requirement tests include Usability tests, Performance tests, Compatibility tests, and Security tests. Authors in [26] observed that such tests had been deemphasized as they were perceived as low risk. Our results confirm that the non-functional tests are the least performed than the functional tests.…”