Vijayanand Chelliahdhas, HCL Technologies Ltd.
Typically organizations tend to adapt a one-size-fits-all approach to validate a system for its non-functional (NF) requirements. Not surprisingly, a significant number of non-functional issues surface post go-live. Such unpredictability in the non-functional quality of a software implementation can be largely attributed to the lack of a focused approach to non-functional testing targeting the critical technical and non-functional risks in the system under test (SUT).
This challenge can be mitigated by conducting a Non-Functional Risk Assessment exercise to develop a comprehensive Risk Catalogue. As a result, the NF test strategy and scenarios would be directly mapped to all the technical and NF risks in the system.
The “NF Risk Assessment Framework” described in this paper enables to precisely determine the key vulnerable areas in the system and not just the application, addresses coverage across multiple non-functional domains of the SUT and not just performance, ensures the tests are designed to simulate production condition as close as possible and helps to prioritize test activities based on the criticality assigned.
Target audience: Expert/Advanced