The Model Tree

The Model Tree is a standard Windows Treeview that displays one or more UML models. It shows the details of the model, using icons to represent the element types:

• Model: Represents one model file within Tablet UML.
  • Package: Represents one package within a model. Packages allow you to group your model elelements in a hierarchy, making them easier to manage and understand.
  • Use Case Diagram
    • Actor: Represents a user or external system related to the system under design. See also Editing Classifiers .
    • Use Case: Represents a task the system must perform in response to an actor's request.
    • Navigable Association: Represents a request from an actor for the system to perform a use case; or represents a request from the system for an actor to perform some task as part of a use case.
    • Association: Indicates that an actor is involved in a use case in some way.
    • Dependence: Indicates that one use case relies on another in some way.
    • Class: Represents some kind of object or information involved in a use case. See also Editing Classes and Editing Classifiers.
    •  Attribute: Represents an attribute of a classifier, such as an actor, a class, or an interface. See also Editing Attributes.
    •  Operation: Represents an operation of a classifier, such as an actor, a class, or an interface. See also Editing Operations.
    • Note: Represents some text information you want to include in a diagram.
    • Note Attachment: Attaches a note to the things it describes.
  • Activity Diagram
    • Initial State: Represents the point where the diagram begins.
    • Activity: Represents a step in the process depicted in the diagram.
    • Transition: Represents a transition from one activity or branch to another.
    • Branch/Merge: Represents a decision in the diagram; or represents a point where alternative paths come back together.
    • Final State: Represents a point where the diagram ends.
    • Object: Represents some object or information changed by or used within the diagram.
    • Object Flow: Represents information being stored in or retrieved from an object.
    • Swimlane: Represents some entitiy withing the design (perhaps a processor, a component, an actor, an interface, or a class). All activities and branches and merges that appear within the swimlane are the responsibility of the corresponding entity.
    • Fork/Join: Represents a point within the diagram where two or more parallel paths of execution begin; or represents a point where two or more parallel paths rejoin.
    • Note: Represents some text information you want to include in a diagram.
    • Note Attachment: Attaches a note to the things it describes.
  • Component Diagram
    • Component: Represents one executable or data component within your design.
    • Interface: Represents a set of services provided by and used by components. See also Editing Classifiers.
    •  Attribute: Represents an attribute of a classifier, such as an actor, a class, or an interface. See also Editing Attributes.
    •  Operation: Represents an operation of a classifier, such as an actor, a class, or an interface. See also Editing Operations.
    • Association: Indicates that a component provides an interface.
    • Dependence: Indicates that a component uses an interface.
    • Note: Represents some text information you want to include in a diagram.
    • Note Attachment: Attaches a note to the things it describes.
  • Class Diagram
    • Class: Represents a kind of information within the design, including fields that describe the information and methods that use or change the information. See also Editing Classes and Editing Classifiers
    • Interface: Represents a set of services provided by and used by classes.See also Editing Classifiers.
    •  Attribute: Represents an attribute of a classifier, such as an actor, a class, or an interface. See also Editing Attributes.
    •  Operation: Represents an operation of a classifier, such as an actor, a class, or an interface. See also Editing Operations.
    • Association: Indicates that two classes (or a class and an interface) are related and aware of each other.
    • Navigable Association: Indicates that two classes (or a class and an interface) are related, but the class pointed at is unaware of the other class.
    • Dependence: Indicates that one class is aware of another class or interface (i.e., knows how to uses its fields and methods) but isn't directly related to it.
    • Genralization (Inheritance): Indicates that one class (the class pointing) is a special case or subclass of another class (the class pointed at).
    • Realization: Indicates that a class provides an interface.
    • Note: Represents some text information you want to include in a diagram.
    • Note Attachment: Attaches a note to the things it describes.
  • Deployment Diagram
    • Processor: Represents a computer, processor, or device within the system.
    • Association: Represents a logical or physical mechanism by which two processors communicate.
    • Note: Represents some text information you want to include in a diagram.
    • Note Attachment: Attaches a note to the things it describes.
  • State Diagram
    • Initial State: Represents the point where the diagram begins.
    • State: Represents some state or condition of the system, or of some part of the system.
    • Transition: Represents a transition from one state to another.
    • Final State: Represents a point where the diagram ends.
    • Note: Represents some text information you want to include in a diagram.
    • Note Attachment: Attaches a note to the things it describes.
  • Sequence Diagram
    •  Object: Represents an object within the sequence diagram begins.
    •  Lifeline: Represents the existence of an object within the sequence diagram.
    •  Activation: Represents an object's activation within the sequence diagram.
    •  Message: Represents a message between two objects in the sequence diagram.
    • Note: Represents some text information you want to include in a diagram.
    • Note Attachment: Attaches a note to the things it describes.
  • Collaboration Diagram
    •  Object: Represents an object within the sequence diagram begins.
    •  Collaboration: Represents an allowed communication path between two objects.
    •  Message: Represents a message that passes along a collaboration.
    • Note: Represents some text information you want to include in a diagram.
    • Note Attachment: Attaches a note to the things it describes.
  • Package Diagram
    • Package: Represents one package within a model. Packages allow you to group your model elelements in a hierarchy, making them easier to manage and understand.
    • Dependence: Inidicates that elements in one package make use elements in another package (the package pointed at).
    • Note: Represents some text information you want to include in a diagram.
    • Note Attachment: Attaches a note to the things it describes.
  • Sketch Diagram

To reuse a model element from the model in a diagram, click down in it in the tree and drag it onto the diagram.

You can update the Model Tree by right-clicking on it to open the Model Tree Context Menu.

Legal Notices

For an easy, affordable UML tool, visit The Tablet UML Company.

Copyright © 2006 by Martin L. Shoemaker/The Tablet UML Company.