There might be a call message for calling an operation (performed by “Operator” another component discussed later), a message for creating an instance, message for destroying an instance and lastly for sending a signal. Message includes many activities within itself. This component dictates how 2 lifelines would interact among each other. This is pretty much analogous to conversations “Person” would have with another. The next component is “Messages”, which denotes the specific type of communication between lifelines in an interaction. Lifeline is like individual “Person” in a society. a Boolean condition, which is used for selecting a particular instance.
The last attribute is the “Selector”, which is similar to a flag option, i.e. The next attribute is “Type” which is a mandatory attribute, as it represents the name of the classifier of which this lifeline is a part of. One of them is “Name”, with which the lifeline is referred to in an interaction. There are many attributes that are possible for lifeline. Lifeline can be thought about as a smallest building block of interaction diagram or may be the role that instance would play in the interaction.
Starting off with lifeline, it denotes a single participant in an interaction. We would take some analogous instance which is very prevalent in our society, so that it becomes easier for our readers to understand the concepts faster. In this section we will go through each of these components one by one and understand deep about each component to get a clear overall picture. The main components of UML diagram are lifelines, messages, operators, state invariant and constraints.
#Interaction diagram software#
Web development, programming languages, Software testing & others Start Your Free Software Development Course
0 kommentar(er)
