Toward Engineered, Useful Use Cases.

Williams, Clay; Kaplan, Matthew; Klinger, Tim; Paradkar, Amit

doi:10.5381/jot.2005.4.6.a4

Cited by 23 publications

(15 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…According to [17], the lack of well defined semantics is one of the limitations to a wider adoption of use cases in industry. In this paper, we presented a meta-model for textual use case description that could serve as a definition of static semantics.…”

Section: Discussionmentioning

confidence: 99%

A Meta-Model for Textual Use Case Description.

Somé¹

2009

JOT

View full text Add to dashboard Cite

A Use Case is a specification of interactions involving a system and external actors of that system. The capability for use case modeling has been integrated to the Unified Modeling Language (UML) since its inception. However, use cases are only defined at an abstract level, as the UML Specification does not discuss use case description in text form. In this paper, we propose an abstract syntax for textual use case description as a meta-model extension of the UML Specification. This meta-model is based on elements commonly found in use case templates. The meta-model also includes OCL constraints for ensuring consistency with the UML specification.

show abstract

Section: Discussionmentioning

confidence: 99%

A Meta-Model for Textual Use Case Description.

Somé¹

2009

JOT

View full text Add to dashboard Cite

show abstract

“…Continuing, and following Hoffmann et al's [16] account, there is the situation where -the alarm can be raised at any time (10), which -triggers the driver (11) to trigger the remote control (12), -to create a signal (13), -that flows to the alarm to be processed (14), and -turns off the alarm (15).…”

Section: Fm-based Descriptionmentioning

confidence: 98%

“…Their shortcomings are also known [14,15]. According to Constantine and Lockwood [13], Owing in part to imprecise definition and in part to the confusion and conflation of the various possible uses and purpose of use cases, many use cases, including published ones, intermingle analysis and design, business rules and design objectives, internals and interface descriptions, with gratuitous asides thrown in to cover all bases.…”

Section: Introductionmentioning

confidence: 99%

Schematizing UML Use Cases

Al-Fedaghi

Alrashed

2013

2013 Fourth World Congress on Software Engineering

View full text Add to dashboard Cite

This paper deals with the problem of achieving consistency between a UML use case model and its corresponding set of textual descriptions. One solution that has been proposed is a format for textual use case descriptions that provides the conceptual background for textual use case descriptions while integrating them into the UML metamodel. The paper suggests that problems related to UML diagrams (multiplicity of representations and consistency among them) stem from lack of an underlying conceptual model of the basic system. This idea is demonstrated by contrasting the proposed format with a new flow-based methodology. The demonstration indicates that the latter provides a viable alternative for basic representation of system requirements.

show abstract

“…Since their invention by Ivar Jacobson in 1986 [Jacobson87,Jacobson04], and although having some deficiencies [Glinz00,Williams05] use cases have gained wide-spread acceptance as a means to describe interactions between a system and its environment [McPhee02,Neill03]. Today, the Unified Modeling Language [OMG07] is a widely accepted standard defining the central use case modeling concepts.…”

Section: Introductionmentioning

confidence: 99%

Towards the Integration of UML- and textual Use Case Modeling.

Hoffmann¹,

Lichter²,

Nyßen³

2009

JOT

View full text Add to dashboard Cite

In this paper, we present a metamodel for textual use case descriptions, structurally conforming to the UML, to specify the behavior of use cases in a flow-oriented manner. While being primarily targeted at supporting requirements engineers in creating consistent use case models, the metamodel defines a textual representation of use case behavior that is easily understandable for readers, who are unaware of the underlying metamodel. Hence, the known benefits of natural language use case descriptions are preserved. Being formalized, consistency between UML-based use case representations and their textual descriptions can be automatically ensured. With NaUTiluS we present an extensible, Eclipse-based toolkit, which offers integrated UML use case modeling support, as well as editing capabilities for their textual descriptions.

show abstract

Toward Engineered, Useful Use Cases.

Cited by 23 publications

References 11 publications

A Meta-Model for Textual Use Case Description.

A Meta-Model for Textual Use Case Description.

Schematizing UML Use Cases

Towards the Integration of UML- and textual Use Case Modeling.

Contact Info

Product

Resources

About