A Methodological Assistant for Use Case Diagrams

Abstract

Use case driven analysis is the corner stone of software and systems modeling in UML and SysML, respectively. Although many books and tutorials have discussed the use of use case diagrams, students and industry practitioners regularly face methodological problems in writing good use cases. This paper defines a methodological assistant that helps designing use case diagrams relying on formalized rules and reuse of previous diagrams. The methodological assistant is implemented in Python. It is interfaced with the free SysML software TTool, and with Cameo Systems Modeler.

Recommender systems in model-driven engineering

“…The second approach is a modelling assistant for use case diagrams called UCcheck [9]. This tool has a wizard to create new use case diagrams using an existing one as a reference, from which suitable actors and use cases are recommended.…”

“…Other approaches can be used with several tools, but are still tool-dependent. This is the case of UCcheck [9], an assistant for use case diagrams coded in Python that supports use case diagrams specified with TTool-a free software from Telecom Paris-and the Cameo Systems Modeler.…”

“…For quality assurance, BPMoQualAssess [60] recommends improvements for process models based on rules modelling expected quality criteria (e.g. regarding size, nesting levels and element ratios), and UCcheck [9] provides advices for improving use case diagrams based on sets of rules and guidelines.…”

Checking SysML Models Against Safety and Security Properties

“…Writing good use cases to have a good basis for the design phase is not trivial. In [46] Rizzo-Aquino, de Saqui-Sannes and Vingerhoeds present UCCheck, a methodological assistant for use case diagrams creators. UCCheck detects errors such as confusion between high-level functions (appropriate for a use case diagrams) and elementary actions (appropriate for activity diagrams documenting the use cases).…”

“…For instance, the authors of this paper have frequently noticed that use case diagrams are often misused by newcomers to SysML. In [46], Rizo Aquino, de Saqui-Sannes and…”