Abstract
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.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callMore From: International Journal of Software Engineering and Knowledge Engineering
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
