Challenging Incompleteness of Performance Requirements by Sentence Patterns

Eckhardt, Jonas; Vogelsang, Andreas; Femmer, Henning; Mager, Philipp

doi:10.1109/re.2016.24

Cited by 23 publications

(22 citation statements)

References 21 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…We already instantiated our approach for one specific quality attribute (performance) and conducted an empirical evaluation with respect to its applicability [8]. The results indicated that the approach is applicable and besides the constructive nature of our approach, further supports analytic quality assessment with syntactic analyses.…”

Section: Introductionmentioning

confidence: 60%

“…The result of this step is a content model for performance that ideally is a superset of all performance aspects mentioned in literature. A detailed description of the resulting content model for performance can be found in Eckhardt et al [8].…”

Section: A Step 1: Context-independent Definitionmentioning

confidence: 99%

“…Furthermore, the scope of the requirement is necessary for the activity plan test, as the test engineer needs this information for assigning the test to a person/team responsible. The final context-dependent content model can be found in Eckhardt et al [8].…”

Section: Time Propertymentioning

confidence: 99%

“…In our running example, we iterated through the set of content items in a pair of researchers and discussed how to adequately represent this content element in terms of a sentence fragment. The complete set of patterns can be found in Eckhardt et al [8]. An exemplary instance of a sentence is…”

Section: Step 4: Concretizationmentioning

confidence: 99%

See 3 more Smart Citations

An Approach for Creating Sentence Patterns for Quality Requirements

Eckhardt¹,

Vogelsang²,

Femmer³

2016

2016 IEEE 24th International Requirements Engineering Conference Workshops (REW)

Self Cite

View full text Add to dashboard Cite

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.

show abstract

Section: Introductionmentioning

confidence: 60%

Section: A Step 1: Context-independent Definitionmentioning

confidence: 99%

Section: Time Propertymentioning

confidence: 99%

Section: Step 4: Concretizationmentioning

confidence: 99%

See 2 more Smart Citations

An Approach for Creating Sentence Patterns for Quality Requirements

Eckhardt¹,

Vogelsang²,

Femmer³

2016

2016 IEEE 24th International Requirements Engineering Conference Workshops (REW)

Self Cite

View full text Add to dashboard Cite

show abstract

“…Lightweight Requirements Modeling: The use of constrained natural language is an approach to create requirements models while keeping the appearance of natural language. Several authors propose different sets of sentence patterns that should be used to formulate requirements [8,4]. Besides the advantage that requirements are uniformly formulated, the requirements patterns enrich parts of the requirement with information about the semantics.…”

Section: Background and Related Workmentioning

confidence: 99%

A Lightweight Multilevel Markup Language for Connecting Software Requirements and Simulations

Pudlitz

Vogelsang

Brokhausen

2019

Requirements Engineering: Foundation for Software Quality

Self Cite

View full text Add to dashboard Cite

Usefulness of open domain model for identifying missing software requirements concepts

Zhao,

Zhang,

Lian

2023

Softw Pract Exp

View full text Add to dashboard Cite

SummaryDetecting missing requirements during software development is crucial to avoid unexpected consequences. However, this task is challenging due to limited domain knowledge of requirements analysts and the dynamic nature of software requirements. Previous studies have shown that requirement‐oriented domain models can help identify omissions in requirements, but they are often incomplete for many domains. Meanwhile, domain models constructed from other artifacts are available online. This raises the question: Can these domain models be useful in identifying missing functional information in requirement specifications? To address this question, we conducted a study to measure the overlap between entities in domain models and requirements. We analyzed the occurrence of overlapped entities, considering four distribution characteristics: the type of entities in the domain model, the distribution of mapped entities in the domain model, the family belonging of the mapped entities in the domain model, and the distribution of mapped entities in the requirements. Based on our findings, we proposed recommendations for missing requirements. Additionally, we performed experiments, including the use of the proposed metric “ancestors of the highest level with the most mapped entities” (AHME). The results showed significant improvements with gains of 146% and 223% in the two domains, highlighting the benefits of these distribution characteristics.

show abstract

Challenging Incompleteness of Performance Requirements by Sentence Patterns

Cited by 23 publications

References 21 publications

An Approach for Creating Sentence Patterns for Quality Requirements

An Approach for Creating Sentence Patterns for Quality Requirements

A Lightweight Multilevel Markup Language for Connecting Software Requirements and Simulations

Usefulness of open domain model for identifying missing software requirements concepts

Contact Info

Product

Resources

About