Visual Studio 2010 is the most comprehensive suite of application development tools a software team could ever wish for. But its dazzling array of features can be daunting to say the least. Whether you’re building custom line-of-business applications or the next killer viral internet app you need to understand what’s under the hood and how your team can take advantage of its broad capabilities. Join a team of industry experts for a hands-on discussion of proven techniques for getting the most power and mileage out of this incredible product. Session 1: Drive Your Process In our first session we will examine what it takes to establish and support a world class development team using Visual Studio 2010 and Team Foundation Server 2010. We will discuss what makes a team great and how to choose a software development methodology to ensure repeatable results. We will reveal best practices to help teams perform at world class levels using Visual Studio 2010. Session 2: Drive Your Design In this session, we will take a look at role of design in modern development teams. We will discuss strategies for choosing the right level of design based on the complexity of your projects and best practices for ensuring designs are fully realized. We will also provide an overview of the new UML features provided in Visual Studio 2010 that support model driven development. Session 3: Drive Your Code In our last session, we will take a look at how it all comes together. We will walk through the process of turning requirements and designs into code and highlight the powerful tools provided in Visual Studio 2010 to help you create what you can imagine, build on the strengths of your team, and open up new possibilities. Presenters on this tour are team development expert Jeff Fattic, solutions architect MVP Kevin Grossnicklaus, and Architect Evangelist Clint Edmonson.

1. http://go.microsoft.com/?linkid=9692084

2. Today’s Sessions Session 1: Drive Your Process Session 2: Drive Your Design Session 3: Drive Your Code

3. Drive Your Process Kevin Grossnicklaus ArchitectNow Drive Your Development with Visual Studio 2010

4. Introduction Kevin Grossnicklaus ArchitectNow-www.ArchitectNow.net (2009-Present) President Washington University - CAIT Program (2003-Present) Instructor SSE - www.SSEinc.com (1999-2009) Chief Architect Software Development Practice Leader Email: kvgros@architectnow.net Twitter: http://twitter.com/kvgros Blog: http://www.GeeksWithBlogs.com/kgrossnicklaus

5. Agenda Expectations General Development Processes Setting Up a New Project VS.NET 2010/TFS 2010 Demos Resources

6. Expectations What can I expect out of this session? Where can I get more information?

7. General Development Processes

8. Software Teams Roles Project Managers Analysts Architects Developers DBA’s and Database Developers Testers Subject Matter Experts (SMEs) Various team members commonly separated by geography and time zones Many times team members are working on multiple simultaneous projects

9. Development Methodologies Methodologies define the processes followed to design, build, test, and deploy software Common options include: Agile Waterfall There are repeatable processes to writing great software

10. Development Tools Tools manage the tangible tasks to create deliverables as well as facilitate the workflow and collaboration between team members Tools should be flexible enough to be useful regardless of the methodology

11. Common ALM Tools Requirements Tracking Issue/Defect Tracking Source Control/Change Management Development/Debugging Database Design/Development Build Management Testing Reporting/Oversight Collaboration/Knowledge Sharing

12. Best Practices Clearly understood process Common tools Consistent knowledge of tools Consistent and repeatable conventions Naming Architectural UX Automated build process Continuous Integration builds Test Driven Development Clearly understood environments Test Pre-Production

13. Common Scenario:Infrastructure for a New Project

14. Getting Started: Tools Setup Select tools Install/Configure if necessary Verify connectivity of all team members to necessary tools Configure all team members in appropriate tools with appropriate permissions and workflow settings Train and support team members in use of various tools

15. Getting Started: Development Set up project structure in source control Verify developers have connectivity Set up databases and secure/expose accordingly Set up additional test environments (i.e. Test, Pre-Production, etc) Configure automated build and continuous integration processes Distribute/configure any necessary licenses to 3rd party controls Other steps?

16. Considerations New Team Members On boarding process and training Licenses Tool Upgrades Remote Access Backup/Restore Multiple Simultaneous Projects

17. Visual Studio.NET 2010 Team Foundation Server 2010

18. Visual Studio.NET 2010 .NET 4.0 Framework Releases: Current: Beta 2 (w/ Go Live license) http://msdn.microsoft.com/en-us/vstudio/dd582936.aspx Final: April 2010 3 SKUs: Ultimate Premium Professional

19. Team Foundation Server 2010 Full suite of integrated ALM capabilities Work Item Tracking Source Control Collaboration/Knowledge Sharing Project Tracking/Reporting Project Dashboards Build Management Continuous Integration Test Lab Management

20. Team Foundation Server 2010 Tightly integrated with VS.NET 2010 Built on: WSS 3.0 SQL Server 2008 SQL Server Reporting Services

21. Demos

22. ALM with TFS 2010 Tightly integrated with VS.NET 2010 Extensive team collaboration via SharePoint Manage all projects from a single point Completely automated build process Continuous Integration Gated Builds Automated unit test execution Single point of backup for all project assets Extensive reporting and query capabilities for project oversight

23. VS.NET 2010 and TFS 2010 Communication Collaboration Automation

24. Questions?

25. Resources VS.NET 2010 and TFS 2010 Beta 2Virtual Images Windows 7 Virtual PC http://www.microsoft.com/downloads/details.aspx?FamilyID=27d91e63-e33b-4cef-a331-f20d343da9de&displaylang=en Windows 2008 Hyper-V http://www.microsoft.com/downloads/details.aspx?FamilyID=426cdffc-53b5-46a5-89d3-e2ecd23570c6&displaylang=en Virtual PC 2007 http://www.microsoft.com/downloads/details.aspx?FamilyID=540777b0-cbd7-485e-bde5-23a1d4f442e0&displaylang=en

26. What’s Next? Session 1: Drive Your Process Session 2: Drive Your Design Session 3: Drive Your Code

27. Drive Your Design Drive Your Development with Visual Studio 2010 Clint Edmonson Architect Evangelist Microsoft Corporation

28. Agenda Why should we design first? What should we design? How will we design with Visual Studio 2010 Why is Microsoft investing in design tools

29. Quick show of hands Anyone using… Visio Together Altova Rational Sparx Others???

30. Why should we design first?

36. Solve Customer Problems

37. Lower Fidelity + Higher Abstraction Design before code – lower fidelity , saves time, money, and avoids mistakes Abstraction level above code Determine difficult decisions before we start building anything Communicate our thoughts to others without making them read the code

38. Demo Architecture Explorer

39. What should we design?

40. Logical & Physical Designs Logical design refers to the class and algorithmic structure of a program Physical design refers to how these classes are packaged into assemblies and deployed

41. Architectural Frameworks Krutchen’s 4+1 Views of Architecture TOGAF (The Open Group Architecture Framework) Zachman Framework

42. Architectural Frameworks Krutchen’s 4+1 Views

43. Architectural Frameworks TOGAF

44. Architectural Frameworks Zachman Framework

45. Architectural Views (TODO) As a minimum (think Agile): Layer Diagram (Logical) Use Case Diagram (Logical) Logical Class Diagram (Logical) Component Diagram (physical) Deployment Diagram (physical)

46. Design vs. Realization Should designs be tightly coupled to code? To the VS project or solution? Our approach is to use explicit designer initiated transformations

47. How will we model with Visual Studio 2010?

48. Models as… Sketch Blueprint …(TODO)

49. Our Approach

50. UML & other DSLs

51. Demo Diagram Walkthroughs

52. Why is Microsoft investing in modeling?

53. Our GoalsBroadening the Reach of Modeling Manage complexity with Visual Models Understand, manipulate and evolve applications Leverage Models across ALM

54. Questions?

55. Next Steps Download the Beta 2 (TODO) Available later this month Team blog: http://blogs.msdn.com/vsarch Stayed tuned to my blog for more… http://www.notsotrivial.net

56. What’s Next? Session 1: Drive Your Process Session 2: Drive Your Design Session 3: Drive Your Code

57. Drive Your Code Drive Your Development with Visual Studio 2010 Jeff Fattic Mid-Tier Applications Supervisor

58. Who’s Jeff and why should I listen to him? I’ve built dev and test teams from the ground up Formerly ALM Practice Manager Assisted several companies in enabling process & enabling change, adopting VSTS Microsoft Virtual Technology Specialist for Dev Tools Inner Circle Partner VSTS TAP participant Using VSTS since 2004 (2005 beta) Using VSTS 2010 for almost two years

59. Can anyone tell me what’s happened up ‘til now?

61. Business Case Development

62. Business Strategy Prioritization

64. Capacity Planning

66. Task breakdown

68. New Features in VSTS 2010 Fully supports Java shops

69. How Can I Find Out More? My Blog jeffsuperman.spaces.live.com My Email jfattic@live.com MSDN Local VSTS Users Group When Can I Get My Hands On This Stuff? Beta 2 VPC available and “go-live” today RC Coming Soon! RTM: April 12, 2010 We love feedback!

70. Questions?

71. © 2009 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.