This package contains diagrams:
Activity diagram features are presented by three diagrams:
Data Activity diagram demonstrates object flow via actions and pins, and the usage of central buffer.
Final Nodes diagram represents a process of building an application, using multiple control flows and terminal blocks. During the process the application components should be assembled. If there are no more components to be built, the building flow is terminated (Flow Final), while the installation flow goes on working. If all the components are built and installed, the Deliver action is performed, and thus the whole activity is terminated (Activity Final).
Process Order demonstrates the usage of interaction of the various actions by means of the control flows, transferring information via object flows, and the usage of signal send and receive elements.
State Machine diagram features are presented by two diagrams:
Course Attempt demonstrates the usage of substates and regions. Since the states cannot have children of the same type, the nested substates are inserted into the regions.
Submachine State shows how one can refer to a different diagram from a state. In the case ReadAmountSM is a standalone state that represents a whole diagram, and ReadAmount:ReadAmountSM is a state that implements the behavior of ReadAmountSM. Both states are hyperlinked.
Use Case diagram is represented by Main Use Cases, which demonstrates the usage of subjects and stereotypes links.
Interaction diagrams show interaction between objects represented by their lifelines, by ways of messages. Each lifeline instantiates a class or represents a part. An interaction can be shown in two ways: as a sequence diagram or as a communication diagram. The sample interaction ShowAlbumsDialog is represented by the ShowAlbumsDialog diagram (sequence) and cd_ShowAlbumsDialog diagram (communication).
Copyright(C) 2008 CodeGear(TM). All Rights Reserved.
What do you think about this topic? Send feedback!