2. DEV304 Delving into Visual Studio 2005 Team Edition for Software Architects Richard Hundhausen Senior Consultant Accentient, Inc.

3. Who am I? I'm a geek from Boise, Idaho, USA I spend my days teaching, consulting, and writing on Team System, SQL Server, and BizTalk I've co-authored books on ADO.NET, XML Web Services and Working with Visual Studio 2005 Team System (Microsoft Press) I'm a Microsoft Regional Director and Visual Studio Team System MVP

4. Prerequisites To get the most out of this presentation, I would hope that: You are familiar with Microsoft Visual Studio 2003 and Visual Studio 2005 You work with Application or Infrastructure architecture You appreciate modeling and designing You live and work in a domain-specific world!

5. Agenda Microsoft Visual Studio Team System Edition for Software Architects Distributed System Designers Implementing an Application Extending the Designers

6. Visual Studio Team System Edition for Software Architects

7. The Software Architect Role An Architect is someone who puts together the structure or structures of a system, whether it is a network, datacenter, or software system Must be an expert in the areas of maintenance, performance, compatibility, and security Visual Studio Team System identifies two architect sub-roles Infrastructure architect (IA) Application architect (AA) Both sub-types will use the Visual Studio Team System Edition for Software Architects

8. Software Architect Responsibilities Design the Logical Datacenter The IA will use the LDD Design the Application The AA will use the AD and, optionally, the SD Perform a Trial Deployment The AA will use the DD to validate the architecture(s) The AA will generate a deployment report Implement the Application The AA can kick-off development by implementing the application(s)

9. Distributed System Designers

10. Logical Datacenter Designer (LDD) Creates diagrams of interconnected servers Application Designer (AD) Allows developers and architects to define applications that will be configured into systems for deployment System Designer (SD) Composes applications into systems for reusability Deployment Designer (DD) Describes and validates a deployment of a system to a logical datacenter

11. Designing the Logical Datacenter Zones Represent boundaries, such as domains, perimeter networks, or other isolated security areas Hosts Represent the various server types on which applications will be hosted (IIS Web, database, Windows, and generic) Endpoints Represent communication gateways into or out of the hosts and zones, including both client-side and server- side

12. Logical Datacenter Designer (LDD)

13. LDD Endpoints and Server Prototypes Logical Server Prototypes WindowsClientIISWebServerDatabaseServerGenericServerZoneEndpointsWebSiteEndpointHTTPClientEndpointDatabaseClientEndpointGenericServerEndpointGenericClientEndpointZoneEndpoint

14. Settings and Constraints

15. Designing the Application Applications Represent the various Microsoft Windows, Microsoft Office system, ASP.NET Web applications, generic applications to be connected Services Represent the various ASP.NET Web service, BizTalk Web service, or external Web service to be connected Database An external database, such as SQL Server 2005 Endpoints Represent communication gateways into or out of the applications, services, and/or databases

16. Application Designer (AD)

17. Endpoints and Application Prototypes EndpointsWebServiceEndpointWebContentEndpointGenericEndpointApplicationsWindowsApplicationASP.NETWebServiceASP.NETWebApplicationOfficeApplicationExternalWebServiceExternalDatabaseBizTalkWebServiceGenericApplication

18. Defining Web Service Operations

19. Composing the Application into Systems Sometimes beneficial to group applications or services When the aggregation has some purpose or function For example: grouping three ASP.NET Web services into a "security system" Use system designer To precisely arrange the applications and services To override any settings Add a proxy endpoint to the system (optional)

20. System Designer

21. Performing a Trial Deployment Both the LDD and AD must be created first Select Define Deployment from the AD Bind applications by dragging and dropping from System View Validate the deployment diagram Resolve warnings and errors Some are immediately know because you won't be able to drop Most show up when you validate Double-click the entries in the error list

22. Deployment Designer

23. System View Window Used in System Designer Drag applications and other systems to design application systems Used in Deployment Designer Drag applications to bind them to logical servers Shows as Shows as

24. Generating a Deployment Report Once trial deployment is complete and errors have been resolved Set additional metadata Owner information, Project Files, Report options, SDM documentation What gets generated? XML document (not really human readable) HTML document (human readable, transformed using DeploymentReport.xsl)

25. Modeling an Application using the Distributed System Designers

26. Implementing an Application

27. Implementing the Application Application architects and/or developers can implement one or more of the applications on the diagram Implementing is the process of creating the Visual Studio projects (similar to File > New) Generates starter source code, content, and config files based on Visual Studio templates Implementing requires the Team Edition for Software Architects or Team Suite

28. Application Metadata Default Class Namespace LanguageProject Project Location Type (Web apps) Template

29. Post-Implementation Tasks Architecture is (hopefully) complete – ya, right! Changes in the model will be reflected in the Visual Studio Projects Example: Creating a new Web Service Project development has been kicked-off Changes to the application will be reflected in the Application Diagram (AD) Example: Adding some additional Web Methods

30. Implementing an Application

31. Extending the Designers

32. System Definition Model (SDM) SDM is Microsoft’s initial Dynamic Systems Initiative offering Provides a common language to describe the design and configuration for all aspects of a distributed system Provides familiar abstractions that make it possible for application and infrastructure architects to communicate on common ground Makes it possible for infrastructure architects to communicate application runtime, security, and connectivity requirements that result from policies defined in the deployment environment

33. SDM SDK Add new SDM resources as additional properties on any logical server or application Associate with any existing prototypes Constrainable Better than generic servers/applications Define new SDM types System definitions EndpointsRelationshipsConstraints SDM SDK is part of the Visual Studio SDK

34. SDM SDK  Architect models product in SDM definition  Developer codes any constraints  Install package is created and executed  New SDM types get installed  New SDM models are created using these types Integrated modeling experience Integrated editing experience Integrated validation experience New types persisted as SDM files

35. Visual Studio as a Modeling Platform Customers want their own custom, domain- specific, graphical designers They want to interact with familiar abstractions They want to interact with their architecture and software development processes They want to reduce costs and increase agility Building custom modeling tools is impractical They give up and just use XML Or, they put up with limited customization in UML Or, they kludge together some combination of the above

36. Domain Specific Languages Productive.NET developers require DSLs Tools that precisely target.NET development Without any abstraction or the need for tweaks Visual Studio hosts several DSLs LDD, AD, DD, SD, CD But customers want to create their own “DSL Tools” are part of the Visual Studio SDK http://msdn.microsoft.com/vstudio/dsltools

37. Design For Operations (DFO) Kit Generate work items automatically Trouble tickets Events Application faults Performance bottlenecks Unhandled/Non-instrumented errors Furthers Microsoft’s Dynamic Systems Initiative Developers and operations have clear insight into the behavior and health of production.NET applications Automatic creation of MOM 2005 Management Packs for custom applications

38. DFO Requirements Development Windows Server 2003 Service Pack 1 Visual Studio 2005 Professional Edition Deployment Team Foundation Server Microsoft Operations Manager (MOM) 2005 Team Foundation Server CAL MOM Connector Framework (MCF)

39. SDM SDK and DFO Kit

40. Summary Visual Studio Team System provides great modeling tools Visualize and validate complex systems Enables knowledge transfer Between architects and developers Between developers and operations Improve predictability of deployment Customize the modeling process SDM SDK, DSL Tools Design for Operations Integration Kit

41. Resources Technical Chats and Webcasts http://www.microsoft.com/communities/chats/default.mspx http://www.microsoft.com/usa/webcasts/default.asp Microsoft Learning and Certification http://www.microsoft.com/learning/default.mspx MSDN & TechNet http://microsoft.com/msdn http://microsoft.com/technet Virtual Labs http://www.microsoft.com/technet/traincert/virtuallab/rms.mspx Newsgroups http://communities2.microsoft.com/ communities/newsgroups/en-us/default.aspx Technical Community Sites http://www.microsoft.com/communities/default.mspx User Groups http://www.microsoft.com/communities/usergroups/default.mspx

42. Fill out a session evaluation on CommNet for a chance to Win an XBOX 360!

43. © 2006 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.