Visual Studio Whidbey

1
(No Transcript)
2
The Visual Studio Vision

• Build the right product for customers

• Reduce development complexity

• Improve software team communication

• Foster a vibrant partner ecosystem

3
Visual Studio 2005Personalized productivity
4
The Software LifecycleWhat Weve Heard

• Building software today is very difficult
• My team is spread out and specialized
• Tools today dont work well together
• I need to be able to predict the success of my
  projects
• My organization needs customizable process
  guidance

5
Silos in the IT Lifecycle
6
Development Teams
7
Communication Barriers

• Pockets of information within disciplines
• Unclear delineation of responsibilities
• Conflicting best practices and architectures
• Conflicting strategic goals and objectives

8
Core Tenets to Success

• Tools need to
• reduce the complexity of delivering modern
  service-oriented solutions
• be tightly integrated and facilitate better team
  collaboration
• enable customization and extensibility by
  organizations and ISVs

9
Expanding Visual Studio
10
(No Transcript)
11
Visual Studio Team System
Visual Studio Team EditionSoftware Architects
Visual Studio Team EditionSoftware Developers
Visual Studio Team EditionSoftware Testers
Visual StudioTeam Foundation Server
12
Visual Studio Team System
Visual Studio Team EditionSoftware Architects
Visual Studio Team EditionSoftware Developers
Visual Studio Team EditionSoftware Testers
Visual StudioTeam Foundation Server
13
Team Edition (Architects)

• Application Designer
• Whiteboard mode for application design
• Validation against logical infrastructure
• Visualize relationships of distributed systems
• Logical Datacenter Designer
• Settings and constraints editor
• SDM generation and compiler
• System Designer and Deployment Designer
• Binds application design to datacenter design
• Enables creation of composable systems

14
Team Edition (Architects)Problem Space

• Customers have communication problems between
• Architects and Developers
• Developers do not work within architectural
  guidelines
• Development and Operations
• Deployment problems caught too late
• Customers recognize value of modeling tools
• Visualization of designs
• Higher level abstractions simply design and
  development
• Generation of code and other artifacts can
  improve productivity
• Modeling tools have poor history of success
• Positive good for documentation
• Negative CASE baggage, round-tripping
  complexities, not used for software development

15
Team Edition (Architects)

• Key scenarios
• Design connected systems
• Design for Operations
• Code visualization
• Documentation and conceptual drawings
• UML and more
• UML tools for software documentation (Visio for
  Enterprise Architects)
• DSLs tools for precise software development

• DSL tools
• Distributed Systems Designers
• Application Designer
• System Designer
• Logical Datacenter Designer
• Deployment Designer
• Class Designer
• Common Features
• Multiple artifact generation
• Continuous synchronization
• Design-first mode
• SDM schema underlies Distributed System Designers

16
Application Designer
Service-OrientedArchitecture model
Port Details editor
17
Logical Infrastructure Designer
Services assignedto logical infrastructure
Architecture validatedagainst operationalsetting
s and constraints
18
Class Designer
Class Designerandtwo-way code synch
19
Team Edition (Architects)V2 Roadmap

• Support for Indigo service framework
• Contract Designer
• Business Process Designer

20
Team Edition (Architects)Partner Opportunities

• Designer extensibility
• Extend SDM schema
• Add constraints
• Build new designers using MDF framework
• Tool-building tools
• Plan to make available post-Whidbey

21
Visual Studio Team System
Visual Studio Team EditionSoftware Architects
Visual Studio Team EditionSoftware Developers
Visual Studio Team EditionSoftware Testers
Visual StudioTeam Foundation Server
22
Team Edition (Developers)

• Static code analysis
• Support for managed and native code
• Code profiling
• Sequence view examines running threads
• GC view of object allocation and lifetime
• Caller-callee, callstack, and function views
• Code coverage
• Integrated unit testing and framework

23
Team Edition (Developers)Problem Space

• Customers lack predictability and productivity in
  the lifecycle of their applications
• Customers are forced to context switch between
  coding and lifecycle and other engineering
  activities
• Customers are forced to use multiple tools
• Customers are forced to enter project-specific
  data many different times in many different
  places
• Customers want to avoid defects
• Defects are caught late, sometimes too late for
  action

24
Team Edition (Developers)

• The Tools the Microsoft Uses
• Features
• Static code analysis
• Support for managed and native code
• PREfast used in Trustworthy Computing Code
  Reviews
• FxCop used to develop .NET framework
• Code profiling
• Based on two internal profilers
• Instrumented IceCAP, used by Windows Base and
  SQL Server
• Sampling LOP, used throughout MX, including
  Xbox
• Includes ETW events
• Sequence view examines running threads
• GC view of object allocation and lifetime
• Caller-callee, callstack, and function views
• Code coverage
• Basic Block Coverage
• Based on the BBCover technology that Windows
  Visual Studio use
• Application Verifier

25
Static Code Analysis
Static Code Analyzer
26
Code Coverage
Code Coverage
27
Unit Testing
Integrated Unit Testing
28
Team Edition (Developers)V2 Roadmap

• Runtime Analysis
• System level profiling and application monitoring
• Integration of runtime analysis with operations
• Static Analysis
• Editor integration (Squigglies)
• More rules targets

29
Visual Studio Team System
Visual Studio Team EditionSoftware Architects
Visual Studio Team EditionSoftware Developers
Visual Studio Team EditionSoftware Testers
Visual StudioTeam Foundation Server
30
Team Edition (Testers)

• Load testing
• Web services load testing via protocol-based
  script
• Load patterns constant, step, custom
• Perf counter collection and threshold monitoring
• Test case management
• Application Verifier

31
Team Edition (Testers)Problem Space

• Poorly written applications reflect poorly on the
  platform
• Testers are underserved and second class in
  Microsofts tools
• Testing tools products lag behind Visual Studio
• Little integrated support for developer testing
  defects are caught late, sometimes too late for
  action
• Testing is not integrated into the lifecycle
• Developer Tools and Testing Tools vendors are
  rarely the same
• Testing is isolated from development by processes
  and tools
• There is no common vocabulary or view of data for
  rich analytics

32
Team Edition (Testers)

• Testing is 1st class in Visual Studio
• Tests are Source Code
• Test Authoring Execution Environment
• Test View
• Test Explorer (Test Case Management UI)
• Load testing
• Web services load testing via protocol-based
  script
• Load patterns constant, step, custom
• Perf counter collection and threshold monitoring
• Unit Testing
• Similar to NUnit

33
Load Testing Creation
Load Testing Web recorder
34
Load Testing
Load Testing
Perf Counter integrationand monitoring
35
Test Case Management
Test Case Management
36
Team Edition (Testers)V2 Roadmap

• Functional UI testing
• For Avalon, Windows.Forms, Win32, and IE
• Test Lab management
• Setup, tear down, distribution, and baselining
• Historical code coverage trends on a per-method
  basis
• Test case prioritization

37
Visual Studio Team System
Visual Studio Team EditionSoftware Architects
Visual Studio Team EditionSoftware Developers
Visual Studio Team EditionSoftware Testers
Visual StudioTeam Foundation Server
38
Team Foundation Server

• Portfolio creation and navigation
• Project Creation Wizard
• Process editor for customized guidance
• Project management
• Microsoft Project and Excel integration
• Change management
• Branching, changesets, shelving
• Migration from ClearCase and VSS
• Reporting and analytics
• Project portal

39
Team Foundation ServerProblem Space

• Fragmented information
• Cant relate and query work items, work,
  processes and artifacts
• Tools sets are incomplete or poorly integrated
• Difficulty integrating tools with existing
  infrastructure
• Communication is manual
• People use the phone or face-to-face
• Information is not captured
• Distributed development aggravates the problem
• Life cycle tools are expensive and complex
• Tools are difficult to learn and use
• Developers view tools as overhead
• Administration costs are high

40
Team Foundation ServerTodays problems, our
solutions

• Fragmented information
• Communication is manual
• Life cycle tools are expensive and complex

• Integrated Information
• Automated Data Capture
• Complete Lifecycle Toolset
• Common Linking Service
• Extensible Team Foundation SDK with web service
  based APIs
• Stream-lined communication
• Common Project Portal
• Cross Tool Queries and Reports
• Common Notification Service
• Access over the internet
• Easy to use and cost effective
• Deep UI integration with familiar tools
• Developer-centric capabilities
• Easy to setup and administer

41
Team Foundation ServerCapabilities

• Work item tracking
• Easy, Integrated into development process
• Design your own process Fields, Forms, States,
  Rules
• Extensive linking bugs, reports, artifacts
• Notifications
• Source Code Control
• Easy, integrated into development environment
• Integrated check in experience
• Scalable and robust
• Parallel development
• Notifications

• Build automation
• Scripted nightly build
• Reporting
• Integrates many of the Team System tools
• Metrics warehouse
• Automatic data collection
• OLAP reporting
• Trending, aggregation drilldown
• Project portal
• Single place to go for high-level project
  information
• Web access work items
• WSS based

42
Work Items Everywhere
Assign work items toresources usingMicrosoft
Project
Author work items inMicrosoft Excel
Work items show up inVisual Studio
View project status inMicrosoft Excel
orMicrosoft Project
43
Change ManagementCheck In
Shelvework in progress
Build rules enforcedduring check-inprocess
44
Build Server
45
Reporting
46
Project Portal
SharePoint-basedProject Portal
47
Project Creation
Project Creation Wizard
48
MSF Process Guidance

• Integrated throughout Team System
• Framework for GSIs and customers to implement
  custom software development process
• Harvests proven guidance from in- outside of MS
• Includes two process methodologies
• Instantiation of an agile software development
  process
• Instantiation of a formal software development
  process
• Customizable content, policies, workflow

49
Methodology Template

• Delivered via Team Foundation Server
• Contains
• Work Item Types, workflow
• Check In Policy
• Specification Templates
• Reports
• Groups Permissions
• Integrated Help
• Phase Exit Criteria
• Exposed within Help

50
Team Foundation ServerV2 Roadmap

• Work flow
• Automated Check in acceptance testing, approval
  and review
• Inter-work item flow
• Advanced Distributed development
• Replication, Offline
• Better traceability

51
Visual Studio Team System
Visual Studio Team EditionSoftware Architects
Visual Studio Team EditionSoftware Developers
Visual Studio Team EditionSoftware Testers
Visual StudioTeam Foundation Server
52
Project ManagementProblem Space

• Gaps in translating work
• Team is disconnected
• Tracking, not managing
• Difficult to implement process changes

53
Project Management Goals

• Shape the Project
• Office Integration
• Rich Reporting
• Instrument the Process
• MSF 4.0 Integration
• Process Customization

54
Team System Integration

• Delivered via Team Foundation Server
• Methodology Templates
• Work Item Types, workflow
• Check In Policy
• Specification Templates
• Reports
• Groups Permissions
• Integrated Help
• Phase Exit Criteria
• Exposed within Help
• Updated from MSDN
• Book series Addison Wesley MS Learning

55
Project Creation
Project Creation Wizard
56
Project Management
Assign work items toresources usingMicrosoft
Project
Author work items inMicrosoft Excel
Work items show up inVisual Studio
View project status inMicrosoft Excel
orMicrosoft Project
57
Project Portal
SharePoint-basedProject Portal
58
Team SystemPartner Integration

• Improved shell extensibility model
• Source code control integration
• Plug-in and add-in integration
• Web services for lifecycle integration
• Share data with other lifecycle tools
• Published schemas for modeling
• Shallow extensibility for designers

59
Broad Industry Support
60
Dimensions of Business Value

• Productivity, integration, extensibility
• Lower installation costs
• Lower operations and management costs
• Greater efficiency through integrated tools
• Greater efficiency through integrated methodology
• Greater efficiency through customizability
• Greater team productivity
• Scalable and reliable enough to host large teams
• Lower load testing costs
• Increased predictability and reduced project risk

61
Team System Version 2
62
MSDN Transition
License
Software Assurance
63
Licensing Model

• Active MSDN Universal subscribers will receive a
  no-cost upgrade to their choice of
• Visual Studio Team Edition for Software
  Architects
• Visual Studio Team Edition for Software
  Developers
• Visual Studio Team Edition for Software Testers

or
or

• Team Foundation Server available separately on a
  Server/CAL pricing model

Each Team System client product includes one CAL
for Team Foundation
64
Upgrading to Team SystemPromotional opportunities

• Visual Studio customers should purchase, renew,
  or upgrade to MSDN Universal now
• Promotional opportunities to acquire MSDN
  Universal are now available for new and existing
  Visual Studio customers

• MSDN Universal subscribers will get a no-cost
  upgrade to the role-based Team Edition products
• Special upgrade pricing will be available to move
  up to the Team Suite

65
Developer Roadmap
Windows Longhorn
66
Our PhilosophyCommitment to

• Overall customer satisfaction

• Transparency in features and roadmap

• Increased partner readiness

• Community involvement in design