Analysis of Non-functional Requirements: Current Issues and Approaches: (A Survey)

Abstract

In today's evolutionary era, eliciting both functional and nonfunctional requirements is the primary responsibility of a requirement engineer. The industry has recently adopted the practice of measuring non-functional requirements as second class or ad hoc, which is the case in the event of software failure, while working with functional requirements as primary class requirements. Here, we used questionnaires to poll various software companies on the main vulnerabilities that impact the NF software requirements and the problems with the requirements that lead to software failure. The likelihood of software success can be increased when non-functional requirements are incorporated into the requirement level. The challenges and obstacles that software houses face due to non-functional requirements are described in this literature review, along with our efforts to overcome them by offering some helpful suggestions and solutions to reduce the likelihood that software will fail due to non-functional requirements and to produce higher-quality software.