active passive objects sequence diagram uml

Behavior: Figure 7.9 presents a UML sequence diagram for an example of the Actuator-Sensor Pattern. It is actually how is class inheritance implemented in some languages so the scenario is not completely 'made-up'. A sequence diagram is a form of interaction diagram which shows objects as lifelines running down the page, with their interactions over time represented as messages drawn as arrows from the source lifeline to the target lifeline. The active state of an object indicates the current. I drew the abstract class as implicit friend object sharing the lifetime (and most of the memory) with the concrete class instance. Model high-level interaction between active objects in a system. Then UML Sequence Diagram capturing what happens withing the Program.Main might look like this: UML Sequence Diagrams are interaction diagrams that detail how operations are carried. A UML Sequence diagram shows how messages go back and forth between objects over time. You can show any > (including >) in the lifeline head as in this example: : UML Sequence Diagrams Examples → Submit Comments to Pluckįor example, let's suppose we have this (useless) C# code: abstract class BaseClassĬonsole.WriteLine('Something useful done.') Ĭonsole.WriteLine('Hi active objects are added in architectural design to organize passive objects. I say parts instead of objects because in UML 2, the life lines in sequence diagrams correspond to parts, not to individual instances and are therefore not underlined.

If you want to model two different classes then in the Sequence Diagram it would mean two different lifelines. Yes, it is common practice to let an actor send messages directly to parts of the system, not to the system as a whole.

Active passive objects sequence diagram uml