
Language to specify Value Added Invariants for Use Cases
With this language, value added invariants for use cases can be modelled as proposed in [1]. The idea is that each actor in a use case gives and takes values during a system's lifetime where the total amount of values in the system stays invariant. In [1] a graphical notation is used. We provide a textual syntax here. The metamodel contains OCL constrains that check if the invariant for the complete use case is fulfilled (i.e, all values given must be received and the other way around). These are checked automatically by EMFText each time a model is saved.
Contents |
org.emftext.language.usecaseinvariant
org.emftext.language.usecaseinvariant.resource.ucinv
org.emftext.language.usecaseinvariant.resource.ucinv.ui
[1] Roussev, B., Wu, J.: Transforming use case models to class models and ocl-speciļ¬cations. Int. Journal of Computers and Applications 29(1) (2007)