Reading Models and Diagrams in Other Visual Studio Products
When you open a model in Microsoft Visual Studio Premium, the model opens in read-only mode. In this mode, you can change the layout of the diagrams, but you cannot change the model.
To read a UML diagram or a layer diagram, you must first use Visual Studio to open the modeling project, and then open the diagram within it.
For this reason, if you want to read a UML diagram or Layer diagram, you must also have access to the modeling project in which it was created. You can do this either by accessing the project from Team Foundation version control, or by obtaining a copy of the project files.
This does not apply to sequence diagrams that have been generated from program code, directed graphs, and .NET class diagrams generated from code. Those diagrams can be viewed independently of a project.
To read a UML diagram or a Layer diagram, the minimum set of files that you need is as follows:
The two diagram files for the diagram that you want to read, for example, MyDiagram.classdiagram and MyDiagram.classdiagram.layout.
For Layer diagrams, you should also have the file that is named MyDiagram.layerdiagram.suppressions.
The modeling project file (MyModel.modelproj)
The root model file (ModelDefinition\MyModel.uml)
The package files for any package referenced in the diagram (ModelDefinition\MyPackage.uml)
If you open a model and its diagrams in Visual Studio Premium, you cannot change the model. That is, you cannot change the elements and relationships that are displayed on the diagrams or in model explorer. However, you can make some changes to the layout of the diagrams:
Rearrange the shapes and connectors on the diagram.
Expand and collapse shapes.
You can save these changes. If you want to make your changes visible to other users, you must at least send the updated .layout files.
A layer diagram shows the structure of an existing or proposed architecture. When code is written, it can be automatically validated against a layer diagram.
An activity diagram shows a flow of work, either in a business process or in software.
A class diagram shows types and relationships used in many contexts such as code, database schemas, communications protocols, or the glossary of terms used to describe a business domain.
A component diagram shows separable parts in a software design, and their interfaces.
A sequence diagram shows interactions between elements in a software design. A sequence diagram can be drawn manually, or it can be generated from code. If it was generated, it can be changed to propose a new design.
A use case diagram shows the users of a system and the activities that they can perform to achieve specific goals.