ViPER NaUTiluS
From ViPER Wiki
ViPER NaUTiluS is build upon the ViPER Platform and delivers narrative use case description toolkit, including editing, evaluation, and simulation capabilities. It is bundled as part of the ViPER IDE.
[edit] Remarks
ViPER NaUTiluS is just going through some mayor changes, which affect the metamodels as well as the editors. Some of the information here might be outdated soon!
[edit] Introduction
While there is a manifold of notations for detailed descriptions of the behaviour captured by use cases, textual descriptions are the form that is most widely used. Nowadays the UML specification represents a widely accepted standard w.r.t. definition of terms and concepts related to use cases. I.e. the UML specification describes the elements by which a set of use cases can be captured and structured, but it does not prescribe how the behaviour encapsulated within the single Use Cases should be described. Especially it does not cover a form for textual use case descriptions. As a consequence, most tools offering UML modeling facilities do not support creating textual use case descriptions on a level beyond offering simple text fields. Hence, textual use case descriptions are mostly captured using additional tools, e.g., word processors like Microsoft Word. In both cases, i.e., when using tools offering facilities for editing textual use case descriptions or when using additional tools, UML-based representations of a use case model and the textual descriptions of use cases captured in such a UML model are maintained and persisted without being strongly coupled. This often leads to consistency problems between those two representations when a use case model as a whole evolves.
To ensure consistency between a UML-based representation of a use case model and the textual descriptions of use cases captured in a UML model automatically, the contents of a textual use case description must be "understood" by a modeling tool. This is a non-trivial problem, because textual use case descriptions are mostly verbalized in more or less natural language, which currently cannot be analysed algorithmically if its usage is completely unconstrained. So, we decided to try to structure textual use case descriptions in a way that
- Natural language can be used in dedicated areas, and
- To some degree, it can be algorithmically checked whether textual use case descriptions and a UML model capturing described use cases and their relationships are consistent with each other.
The definition of the structure of textual use case descriptions is given through a meta model for textual use case descriptions which was then implemented by means of EMF. Based on this meta model implementation, an editor for textual use case descriptions offering proactive and reactive support for ensuring consistency between textual use case descriptions and a UML model has been realized.
[edit] Plug-in Architecture
|
|
The ViPER NaUTiluS feature is organized into the following sub-features:
|
