Across
- 2. isplays the structural relationship of components of a software system
- 5. Represent the behavior of objects in a given time frame
- 7. Sometimes referred as Instance diagrams and very similar to class diagrams.
- 9. Describes the behavior of objects that act different according to the state they are at the moment.
- 10. Shows how object interact with each other and the order those interactions occur
- 11. Main building block of any object oriented solution.
Down
- 1. Focuse on messages passed between objects
- 3. Shows the hardware of your system and the software in those hardware
- 4. Shows the dependencies between different packages in a system
- 6. represent workflows in an graphical way.
- 8. Gives a graphic overview of the actors involved in a system, different functions needed by those actors.