UML 2.0 Profile Support

Together allows you to model diagrams using the UML 2.0 features. By default, Together uses the UML 1.4 specification for modeling diagrams. To enable UML 2.0 support, see Enabling UML Profiles.

The list below lists the additional features that have been added to the standard UML diagrams with respect to the UML 2.0 specification:

Use Case Diagram

• Subject: Formerly known as the system boundary element. Use the subject element to group use case elements.
• Specialize Link: A specialize link allows you to show that a use case may be specialized by another use case.
• Performance Link: The performance link allows you to model many to many relationships between an actor and a use case.
• Use Case Collaboration: A use case collaboration represents a conceptual modeling element to define ownership of subjects, use cases, and actors.

Sequence Diagram

• Frames: The sequence diagram is surrounded by a rectangular interaction frame. The interaction name shows in a compartment in the upper left-hand corner of the frame. In a sequence diagram, "sd" precedes the interaction name.
• Interaction Occurrences: Use the interaction occurrence to reuse interaction definitions.

Collaboration Diagram

• Frames: The communication diagram is surrounded by a rectangular interaction frame. The interaction name shows in a compartment in the upper left-hand corner of the frame. In a communication diagram, "cd" precedes the interaction name.
• Interaction Occurrence: Use the interaction occurrence to reuse interaction definitions.
• Lifeline: Interaction occurrences cover lifelines. You can associate a sequence of events by using a lifeline.
• Uses Link: Use this link between interaction occurrences and lifelines or between two lifelines. The "uses" stereotype displays above the link on the diagram.
• InterLifelineConnector: Use the InterLifelineConnector to show connections between lifelines. These connectors are associated with number messages that indicate its direction.

Collaboration2.0 Diagram

• Part: Use a part to represent a set of instances specified by a class or interface.
• Port: Use a port to specify a unique communication point between a class or interface and its environment.
• Collaboration: Use a collaboration to define a set of cooperating parts that are needed for a given task.
• Collaboration Occurrence: Use a collaboration occurrence to explain the relationships between the parts of a class or interface or to specify how a collaboration represents a class or interface.

State Diagram

• Initial State: Formerly known as the start state element. Use to indicate the initial state in a state diagram.
• Final State: Formerly known as the end state element. Use to indicate the final state in a state diagram.

Activity Diagram

• Activity Invocation: This is the new name for the activity element. It has an additional property called multiplicity.
• Fork/Join nodes: The fork/join nodes have been replaced with synchronization bars.
• Initial Node: Formerly known as the start state element. Use initial node to indicate the initial state in an activity diagram.
• Activity Final: Formerly known as the end state element. Use activity final to indicate the final state in an activity diagram.
• Flow Final: Use the flow final element from a decision element. Designates either the termination or merge of a flow.
• Activity Partition: This is the new name for the swimlane element.
• Signal: Signal sending and receipt elements have been removed from the toolbar. To designate a signal sending element, drop an object onto the diagram, and set the stereotype property as "Signal" through the Properties view of the object.
• Time Signal: A stereotype property for an object. To designate a time signal element, drop an object onto the diagram, and set the stereotype property as "Time Signal" through the Properties view of the object.
• Multiplicity: Set the multiplicity of an activity element through its Properties view. Multiplicity displays in the upper right-hand corner of the activity.
• Control Flow Link: Formerly known as the transition link. Use the control flow link between state elements on an activity diagram.
• Synchronous and Asynchronous input/output: Specify as text on flow links, for example, {sync} or {async}.
• Interruptible Activity Region: Use this type of grouping to encapsulate activity and decision elements that constitute loops in a process.
• Iteration Activity Group: Use an iteration group to set apart a loop in the flow of an activity.
• Interrupting Edge: Use an interrupting edge to show a non-local termination of flow.

Component Diagram

• Artifact: Use an artifact to represent physical pieces of the system, for example, a design model or source code files.
• Component: The component shape has changed, and now displays as a plain rectangle with the component icon in the upper right-hand corner.

Deployment Diagram

• Component: Uses the new component element shape as described in the Component Diagram section above.