Drive Your Development with Visual Studio 2010


Published on

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.

Published in: Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Photo credits: Commons Attribution License
  • Photo credits: Commons Attribution License
  • Photo credits: Commons Attribution License
  • Photo credits: Commons Attribution License
  • Photo credits: Commons Attribution License
  • Demo 2 – High Level Design (Place Order Use Case)
  • Drive Your Development with Visual Studio 2010

    1. 1.<br />
    2. 2. Today’s Sessions<br />Session 1: Drive Your Process<br />Session 2: Drive Your Design<br />Session 3: Drive Your Code<br />
    3. 3. Drive Your Process<br />Kevin Grossnicklaus<br />ArchitectNow<br />Drive Your Development with Visual Studio 2010<br />
    4. 4. Introduction<br />Kevin Grossnicklaus<br /> (2009-Present)<br />President <br />Washington University - CAIT Program (2003-Present)<br />Instructor<br />SSE - (1999-2009)<br />Chief Architect<br />Software Development Practice Leader<br />Email:<br />Twitter:<br />Blog: <br /><br />
    5. 5. Agenda<br />Expectations<br />General Development Processes<br />Setting Up a New Project<br />VS.NET 2010/TFS 2010<br />Demos<br />Resources<br />
    6. 6. Expectations<br />What can I expect out of this session?<br />Where can I get more information?<br />
    7. 7. General Development Processes<br />
    8. 8. Software Teams<br />Roles<br />Project Managers<br />Analysts <br />Architects<br />Developers<br />DBA’s and Database Developers<br />Testers<br />Subject Matter Experts (SMEs)<br />Various team members commonly separated by geography and time zones<br />Many times team members are working on multiple simultaneous projects<br />
    9. 9. Development Methodologies <br />Methodologies define the processes followed to design, build, test, and deploy software<br />Common options include:<br />Agile<br />Waterfall<br />There are repeatable processes to writing great software<br />
    10. 10. Development Tools<br />Tools manage the tangible tasks to create deliverables as well as facilitate the workflow and collaboration between team members<br />Tools should be flexible enough to be useful regardless of the methodology<br />
    11. 11. Common ALM Tools<br />Requirements Tracking<br />Issue/Defect Tracking<br />Source Control/Change Management<br />Development/Debugging<br />Database Design/Development<br />Build Management<br />Testing<br />Reporting/Oversight<br />Collaboration/Knowledge Sharing<br />
    12. 12. Best Practices<br />Clearly understood process<br />Common tools<br />Consistent knowledge of tools<br />Consistent and repeatable conventions<br />Naming<br />Architectural<br />UX<br />Automated build process<br />Continuous Integration builds<br />Test Driven Development<br />Clearly understood environments<br />Test<br />Pre-Production<br />
    13. 13. Common Scenario:Infrastructure for a New Project<br />
    14. 14. Getting Started: Tools Setup<br />Select tools<br />Install/Configure if necessary<br />Verify connectivity of all team members to necessary tools<br />Configure all team members in appropriate tools with appropriate permissions and workflow settings<br />Train and support team members in use of various tools<br />
    15. 15. Getting Started: Development<br />Set up project structure in source control<br />Verify developers have connectivity<br />Set up databases and secure/expose accordingly<br />Set up additional test environments (i.e. Test, Pre-Production, etc)<br />Configure automated build and continuous integration processes<br />Distribute/configure any necessary licenses to 3rd party controls<br />Other steps?<br />
    16. 16. Considerations<br />New Team Members<br />On boarding process and training<br />Licenses<br />Tool Upgrades<br />Remote Access<br />Backup/Restore<br />Multiple Simultaneous Projects<br />
    17. 17. Visual Studio.NET 2010 Team Foundation Server 2010<br />
    18. 18. Visual Studio.NET 2010<br />.NET 4.0 Framework<br />Releases:<br />Current: Beta 2 (w/ Go Live license)<br /><br />Final: April 2010<br />3 SKUs:<br />Ultimate<br />Premium<br />Professional<br />
    19. 19. Team Foundation Server 2010<br />Full suite of integrated ALM capabilities <br />Work Item Tracking<br />Source Control<br />Collaboration/Knowledge Sharing<br />Project Tracking/Reporting<br />Project Dashboards<br />Build Management<br />Continuous Integration <br />Test Lab Management<br />
    20. 20. Team Foundation Server 2010<br />Tightly integrated with VS.NET 2010<br />Built on:<br />WSS 3.0<br />SQL Server 2008<br />SQL Server Reporting Services<br />
    21. 21. Demos<br />
    22. 22. ALM with TFS 2010<br />Tightly integrated with VS.NET 2010<br />Extensive team collaboration via SharePoint<br />Manage all projects from a single point<br />Completely automated build process<br />Continuous Integration<br />Gated Builds<br />Automated unit test execution<br />Single point of backup for all project assets<br />Extensive reporting and query capabilities for project oversight <br />
    23. 23. VS.NET 2010 and TFS 2010<br />Communication<br />Collaboration<br />Automation<br />
    24. 24. Questions?<br />
    25. 25. Resources<br />VS.NET 2010 and TFS 2010 Beta 2Virtual Images<br />Windows 7 Virtual PC<br /><br />Windows 2008 Hyper-V<br /><br />Virtual PC 2007<br /><br />
    26. 26. What’s Next?<br />Session 1: Drive Your Process<br />Session 2: Drive Your Design<br />Session 3: Drive Your Code<br />
    27. 27. Drive Your Design<br />Drive Your Development with Visual Studio 2010<br />Clint Edmonson<br />Architect Evangelist<br />Microsoft Corporation<br />
    28. 28. Agenda<br />Why should we design first?<br />What should we design?<br />How will we design with Visual Studio 2010<br />Why is Microsoft investing in design tools<br />
    29. 29. Quick show of hands<br />Anyone using…<br />Visio<br />Together<br />Altova<br />Rational<br />Sparx<br />Others???<br />
    30. 30. Why should we design first?<br />
    31. 31.
    32. 32.
    33. 33.
    34. 34.
    35. 35.
    36. 36. Solve Customer Problems<br />
    37. 37. Lower Fidelity + Higher Abstraction<br />Design before code – lower fidelity , saves time, money, and avoids mistakes<br />Abstraction level above code<br />Determine difficult decisions before we start building anything<br />Communicate our thoughts to others without making them read the code<br />
    38. 38. Demo<br />Architecture Explorer<br />
    39. 39. What should we design?<br />
    40. 40. Logical & Physical Designs<br />Logical design refers to the class and algorithmic structure of a program<br />Physical design refers to how these classes are packaged into assemblies and deployed<br />
    41. 41. Architectural Frameworks<br />Krutchen’s 4+1 Views of Architecture<br />TOGAF <br />(The Open Group Architecture Framework)<br />Zachman Framework<br />
    42. 42. Architectural Frameworks<br />Krutchen’s 4+1 Views<br />
    43. 43. Architectural Frameworks<br />TOGAF<br />
    44. 44. Architectural Frameworks<br />Zachman Framework<br />
    45. 45. Architectural Views (TODO)<br />As a minimum (think Agile): <br />Layer Diagram (Logical)<br />Use Case Diagram (Logical)<br />Logical Class Diagram (Logical)<br />Component Diagram (physical)<br />Deployment Diagram (physical)<br />
    46. 46. Design vs. Realization<br />Should designs be tightly coupled to code? <br />To the VS project or solution?<br />Our approach is to use explicit designer initiated transformations <br />
    47. 47. How will we model with Visual Studio 2010?<br />
    48. 48. Models as…<br />Sketch<br />Blueprint<br />…(TODO)<br />
    49. 49. Our Approach<br />
    50. 50. UML & other DSLs<br />
    51. 51. Demo<br />Diagram Walkthroughs<br />
    52. 52. Why is Microsoft investing in modeling?<br />
    53. 53. Our GoalsBroadening the Reach of Modeling<br />Manage complexity with Visual Models<br />Understand, manipulate and evolve applications<br />Leverage Models across ALM<br />
    54. 54. Questions?<br />
    55. 55. Next Steps<br />Download the Beta 2<br />(TODO) Available later this month<br />Team blog:<br /><br />Stayed tuned to my blog for more…<br /><br />
    56. 56. What’s Next?<br />Session 1: Drive Your Process<br />Session 2: Drive Your Design<br />Session 3: Drive Your Code<br />
    57. 57. Drive Your Code<br />Drive Your Development with Visual Studio 2010<br />Jeff Fattic<br />Mid-Tier Applications Supervisor<br />
    58. 58. Who’s Jeff and why should I listen to him?<br />I’ve built dev and test teams from the ground up<br />Formerly ALM Practice Manager<br />Assisted several companies in enabling process & enabling change, adopting VSTS<br />Microsoft Virtual Technology Specialist for Dev Tools<br />Inner Circle Partner<br />VSTS TAP participant<br />Using VSTS since 2004 (2005 beta)<br />Using VSTS 2010 for almost two years<br />
    59. 59. Can anyone tell me what’s happened up ‘til now?<br />
    60. 60. Portfolio Management<br /><ul><li>Unified Project & Portfolio Management
    61. 61. Business Case Development
    62. 62. Business Strategy Prioritization
    63. 63. Portfolio Prioritization & Optimization</li></li></ul><li>Project Management<br /><ul><li>Team Planning
    64. 64. Capacity Planning
    65. 65. Time Tracking</li></li></ul><li>Iteration Planning<br /><ul><li>Project & Excel integration
    66. 66. Task breakdown
    67. 67. Estimation collaboration</li></li></ul><li>Now, enough talk! On to the demo…<br />
    68. 68. New Features in VSTS 2010<br />Fully supports Java shops<br />
    69. 69. How Can I Find Out More?<br />My Blog<br /><br />My Email<br /><br />MSDN<br />Local VSTS Users Group<br />When Can I Get My Hands On This Stuff?<br />Beta 2 VPC available and “go-live” today<br />RC Coming Soon!<br />RTM: April 12, 2010<br />We love feedback!<br />
    70. 70. Questions?<br />
    71. 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.<br />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.<br />