Improving requirements quality using essential use case interaction patterns

Kamalrudin, Massila; Hosking, John; Grundy, John

doi:10.1145/1985793.1985866

Cited by 58 publications

(37 citation statements)

References 25 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…The DODT tool applies NLP and a domain ontology to semi-automatically transform NL requirements into higher quality semi-boilerplate requirements for embedded systems development [14]. The MaramaAI tool extracts semi-formal Essential Use Cases (EUC) models from natural language requirements and enables an end user to detect inconsistency, incompleteness, and incorrectness by visually highlighting the differences to a baseline EUC [27]. The EuRailCheck project uses rule-based techniques and ontologies to validate formalized requirement fragments and pinpoint flaws that are not easy to detect in an informal setting [8].…”

Section: Natural Language Processing For Rementioning

confidence: 99%

Improving agile requirements: the Quality User Story framework and tool

et al. 2016

View full text Add to dashboard Cite

User stories are a widely adopted requirements notation in agile development. Yet, user stories are too often poorly written in practice and exhibit inherent quality defects. Triggered by this observation, we propose the Quality User Story (QUS) framework, a set of 13 quality criteria that user story writers should strive to conform to. Based on QUS, we present the Automatic Quality User Story Artisan (AQUSA) software tool. Relying on natural language processing (NLP) techniques, AQUSA detects quality defects and suggest possible remedies. We describe the architecture of AQUSA, its implementation, and we report on an evaluation that analyzes 1023 user stories obtained from 18 software companies. Our tool does not yet reach the ambitious 100 % recall that Daniel Berry and colleagues require NLP tools for RE to achieve. However, we obtain promising results and we identify some improvements that will substantially improve recall and precision.

show abstract

Section: Natural Language Processing For Rementioning

confidence: 99%

Improving agile requirements: the Quality User Story framework and tool

et al. 2016

View full text Add to dashboard Cite

show abstract

“…Estos métodos son: Especificación de r equisitos uso del lenguaje natural: La especificación de requisitos, con frecuencia se realiza utilizando lenguaje natural. Una ventaja principal de utilizar lenguaje natural para especificar requisitos es que son comprensibles por los stakeholders 1 (Kamalrudin et al, 2011).…”

Section: Especificación De Requerimientosunclassified

Reflexión Sobre La Especificación De Requerimientos Dentro De Un Contexto Universitario

Gómez¹,

Ibáñez²

2017

RCTA

View full text Add to dashboard Cite

This paper is aiming to deepen the concepts of engineering requirements (ER), seeking to know what alternatives techniques or forms there are for specification requirements, a process that is part of the development of Software. The Guide to the software engineering body of knowledge (SWEBOK) states that there are two types of requirements specifications; the specification of system requirements and software requirements specification, the first talk of global solutions for the organization and the second speaks of the development of requirements-level features, this paper only the software of specification of requirements was addressed.

show abstract

“…Due to its high reusability, workflow patterns have a wide applicability in both academia and industry [13]. Figure 1 shows the popularity of workflow patterns through comparing with other requirements patterns, such as event patterns [11], essential use cases [2], problem frames [14] and object system models [15] in Google trends (http://www.google.com/trends/). We can see from much more attention than other requirements patterns.…”

Section: Workflow Patternsmentioning

confidence: 99%

“…Kamalrudin et al [2] reported a technique to improve requirements quality using Essential Use Case (EUC) Interaction Patterns, and developed a CASE tool to support their work. This technique first transformed natural language requirements to semi-formal requirements, i.e.…”

Section: Related Workmentioning

confidence: 99%

Improving Natural Language Requirements Quality Using Workflow Patterns

Wang

Yang

Chang

et al. 2013

IEICE Trans. Inf. & Syst.

View full text Add to dashboard Cite

SUMMARYNatural language (NL) requirements are usually humancentric and therefore error-prone and inaccurate. In order to improve the 3Cs of natural language requirements, namely Consistency, Correctness and Completeness, in this paper we propose a systematic pattern matching approach supporting both NL requirements modeling and inconsistency, incorrectness and incompleteness analysis among requirements. We first use business process modeling language to model NL requirements and then develop a formal language -Workflow Patterns-based Process Language (WPPL) -to formalize NL requirements. We leverage workflow patterns to perform two-level 3Cs checking on the formal representation based on a coherent set of checking rules. Our approach is illustrated through a real world financial service example -Global Equity Trading System (GETS).

show abstract

Improving requirements quality using essential use case interaction patterns

Abstract: Improving requirements quality using essential use case interaction patterns.

Cited by 58 publications

References 25 publications

Improving agile requirements: the Quality User Story framework and tool

Improving agile requirements: the Quality User Story framework and tool

Reflexión Sobre La Especificación De Requerimientos Dentro De Un Contexto Universitario

Improving Natural Language Requirements Quality Using Workflow Patterns

Contact Info

Product

Resources

About