UML modeling extensibility namespaces
| Namespace | Description |
|---|---|
| Microsoft.VisualStudio.ArchitectureTools.Extensibility | The types in this namespace help you to load UML models. |
| Microsoft.VisualStudio.ArchitectureTools.Extensibility.Presentation | This namespace contains types for reading and updating UML diagrams. |
| Microsoft.VisualStudio.ArchitectureTools.Extensibility.Uml | This namespace contains extensions to the UML types. The majority of the extensions are methods for creating new instances. There are also a number of helper methods and types that make it easier to navigate and update a UML model. |
| Microsoft.VisualStudio.Uml.Actions | An action is an element in an activity. It represents a unit of behavior, can take be described with inputs and outputs. For more information about activity modeling in Visual Studio Ultimate, see UML Activity Diagrams: Guidelines. For more information about the UML API, see Extend UML models and diagrams. |
| Microsoft.VisualStudio.Uml.Activities | An activity describes the flow of control and information between different actions, which may be executed by program objects, computers, or people. For more information about activity modeling in Visual Studio Ultimate, see UML Activity Diagrams: Guidelines. For more information about the UML API, see Extend UML models and diagrams. |
| Microsoft.VisualStudio.Uml.AuxiliaryConstructs | This namespace provides an API on the UML Model, as well as methods to define and use UML template classes. For more information about UML models in Visual Studio Ultimate, see Create models for your app. For more information about template classes, see UML Class Diagrams: Guidelines. For more information about the UML API, see Extend UML models and diagrams. |
| Microsoft.VisualStudio.Uml.Classes | This namespace defines the basic modeling concepts in UML, such as IElement and IRelationship, from which all the other UML types are derived. For more information about UML models in Visual Studio Ultimate, see Create models for your app. For more information about the UML API, see Extend UML models and diagrams. |
| Microsoft.VisualStudio.Uml.CommonBehaviors | This namespace defines the core concepts of messages, operation invocation, and events. For more information about the UML API, see Extend UML models and diagrams. |
| Microsoft.VisualStudio.Uml.Components | A UML component describes a modular unit of a software system with well defined interfaces, typically designed so that it can easily be replaced or used in different combinations with other components. |
| Microsoft.VisualStudio.Uml.CompositeStructures | Composite structures are descriptions of how an instance of one type, typically IComponent, is made up of interconnected parts. For more information about component modeling in Visual Studio Ultimate, see UML Component Diagrams: Reference and UML Component Diagrams: Guidelines. For more information about the UML API, see Extend UML models and diagrams. |
| Microsoft.VisualStudio.Uml.Deployments | Deployment objects can be used to define the assignment of software artifacts to execution environments. In Visual Studio Ultimate, deployment objects are used to link artifacts to use cases. For more information, see UML Use Case Diagrams: Reference and UML Use Case Diagrams: Guidelines. For more information about the UML API, see Extend UML models and diagrams. |
| Microsoft.VisualStudio.Uml.Interactions | Interactions, which appear on sequence diagrams, can be used to represent function calls between program objects, message protocols between applications or computers, interactions between users and systems, or other sequences of interaction. |
| Microsoft.VisualStudio.Uml.Profiles | Profiles allow you to extend UML for your own purposes. For more information about UML profiles in Visual Studio Ultimate, see Customize your model with profiles and stereotypes. For more information about the UML API, see Extend UML models and diagrams. |
| Microsoft.VisualStudio.Uml.StateMachines | A state machine defines the behavior of an object or interaction in terms of a succession of states. Each event or incoming message causes a transition from one state to another. A state is a boolean condition that is true of the object or system that the state machine describes. |
| Microsoft.VisualStudio.Uml.UseCases | Use cases are a means to specify what a system is required to do. For more information about use case diagrams in Visual Studio Ultimate, see UML Use Case Diagrams: Reference and UML Use Case Diagrams: Guidelines. For more information about the UML API, see Extend UML models and diagrams. |