An Excursion to Ontology-Based Non-functional Requirements Specification

It is challenging to ask stakeholders to explicitly provide Non-Functional Requirements (NFRs) for the software due to the domain-specific and context-sensitive nature. A formal and unambiguous specification of NFRs is provided by creating an NFRs ontology based on domain knowledge and quality models. Ontology concepts make NFRs specification definite, complete, consistent, and convenient to share and reuse. In this paper, we intend to examine the approaches for specifying NFRs. The purpose of this study is to disseminate, analyze, and deconstruct the published research in the field, and select metrics for a comparative assessment.