The strength of UML is that you only have te understand 3 modeltypes. The same models are used for stepwise refinement of requirements all the way down the system development process.

Within the workshops the accent is on making a UML class diagram. Use case scenario's s are used to make UML sequence diagrams en UML sequence diagrams are used to complete class diagrams. Not only completion of data attributes, also completion of assigned functionality. 

The third UML modeltype is a state transition diagram. Such a diagram models state dependent behavior of an instance of a class, that's an object. An example is the state transition of a proposal object to a contract, where the behavior changes from "sales behavior" to "delivery behavior".

Upon completion of the workshop, the partipant:

• understands how to make a UML class diagram
• understands how to make a UML sequence diagram
• understands how to make a UML state transition diagram
• understands how to identify relevant objects
• understands how a use case step can be worked out with a UML sequence diagram
• understands how a UML class diagram can be erriched with additional data atributes and functions
• understands how a UML class diagram evolves gradually to a detailed system specification