A system model for an OO specification language is any timed state transition system whose states are composed of a data store, a control store, and a message pool. To define a semantics for any OO specification language (as e.g. UML) is the art of defining the transition function $Delta$ depending on the current state and on the input sofar that moreover observes certain rules. Having defined what a system model is, the challenge now is to establish when such a system model satisfies a message interchange specification (expressed by means of UML interactions).
@InProceedings{cengarle:DagSemProc.06351.11, author = {Cengarle, Mar{\'\i}a Victoria}, title = {{System model for UML – The interactions case}}, booktitle = {Methods for Modelling Software Systems (MMOSS)}, pages = {1--19}, series = {Dagstuhl Seminar Proceedings (DagSemProc)}, ISSN = {1862-4405}, year = {2007}, volume = {6351}, editor = {Ed Brinksma and David Harel and Angelika Mader and Perdita Stevens and Roel Wieringa}, publisher = {Schloss Dagstuhl -- Leibniz-Zentrum f{\"u}r Informatik}, address = {Dagstuhl, Germany}, URL = {https://drops.dagstuhl.de/entities/document/10.4230/DagSemProc.06351.11}, URN = {urn:nbn:de:0030-drops-8572}, doi = {10.4230/DagSemProc.06351.11}, annote = {Keywords: System model, UML, interaction} }
Feedback for Dagstuhl Publishing