An investigation of use case quality in a large safety-critical software development project

Anda, Bente; Hansen, Kai T.; Sand, Gunhild

doi:10.1016/j.infsof.2009.04.005

Cited by 26 publications

(33 citation statements)

References 19 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Also, the applicability of existing use case templates proposed in different contexts has not been reported yet. Each use case template provides different documentation details specific to a purpose (may be effective only in the same context) hence, the actual intent of the use cases in a development project is an important input for determining the appropriate format [10]. We found as many as twenty use case templates through two-stage search and selection process.…”

Section: Citations Existing Use Case Templatesmentioning

confidence: 99%

“…2. "The terminology should be consistent throughout the use case specifications and should not impose unnecessary constraints on the design" [10]. 3.…”

Section: (Ii) Domain Modelingmentioning

confidence: 99%

“…Likewise, these observations can also be applied for the planning and estimation purpose, where the details of the main actors and the prioritized functionalities must be seized. Also, the use cases applied for the same purpose must consist of information about the included and extended use cases in the specifications, along with their significant level of details while specifying requirements in the use case template [10,8]. Table 9 shows the distinctive structure of the use case template that can be used to specify the use case textual descriptions for the purposes of modeling and designing, planning and estimation, and automated text processing.…”

Section: (Ii) Domain Modelingmentioning

confidence: 99%

“…Use cases have gradually become a widely accepted requirement specification technique both in research domain [2,10,13,32,33,74,103,151] as well as, to some extent, in industrial practice [8,9,39,59,109]. Nevertheless, their inherent utilization of natural language and a behavior of requirement documentation in a semi-conventional way, mean that they are affected by issues such as ambiguity, redundancy, inconsistency, and incompleteness [2,32,146].…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

A systematic literature review of use case specifications research

Tiwari

Gupta

2015

Information and Software Technology

View full text Add to dashboard Cite

Section: Citations Existing Use Case Templatesmentioning

confidence: 99%

“…2. "The terminology should be consistent throughout the use case specifications and should not impose unnecessary constraints on the design" [10]. 3.…”

Section: (Ii) Domain Modelingmentioning

confidence: 99%

Section: (Ii) Domain Modelingmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

A systematic literature review of use case specifications research

Tiwari

Gupta

2015

Information and Software Technology

View full text Add to dashboard Cite

“…Anda et al (2009) improved a previous use case inspection technique (Anda and Sjøberg, 2002), by defining an initial model of quality attributes for UML use cases.…”

Section: Quality Of Scenariosmentioning

confidence: 99%

Analysis of Natural Language Scenarios

CALISAYA¹

View full text Add to dashboard Cite

Use case specifications: How complete are they?

Tiwari

Gupta

2019

J Software Evolu Process

View full text Add to dashboard Cite

The flexibility of the use cases in specifying requirements from informal textual descriptions to more formal ones makes them usable in different contexts and purposes. However, the versatility of use cases regarding their admissible structure raises a natural concern about the specification completeness. This paper reports on the analysis of the eight different variants of use case template regarding their functional completeness, ability to express the set of particular functionalities, by comparing their information contents exercised by comprehensive questionnaires on five different problem specifications. The questionnaire was obtained from two sources: one based on the understanding of the functionality to be implemented and the other based on the functionality documented in eight different use case templates under study. Our results suggested that use cases can be used to specify a complete set of requirements intended to develop a software system. We found that the choice of a use case template influences the completeness of the specification. A more detailed analysis of the eight different variants of use case template resulted in the identification of 21 significant use case elements. We showed that by incorporating these significant use case elements in a given template, the completeness of the specification could be further enhanced.

show abstract

An investigation of use case quality in a large safety-critical software development project

Cited by 26 publications

References 19 publications

A systematic literature review of use case specifications research

A systematic literature review of use case specifications research

Analysis of Natural Language Scenarios

Use case specifications: How complete are they?

Contact Info

Product

Resources

About