Impact of Non-functional Requirements on Requirements Evolution
Kiran Khatter, Arvind Kalia
Abstract
Kiran Khatter, Arvind Kalia
Abstract
Software impacts almost every aspect of modern society. Developers of a software system are responsible for identifying the requirements of the application, developing software that implements the requirements, and for allocating appropriate resources (processors and communication networks). Development of quality software systems has always been a great challenge for software developers. In practice, it happens that non-functional aspects are often ignored while focusing on the functionality of the system. Many systems have failed because of negligence of non-functional requirements. To study the impact of non-functional requirements on requirements evolution, this paper discusses various approaches, available in the literature, to represent non-functional requirements during software development. To study the impact of non-functional requirements on requirements evolution, this paper is focused on three issues: Different views on non-functional requirements, Representation of non-functional requirements and Dealing with non-functional requirements.
OpenAlex reports 12 citations for this work. Citation counts describe recorded attention and do not establish research quality.
A contribution statement is not available in the OpenAlex record.
Method details are not available in the OpenAlex metadata.
Findings are not separately available in the OpenAlex metadata.
Limitations are not available in the OpenAlex metadata.
Application details are not available in the OpenAlex metadata.
Software impacts almost every aspect of modern society. Developers of a software system are responsible for identifying the requirements of the application, developing software that implements the requirements, and for allocating appropriate resources (processors and communication networks). Development of quality software systems has always been a great challenge for software developers. In practice, it happens that non-functional aspects are often ignored while focusing on the functionality of the system. Many systems have failed because of negligence of non-functional requirements. To study the impact of non-functional requirements on requirements evolution, this paper discusses various approaches, available in the literature, to represent non-functional requirements during software development. To study the impact of non-functional requirements on requirements evolution, this paper is focused on three issues: Different views on non-functional requirements, Representation of non-functional requirements and Dealing with non-functional requirements.
Key concepts: Functional requirement, Non-functional requirement, Non-functional testing, Software requirements specification, Computer science, Requirements analysis, Functional specification, Requirements management