Stuart Kent Architect Visual Studio, Microsoft Modelling and Visualisation in Visual Studio 2010

Stuart KentArchitectVisual Studio, Microsoft

Modelling and Visualisation in Visual Studio 2010

3

By the end of this talk, you should…

…understand the following about the Visualization and Architecture tools in Visual Studio 2010

Why we built itWho we built it forWhat it can do

4

Complexity is found everywhereCodeTestsRequirementsOrganizational politics(and more)

Visual Studio 2010 uses visualization and models to help with

Understanding existing code (and other assets)Maintaining control over software architectureUnderstanding the domain

Why: tame complexity

5

Developers who are……trying to understand existing code…focused on the right fix…wanting to do some upfront designArchitects who are……trying to understand the domain…trying to understand architecture of existing assets…keen to keep the architecture clean…wanting to adapt and customize the toolset to specific needs of the organization

Who: Developers and architects

6

Project ManagementCode artefacts

Tasks

Bugs

Visualizations and models

Reports

Stories

DiscoverAs-Is

To-BeWhat-If

Validate

GenerateUpdate

Metrics

ExtensibleV & M Tools

PlatformStandards

Code

Tests

Debug Traces

Trace

What: Product capabilities

4. Understand the domain• Layer• UML• DSLs

5. Maintain control• Generate

code• DSLs

3. Maintain control• Create links to

TFS WIs

1. Understand the code• Standard Graphs +

DGML• Architecture explorer• Sequence Diagrams• Layer Dependencies• Class Diagrams

Concrete

Abstract

2. Maintain control• Validate against

layer diagrams Trace

7

Architecture explorerStandard graphs and DGMLSequence diagram generationClass diagram generation (feature pack)

DEMO: Understand the code

8

Layer diagramLayer validation and integration with MSBuildWork item integration

DEMO: Maintain control (Layer)

9

Modeling projectUML designersUML explorer

DEMO: Understand the domain (UML)

10

Work item integration with UMLCode generation (feature pack)

Code gen from UMLText templates (T4)T4 orchestrator

Using a Domain Specific Language (DSL)

DEMO: Maintain control (UML + DSL)

11

VS Extension manager and VSIX filesExtending a UML designerNot shown:

Creation of custom DGMLBuilding your own Domain Specific designers using DSL ToolsLinking DSLs, UML, layer and DGML together using the modelbus

DEMO: Customizing the tools

12

Project ManagementCode artefacts

Tasks

Bugs

Visualizations and models

Reports

Stories

DiscoverAs-Is

To-BeWhat-If

Validate

GenerateUpdate

Metrics

ExtensibleV & M Tools

PlatformStandards

Code

Tests

Debug Traces

Trace

Summary: Product capabilities

4. Understand the domain• Layer• UML• DSLs

5. Maintain control• Generate

code• DSLs

3. Maintain control• Create links to

TFS WIs

1. Understand the code• Standard Graphs +

DGML• Architecture explorer• Sequence Diagrams• Layer Dependencies• Class Diagrams

Concrete

Abstract

2. Maintain control• Validate against

layer diagrams Trace

13

RC Buildhttp://msdn.microsoft.com/en-us/vstudio/dd582936.aspx

Documentation & resourcesDocs: http://msdn.microsoft.com/en-us/library/57b85fsc(VS.100).aspxVisualization and modeling SDK: http://code.msdn.microsoft.com/vsvmsdkLayer templates: http://visualstudiogallery.msdn.microsoft.com/en-us/237f823c-45b4-4f1f-b9e2-607fe66eaae7

Blogshttp://blogs.msdn.com/camerons (all)http://www.lovettsoftware.com (visualization, dgml)http://blogs.msdn.com/stevecook (uml, msft in OMG)http://www.peterprovost.org/blog/ (umlX, agile)http://blogs.msdn.com/jmprieur (dsl)http://blogs.msdn.com/stuart_kent (dsl, umlX - soon)

Where to find more

© 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED

OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.