Classification and Qualitative Analysis of Non-Functional Requirements Approaches

Abstract

LNBIP reports state-of-the-art results in areas related to business information systems and industrial application software development -timely, at a high level, and in both printed and electronic form. The type of material published includes• Proceedings (published in time for the respective event)• Postproceedings (consisting of thoroughly revised and/or extended final papers) • Other edited monographs (such as, for example, project reports or invited volumes) • Tutorials (coherently integrated collections of lectures given at advanced courses, seminars, schools, etc.) • Award-winning or exceptional theses LNBIP is abstracted/indexed in DBLP, EI and Scopus. LNBIP volumes are also submitted for the inclusion in ISI Proceedings.

ICTD systems development

“…Two recent publications by Hasan et al [4] and Loucopoulos et al [9] employed SLR in the field of non-functional requirements engineering were reviewed and observed the reference list to assess the volume of potential relevant primary studies of requirements elicitation approaches and validate the adopted search strategy of this paper.…”

“…It is not too farfetched to state that the reason that can help us understand why the noble idea of ICTD project development usually has much higher drop-out rates is the high abstraction and lack of understanding the system development requirements and their elicitation process although it has received much, but fragmented attention in isolated methods and tools development [4]. Because of the absence of a clear understanding of the system development requirements and their extraction process in the ICTD projects, the requirements elicitation process is, therefore, informal and peripheral, often ignored and inadequately specified and rarely treated as first-class elements in the project development [5,6].…”

“…The analysis and discussion contribute in the requirements elicitation process by serving the ICTD project developer as the means of understanding the system development requirements, their elicitation process, and deriving appropriate methods and tools for the requirements elicitation process. The work presented in this paper is partly based on our previous study [4] that classifies the documented approaches in the requirements engineering lifecycle. This paper expands the work in requirements elicitation phase by discussing a methodology for the process of requirement elicitation in ICTD system development.…”

Survey: Dealing Non-Functional Requirements at Architecture Level

“…The framework defines precisely how NFRs are expressed and integrated into an architectural-based development. Furthermore, it defines two methodologies for describing NFRs, an integration strategy, a set of refinement rules and a mapping strategy [29][30][31][32][33].…”

Null function classification using NFR matrix and decision tree

“…The services that are to be provided by software and the constraints within which it needs to operate are known as requirements. There can either by high-level abstract statements of services present within the requirements or some mathematical functional specifications that have detailed system constraints within them [3]. The services that are required by the client are established along with the constraints required to develop and operate the systems are provided through requirements engineering process [4].…”