Answers are grounded in this paper and cite their sources.
Non-autonomous Petri nets offer a language especially adapted for controller specifications. They are typically used in the design phase often with no clear connection to the analysis phase, including requirements specification. This paper shows how use cases can be used to support requirements specification amenable to a direct transformation to IOPT nets, a class of non-autonomous Petri nets. To that end, we propose a set of semi-formal rules for use case descriptions, including use case relationships, which take advantage of the concepts available in IOPT nets, namely input and output signals and events and net addition, a net composition operation.
No takes yet. Share an insight, caveat, or question.
Barros et al. (2014) studied this question.
Synapse has enriched 4 closely related papers on similar clinical questions. Consider them for comparative context: