Answers are grounded in this paper and cite their sources.
A use case is a specification of interactions involving a system and external actors of that system. The intuitive, user centered nature of textual use cases is one of the reasons for the success of the use case approach. A certain level of formalization is however needed to automate use case based system development, including tasks such as design synthesis, verification and validation. In this paper, a mapping from textual use cases to a formal model (Petri nets) is proposed. Use cases are described in a restricted-form of natural language. The abstract syntax of the language is formally defined using a tuple structure. The mapping from use cases to Petri nets considers use cases sequencing constraints defined at the syntactic-level, and provides a definition of execution semantics to use cases.
No takes yet. Share an insight, caveat, or question.
Stéphane S. Somé (2010) studied this question.
Synapse has enriched 10 related papers. Consider them for comparative context: