On Non-Functional Requirements: A Survey - Critique

Running head: SOFTWARE ENGINEERING METHODOLOGY
Software Engineering Methodology
Name of the Student
Name of the University
Author Note

1SOFTWARE ENGINEERING METHODOLOGY
Table of Contents
Introduction:...............................................................................................................................2
Intention and Content of the selected article:.............................................................................2
Used Methodology for Survey:..................................................................................................3
Findings from the Research:......................................................................................................3
Problem or Issues highlighted by the authors:...........................................................................4
Conclusion:................................................................................................................................5
References:.................................................................................................................................6

2SOFTWARE ENGINEERING METHODOLOGY
Introduction:
In the system engineering methodology the non-functional requirements or the NFR is
a requirement criteria which is used for judgement of operation of a system rather than some
specific behaviours [1]. The non-functional requirement of the software engineering
contrasted with the functional requirement of the system. In most of the cases the non-
functional requirement is considered as the quality attributes of a specific type of system. In
the case of the software the non-functional requirements are the reliability, security,
maintainability, performance, usability and scalability.
In this article, a paper on non-functional requirement in software engineering
methodology will be critiqued properly. For performing the critique, the selected article is the
“On Non-Functional Requirements: A Survey.” In this article the authors reviewed the art of
the treatment of the non-functional requirement in the software engineering methodologies.
This article will also describe the content and intention of the article. From the broad
discussion of the selected article various issues highlighted by the author will be evaluated.
Further how the selected article is relevant with the unit of study will be discussed.
Intention and Content of the selected article:
The main intention of the selected article is providing a brief idea about the non-
functional requirement for software engineering methodologies and the importance of this in
the software engineering. Also, the article “On Non-Functional Requirements: A Survey.”
intends to provide a brief review of the literature of the non-functional requirement and the
most advanced uses of it in the software engineering processes.
Describing the content of the article, in very first the authors has briefly defined about
the non-functional requirements. As per the authors in this article the NFR or the non-
functional requirement is one of the major aspect for development of the software [2]. This
article has discussed about framework of the non-functional requirements. According to the
authors, this NFR framework is very much important for decoupling the concepts of the
functionalities from the other quality attributes. In this section the authors has discussed about
the basic non-functional requirements for software engineering which includes performance,
reliability, availability, compatibility and the usability. Authors has also shared the
importance of the distinction between the functionality and the other qualities in the field of
the software engineering. As per the authors the distinctions helps the software engineers