Answer 1

In Visual Studio 2010 ultimate, you can use UML component diagrams, Layer diagrams or dependency graphs. UML component diagrams will be familiar to most developers, but have to be created manually. Layer diagrams help you enforce assembly relationships, but don't show the individual assemblies. Dependency graphs are simple blocks and arrows, but can be generated automatically from your projects and assemblies.

Hope this helps,

Answer 2

In Visual Studio Ultimate, you can describe the structure of an application at a high level and verify that the code conforms to this high-level design by using layer diagrams. To ensure that the code stays consistent with the design, you can include layer validation as part of the build process.

Like a traditional architecture diagram, a layer diagram identifies the major components or functional units of the design and their interdependencies. Each node on the diagram, called a layer, represents a logical group of namespaces, projects, or other artifacts. You can draw the dependencies that should exist in your design. Unlike a traditional architecture diagram, you can verify that the actual dependencies in the source code conform to the intended dependencies that you have specified. By making validation part of a regular build on Team Foundation Server, you can ensure that the program code continues to adhere to the system's architecture through future changes.

Define Layers to Represent Functional Areas or Components

Layers represent logical groups of artifacts, such as projects, code files, namespaces, classes, and methods. You can create layers from artifacts in your Visual Studio solution, or you can attach specifications or plans to a layer by linking documents, such as Word files or PowerPoint presentations. Each layer appears as a rectangle on the diagram and shows the number of artifacts that are linked to it. A layer can contain nested layers that describe more granular tasks.

As a general guideline, name layers according to their function, for example, "Presentation" or "Services". If the artifacts are closely interdependent, place them in the same layer. If the artifacts can be updated separately or used in separate applications, place them in different layers. To learn about layering patterns, visit the Patterns & Practices site at http://go.microsoft.com/fwlink/?LinkId=145794.

vedio: http://channel9.msdn.com/posts/clinted/UML-with-VS-2010-Part-5-Architecting-an-Application/

Application Architecture Guide Layer DiagramsFree

http://visualstudiogallery.msdn.microsoft.com/en-us/237f823c-45b4-4f1f-b9e2-607fe66eaae7

Non-trivial matters of interest to software architects and other like minded geeks.

http://www.notsotrivial.net/blog/

Visual Studio Visualization and Modeling Tools - Team blog:

http://blogs.msdn.com/b/vsarch/

http://blogs.msdn.com/b/somasegar/archive/2009/08/29/architecture-tools-in-vsts-2010.aspx

http://blogs.msdn.com/b/camerons/archive/2010/06/18/layer-diagram-extension-using-the-feature-pack.aspx

 Visual Studio 2010 Architecture Tooling Guidance

http://vsarchitectureguide.codeplex.com/

http://blogs.msdn.com/b/camerons/archive/2010/06/26/architecture-guidance-now-available.aspx

Answer 3

Answer 4

Hi Chris,

Thanks for providing the above link!

I like the videos about Dependency graph and the Architecture Explorer.

Answer 5