Improving Software Development Across the Lifecycle with Microsoft Visual Studio 2010 - Dave Mendlen

Dave MendlenSenior Director, Developer

Improving Software DevelopmentAcross the Lifecycle with Microsoft® Visual Studio ® 2010

All happy families are alike; each unhappy family is unique in its own way.-Leo Tolstoy, Anna Karenina

Signs Of Unhappiness

− Loose development practices − Underestimating − ‘No Repro’ bugs − Implementation doesn’t match design − And more…

How much ‘happier’ would you be if…−Quickly understand existing systems?

−You could ensure implementation matched design?

−You could eliminate Dev/Test Ping-Pong?

−You could quickly find the root cause of bugs?

−Had visibility into your projects?

Introducing Visual Studio 2010

Staying Current

Across the Board Innovation

Multi Monitor SupportZoom-able Coding Surface

Partial String IntelliSenseHTML Snippets

One Click Deployment

Generate from usage

Visual Studio Extension Manager

Call Hierarchy

Navigate-To

Refined Multi-targeting

Highlight References

Box Selection

Low impact IntelliSense Mode

New Help Experience

Drag-and-drop Data-binding

Customizable Start Page

Breakpoint Labeling

Breakpoint exporting

Hide selection

Streamline Process

Understand Existing Systems

Eliminate Bugs

UNDERSTAND EXISTING

SYSTEMS

Understanding What You Have

Could one change break something unrelated?

How much faster you could learn a new system if you could visualize it?

Architectural Exploration

−Visualize code and assets.

−Identify upstream and downstream dependencies.

−Generate a Sequence Diagram.

Control Complexity

− Code has a tendency to "go bad" as time passes.

− How can you ensure architectural integrity?

Layer Diagram

− Define and communicate design intent.

− Associate assets with layer elements.

− Validate implementation against diagram.

Architectural Exploration

demo

ELIMINATE BUGS

Five Steps to Any Process

Queue Setup Run Wait Move

Five Steps to Fixing A Bug

Queue

• Tester files bug.

Setup

• Developer searches for the source of the defect.

Run

• Developer fixes bug.

Wait

• Bug is assigned to tester.

Move

• Code is moved to test environment.

Microsoft® Test Manager 2010

−Create test cases for requirements.

−Plan & execute test runs.

−File bugs & track results.

Actionable Bug

−Enables immediate action.−Contains:

−Steps to Reproduce−System Information−Screenshots & Video

Capture−IntelliTrace

IntelliTrace

−Historical record of code execution.

−Like a DVR for debugging.−Examine actual code

execution.

IntelliTrace

demo

STREAMLINE PROCESS

Risk comes from not knowing what you’re

doing.” - Warren Buffet

Can You Answer?

Are we going to deliver a quality project on time?

What do I need to know now to

course correct?

What ‘fires’ will we have to put out

that we don’t know about?

What can I do to reduce the risk?

Poor Visibility == Failure

−Visibility reduces risk, identifies issues.

−What if you could see through the fog?

Out-of-the-Box Agile Support

− Improved Agile process template.

− Baked-in best practices.− Agile Workbooks.

− Product Backlog− Iteration Backlog

Simplified Reporting

− Improved Reports using SQL Server Reporting Services.− Detailed and thorough

− Workbook queries with Microsoft Office Excel.− Fast and flexible

SharePoint Dashboards

−Improved SharePoint integration

−Powerful dashboards−Ensures transparency

for all stakeholders

Simplified Reporting & SharePoint Dashboards

demo

Architecture

BuildTestRequirementsProcess

VS 2010 ALM Partners

DOORS®

SimShipping – Plan to support VS 2010 by end May 2010

Streamline Process

Understand Existing Systems

Eliminate Bugs

Q&A

© 2009 Microsoft Corporation. All rights reserved. Microsoft, Visual Studio, the Visual Studio logo, and [list other trademarks referenced] are trademarks of the Microsoft group of companies.

 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.