An Approach for Creating Sentence Patterns for Quality Requirements

Abstract

Requirements are usually categorized in functional requirements (FRs) and quality requirements (QR). FRs describe "things the product must do" while QRs describe "qualities the product must have". Besides the definition, classification, and representation problems identified by Glinz, there are two further problems with current definitions of quality requirements: (i) the definitions are imprecise and thus difficult to understand and apply, and (ii) the definitions provide no guidance or support for their application in a given organizational context. To tackle these two problems, we propose an approach that-given a quality attribute (e.g., performance) as input-provides a means to specify quality requirements by sentence patterns regarding this quality attribute. In this paper, we contribute a detailed presentation and description of our approach and a discussion of our lessons learnt while instantiating it for performance requirements. Additionally, we give guidance on how to apply our approach for further quality attributes. Through this approach, we aim at encouraging researchers to help us improve the precision of definitions for quality requirements and support practitioners in eliciting and documenting better quality requirements.

Requirements Smells como indicadores de má qualidade na especificação de requisitos: Um Mapeamento Sistemático da Literatura

“…Os autores sugerem o uso de Requirements Smells para fornecer feedback, como indicadores de má qualidade nas especificações. No trabalho de [14] foi apresentada uma metodologia para especificar requisitos de qualidade por meio de atributos de qualidade baseado em padrões. Os autores descrevem que a metodologia pode ser utilizada para fornecer feedback sobre elementos dos requisitos por meio de Requirements Smells.…”

Technical Report on Neural Language Models and Few-Shot Learning for Systematic Requirements Processing in MDSE

“…In addition to the experience-based templates, in the literature there exist approaches that deal with the extraction of requirements templates from legacy requirements. For example, [21] develops a set of sentence templates for quality requirements, [23] presents a metamodel for software requirements. In addition, the PABRE framework presents a method for using requirements templates [24] based on a catalog of 29 QR patterns [54] and 37 non-functional patterns [47].…”