Index[SYMBOL] [A] [B] [C] [D] [E] [F] [G] [H] [I] [J] [K] [L] [M] [N] [O] [P] [R] [S] [T] [U] [V] [W] scalability of UML self-transition send signals Sequence diagram 2nd activation bars in compared to Communication diagram 2nd creating from use case creating Timing diagram from events in fragments in in logical view incorporating into Interaction Overview diagram messages (signals) in participants in 2nd time in when to create 2nd 3rd 4th when to use sequence fragments shall requirements should requirements signals between participants between transitions starting an activity Singleton design pattern sketch, UML used as software code as artifact in Deployment diagram as modeling language nodes hosting package dependencies and packages used in reuse of <<include>> relationships for components for generalization for states in UML model as detailed as software development process methods of UML as part of source state standard for UML standard profiles 2nd standard stereotypes State Machine diagram 2nd final state of guards in in logical view initial pseudostate of pseudostates in 2nd states in transition-oriented view of transitions in triggers in when not to use when to use 2nd states 2nd active and inactive composite states in software internal behavior of internal transitions of notation for regions of source state substates target state static classes or class elements <<utility>> stereotype <<subsystem>> stereotype <<source>> stereotype <<service>> stereotype <<library>> stereotype <<file>> stereotype <<executable>> stereotype <<component>> stereotype <<subsystem>> stereotype <<artifact>> stereotype <<realizations>> stereotype <<import>> stereotype <<access>> stereotype <<device>> stereotype <<artifact>> stereotype <<manifest>> stereotype <<deploy>> stereotype <<device>> stereotype <<executionEnvironment>> stereotype <<deployment spec>> stereotype <<apply>> stereotype stereotypes creating new stereotypes for interfaces 2nd icons associated with in profiles notation for 2nd 3rd profiles for standard, list of tagged values for substates subsystems synchronous messages system boundaries system clock, as tricky actor system requirements associated with use case defining shall requirements should requirements |