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

3. 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 it Who we built it for What it can do

4. 4 Complexity is found everywhere Code Tests Requirements Organizational politics (and more) Visual Studio 2010 uses visualization and models to help with Understanding existing code (and other assets) Maintaining control over software architecture Understanding the domain Why: tame complexity

5. 5 Developers who are… …trying to understand existing code …focused on the right fix …wanting to do some upfront design Architects 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. 6 Project Management Code artefacts Tasks Bugs Visualizations and models Reports Stories Discover As-Is To-Be What-If Validate Generate Update Metrics Extensible V & M Tools Platform Standards Code Tests Debug Traces Trace What: Product capabilities 4. Understand the domain LayerLayer UMLUML DSLsDSLs 4. Understand the domain LayerLayer UMLUML DSLsDSLs 5. Maintain control Generate codeGenerate code DSLsDSLs 5. Maintain control Generate codeGenerate code DSLsDSLs 3. Maintain control Create links to TFS WIsCreate links to TFS WIs 3. Maintain control Create links to TFS WIsCreate links to TFS WIs 1. Understand the code Standard Graphs + DGMLStandard Graphs + DGML Architecture explorerArchitecture explorer Sequence DiagramsSequence Diagrams Layer DependenciesLayer Dependencies Class DiagramsClass Diagrams 1. Understand the code Standard Graphs + DGMLStandard Graphs + DGML Architecture explorerArchitecture explorer Sequence DiagramsSequence Diagrams Layer DependenciesLayer Dependencies Class DiagramsClass Diagrams Concrete Abstract 2. Maintain control Validate against layer diagramsValidate against layer diagrams 2. Maintain control Validate against layer diagramsValidate against layer diagrams Trace

7. 7 Architecture explorer Standard graphs and DGML Sequence diagram generation Class diagram generation (feature pack) DEMO: Understand the code

8. 8 Layer diagram Layer validation and integration with MSBuild Work item integration DEMO: Maintain control (Layer)

9. 9 Modeling project UML designers UML explorer DEMO: Understand the domain (UML)

10. 10 Work item integration with UML Code generation (feature pack) Code gen from UML Text templates (T4) T4 orchestrator Using a Domain Specific Language (DSL) DEMO: Maintain control (UML + DSL)

11. 11 VS Extension manager and VSIX files Extending a UML designer Not shown: Creation of custom DGML Building your own Domain Specific designers using DSL Tools Linking DSLs, UML, layer and DGML together using the modelbus DEMO: Customizing the tools

12. 12 Project Management Code artefacts Tasks Bugs Visualizations and models Reports Stories Discover As-Is To-Be What-If Validate Generate Update Metrics Extensible V & M Tools Platform Standards Code Tests Debug Traces Trace Summary: Product capabilities 4. Understand the domain LayerLayer UMLUML DSLsDSLs 4. Understand the domain LayerLayer UMLUML DSLsDSLs 5. Maintain control Generate codeGenerate code DSLsDSLs 5. Maintain control Generate codeGenerate code DSLsDSLs 3. Maintain control Create links to TFS WIsCreate links to TFS WIs 3. Maintain control Create links to TFS WIsCreate links to TFS WIs 1. Understand the code Standard Graphs + DGMLStandard Graphs + DGML Architecture explorerArchitecture explorer Sequence DiagramsSequence Diagrams Layer DependenciesLayer Dependencies Class DiagramsClass Diagrams 1. Understand the code Standard Graphs + DGMLStandard Graphs + DGML Architecture explorerArchitecture explorer Sequence DiagramsSequence Diagrams Layer DependenciesLayer Dependencies Class DiagramsClass Diagrams Concrete Abstract 2. Maintain control Validate against layer diagramsValidate against layer diagrams 2. Maintain control Validate against layer diagramsValidate against layer diagrams Trace

13. 13 RC Build http://msdn.microsoft.com/en-us/vstudio/dd582936.aspx Documentation & resources Docs: http://msdn.microsoft.com/en-us/library/57b85fsc(VS.100).aspxhttp://msdn.microsoft.com/en-us/library/57b85fsc(VS.100).aspx Visualization and modeling SDK: http://code.msdn.microsoft.com/vsvmsdk http://code.msdn.microsoft.com/vsvmsdk Layer templates: http://visualstudiogallery.msdn.microsoft.com/en- us/237f823c-45b4-4f1f-b9e2-607fe66eaae7http://visualstudiogallery.msdn.microsoft.com/en- us/237f823c-45b4-4f1f-b9e2-607fe66eaae7 Blogs http ://blogs.msdn.com/cameronshttp ://blogs.msdn.com/camerons (all) http://www.lovettsoftware.comhttp://www.lovettsoftware.com (visualization, dgml) http://blogs.msdn.com/stevecookhttp://blogs.msdn.com/stevecook (uml, msft in OMG) http://www.peterprovost.org/blog/http://www.peterprovost.org/blog/ (umlX, agile) http://blogs.msdn.com/jmprieurhttp://blogs.msdn.com/jmprieur (dsl) http://blogs.msdn.com/stuart_kenthttp://blogs.msdn.com/stuart_kent (dsl, umlX - soon) Where to find more

14. © 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.