2011•Unpublished venueRequires access

Analyzing Non-Functional Requirements (NFRs) for software development

Mahrukh Umar, Naeem Ahmed Khan

Open publisher page 38 citations

Abstract

Non-Functional Requirements (NFRs) along with Functional Requirements (FRs) are the most significant and critical requirements for software development. NFRs are often ignored and inadequately specified during software development. If NFRs are not properly considered at early stages of software development, it may become very complex and expensive to address them later on. This paper analyzes various techniques, frameworks and recommendations from various literatures and identifies their limitations as well. Further, the paper discusses different techniques for individual NFRs specified in FURPS quality attribute model. The objective of this study is to provide an analytical comparison of NFRs techniques and perform critical analysis on NFRs.

About this research paper

What this paper is about

Non-Functional Requirements (NFRs) along with Functional Requirements (FRs) are the most significant and critical requirements for software development. NFRs are often ignored and inadequately specified during software development. If NFRs are not properly considered at early stages of software development, it may become very complex and expensive to address them later on. This paper analyzes various techniques, frameworks and recommendations from various literatures and identifies their limitations as well. Further, the paper discusses different techniques for individual NFRs specified in FURPS quality attribute model. The objective of this study is to provide an analytical comparison of NFRs techniques and perform critical analysis on NFRs.

Why it matters

OpenAlex reports 38 citations for this work. Citation counts describe recorded attention and do not establish research quality.

Key contribution

A contribution statement is not available in the OpenAlex record.

Method / approach

Method details are not available in the OpenAlex metadata.

Main findings

Findings are not separately available in the OpenAlex metadata.

Limitations

Limitations are not available in the OpenAlex metadata.

Applications

Application details are not available in the OpenAlex metadata.

Available abstract

Non-Functional Requirements (NFRs) along with Functional Requirements (FRs) are the most significant and critical requirements for software development. NFRs are often ignored and inadequately specified during software development. If NFRs are not properly considered at early stages of software development, it may become very complex and expensive to address them later on. This paper analyzes various techniques, frameworks and recommendations from various literatures and identifies their limitations as well. Further, the paper discusses different techniques for individual NFRs specified in FURPS quality attribute model. The objective of this study is to provide an analytical comparison of NFRs techniques and perform critical analysis on NFRs.

Key concepts: Computer science, Non-functional requirement, Software development, Software quality, Software, Reliability engineering, Software engineering, Risk analysis (engineering)

Related papers

Back to paper searchBrowse research topicsOriginal source
Analyzing Non-Functional Requirements (NFRs) for software development — Research Paper | ScholarLens