Safety-LivenessSemanticsforUML2.0-StonyBrook.pptVIP

Safety-Liveness Semantics forUML 2.0 Sequence Diagrams Radu Grosu SUNY at Stony Brook Related Work PA and PO (Mauw, Alur, Muscholl, Peled, …): Not compositional. Not interested in compositionality. Live SC (Damm, Harel, Kugler): Elegant, alternative AT solution. Departure from UML. Triggered MSC (Cleaveland, Sengupta): Prescriptive/constraint-based. Must preorder. STAIRS (Haugen, Stoelen): Open semantics. Not fully formalized. Other semantics (Broy, Knapp, Krüger,…): Also depart from closed world semantics. Conclusions Presented an Automata-theoretic semantics that solves in a simple and elegant way one of the main open questions about UML 2.0 SD: How to assign a precise meaning to a set of SD without compromising refinement? Provides a direct technique for checking SD refinement in a compositional way. Supports the development of a general purpose MC for property and refinement checking. * March 29, 2004 -- Brown University Joint work with Scott A. Smolka Convenient way of describing interaction among reactive systems, i.e.: Systems where termination is rather an error than an expected behavior. Have become an integral part of all modern software engineering design methods: SDL and ROOM MSC (message sequence charts), UML SD (sequence diagrams). Scenario-Based Specifications Reactive Systems Commercial Aircraft Medical devices Household devices Telecommunication Nuclear Power Plants Automobiles UML 2.0 SD Simplified Syntax m n b sd ack name of SD body of SD process name process lifeline receive event send event message Positive SD: describes traces that are valid and should be possible UML 2.0 SD Simplified Syntax negative qualification Negative SD: describes traces that are invalid and should not be possible m n c neg sd nack UML 2.0 SD Simplified Syntax m n a sd init m n b sd ack m n c neg sd nack sd iod init ref ack nack ref ref High level SD (IOD) synchronous/asynchronous sequencing UML 2.0