3. Activity diagram

As an example of a design model derived from application requirements, we take the activity diagram. We'll start by recalling its main characteristics, which have evolved considerably in UML version 2.0. As such a diagram can model an algorithm, we propose to integrate behavioral semantics into each of these modeling elements. However, the properties of these semantics must be injected at the level of the UML metamodel. For this reason, we recall its main characteristics. We can then show how such a diagram can be transformed into an "L" language program model, after the designer has completed the missing programming elements. Having defined the behavioral properties of the language, designers can check certain behavior at the level of the activity diagram, and the behavior at the level of the "L" language code model. However, we show how such a transformation can be verified against the...