| activity diagram | Describes the flow of control from one activity to the next. |
| class diagram | Depicts the static structure of a system. This includes entities that exist (such as classes and types) and their internal structure. |
| collaboration diagram | Shows the sequential relationship of objects and their links. Together supports collaboration diagrams for both UML 1.4 and 2.0. |
| component diagram | Depicts the physical architecture of a computer-based system. |
| deployment diagram | Models the physical aspects of a computer system, including both hardware and software. |
| GoF | Gang of Four. The four authors of the book Design Patterns: Erich Gamma, Richard Helm, Ralph Johnson, and John Vlissides. |
| hyperlink | Enables you to add additional information, documentation and further links between elements in a diagram. You can navigate hyperlinks to view attachments. |
|
inplace editing |
Ability to double click on a label of a diagram element and enter or edit a name. |
| interaction diagram | See collaboration diagram or sequence diagram. |
|
layout |
The option to depict a diagram according to the default style, or vertical or horizontal hierarchy. |
| LiveSource™ | A central feature of Together products describing the synchronization between a diagram and source code. |
| package diagram | A class diagram that models packages. Package diagrams contain icons for each physical subpackage under the project directory. |
| problem detection | A group of audits specific to Together that are based on a group of metrics. |
| profiles |
Determine which specifications apply to modeling diagrams. By default, Together uses UML 1.4. Other available profiles include: - UML Profile for Modeling in Color |
| sequence diagram | Models the dynamic aspects of a system or subsystem. Depicts one or multiple sequences of messages. Along with the collaboration diagram, a type of "interaction diagram." |
|
shortcut
|
An element created elsewhere that can be placed as a shortcut on a diagram. For example, you can create a class diagram comprised of different classes from different packages. |
| state diagram | Models state machines. A state is a condition during the life of an object (or interaction) during which it satisfies a condition, performs an action, or waits for an event. |
| Together Modeling Perspective | A modeling perspective specific to Together that consists of the Navigator, Patterns Recognizer, Properties, and Editor views. |
| UML Documentation Generator | Produces HTML-navigable documents of a project and its subsections. |
| use case diagram | Describes the external view of a system and its interactions with the outside world. Uses actors to represent customers of the system's functionality. |
| XMI |
XML Metadata Interchange, a standard for porting models between tools.
|