Object Oriented Software Engineering View all facts Glossary Help |
| subject > representation > coding technique > diagram > UML diagram > interaction diagram |
| interaction diagram | ||||
| subject | fact | |||
| interaction diagram | can be used to define the protocol used when two components communicate with each other | ![]() |
| can contain more or less detail depending on what you wish to communicate | ![]() | |
can show several different types of communication including:
| ![]() | |
| has definition A sequence diagram or collaboration diagram used to model the dynamic aspects of a software system | ![]() | |
| has part actor symbol | ![]() | |
| has part message symbol | ![]() | |
| has part object symbol | ![]() | |
| has purpose to better understand the sequence of messages | ![]() | |
| helps you to visualize how the system runs | ![]() | |
| is a subtopic of 5.1 - What is UML? | ![]() | |
| is a kind of UML diagram | ![]() | |
| models the dynamic aspects of a software system | ![]() | |
| should be created after developing a class diagram and a use case model because you need to know the actors and objects involved in an interaction | ![]() | |
| shows the behaviour of systems in terms of how objects interact with each other | ![]() | |
| UML diagram | describes aspects of the architectural model | ![]() |
| has part constraint | ![]() | |
| has part note | ![]() | |
| see also Unified Modelling Language | ![]() | |
| diagram | has advantages it conveys or summarizes complex concepts or mechanisms more easily than other techniques | ![]() |
| has problems | ![]() | |
| should have a label if its meaning is not obvious, using a caption or pop-up label that appears when the user moves the mouse over it | ![]() |
Kinds of interaction diagram :
Next UML diagram: package diagram Up: UML diagram Previous UML diagram: instance diagram