Interaction and Activity diagrams

In UML there are 3 groups of diagrams, Analysis domain diagrams such as usecase. Static diagrams like Class, Package and deployment, and dynamic (or Interaction) diagrams like timing, activity and sequence diagrams.

They each have strengths and weaknesses, you don't have to prepare all diagrams to fully document a system. UML is a toolbox of options not a constraining processes. Use the most appropriate, most useful diagrams only;Use those diagrams that add something when communicating the requirements, design or solution.

An activity diagram is procedural, and owes its heritage to DFD and flowcharts, It allows the logical paths to be shown/explored.

Since 'interaction diagrams' is a group of diagrams I assume you really meant Sequence Diagrams by your term 'interaction diagrams'. These show the normal program flow through a Objects over time, they are each derived from a usecase. You should normally have one path through a usecase. They should not include any conditional logic (#1).

(#1) Yes I know UML 2.0 now includes conditionals, but 1) I consider them to be popularist kludge. 3) I've seen them used to often to justify using associated classes to breaking delegation ad encapsulation. 2) Refuse to use or advocate them on the ground of objective purity :)

MartinS.a at 2007-7-15 21:13:34 >