Vsts intro

526 views
412 views

Published on

Visual studio

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
526
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Alternate SKU Slide
    When we set out to “build the right product” we analyzed all the different customers that Visual Studio serves. If you think back to the little old lady at the photo shoot, you realize that the Microsoft developer tools customer base is large, and very diverse. The product that’s appropriate for high end professionals like yourselves is probably not the right product for the hobbyist or the student or even the developer evaluating whether or not to make the leap to .NET.
    That’s why we built the product line so that each product had its role, its very particular and very well defined customer base. This is what we call “personalized productivity”. Internally, of course, this gives us a lot of focus. We have studied, visited, and lived with each of these different kinds of customers. As a result, each team building each product is truly, building the right product for you.
    On one end of the spectrum we have the Visual Studio Express products. These products aren’t designed for you and me. They’re designed for our sons and daughters, our spouses, our parents, our grand-parents, our neighbors. They’re designed for novices, people who have never programmed in their life. A few months ago we announced these products and made them available, and already we’ve had over 300,000 downloaded. We also announced content partnerships with Amazon and eBay. The idea is that these novices don’t know that they want to program. If you ask them if they want to program, they’ll probably tell you, “nah, Donald Trump’s on television”. But, if you tell can convince them to do something fun and interesting on their computer, something related to our content partners, then maybe they’ll put down the remote and do it, and maybe they’ll accidentally learn how to program in the end. That’s our ultimate goal with these products: to remove the myth of programming a computer, and expand the number of proficient and skilled programmers worldwide.
    Of course, at the high end, we’re talking about teams of developers looking to work together to build Connected Systems. Most folks who build these sophisticated, mission-critical applications do so in teams. That’s why we built the Visual Studio Team System, which we’ll see more of in a few minutes.
    In between is the professional developer who is working solo or in a very small team. Think of this person as the small consultant shop or reseller. They build specialized solutions in small teams. This is the heart and soul of our Visual Studio Professional Edition product.
    But, there’s a missing piece. Not everyone needs the sophistication of tools that will help you build mission-critical servers, or to debug stored procedures inside a database, or even to build code inside a database. For a lot of customers, the tools that do that, our Professional Edition and Team System products, just have a ton of extra features.
    For this customer we built the Visual Studio 2005 Standard Edition. It’s the entry point for the professional developer. It’s as easy to use as the Express products, but it includes professional level features for VB6 developers and Web developers who want to move to the .NET Framework or for those developers who want to evaluate the full breadth of our platform. Historically, this developer has built client/server solutions, spending great care on the presentation layer. Of course, these days many of these same developers are building Connected Systems based on Web services. The Standard Edition product is the ideal product for this kind of developer venturing into a world of Web services for the first time.
  • We heard a lot of things from customers as we prepared this product strategy over time.
    Building software today is very difficult: you need to worry about service oriented architectures, data tiers, languages, etc. This places a great deal of pressure on development organizations to make sense of it all.
    Teams are becoming increasingly distributed and specialized, resulting in communication gaps both between roles people play in an organization and in geographic separation.
    The tools that people use today aren’t very well integrated. They often reinforce a lot of the barriers that result from distribution and specialization.
    At the same time, many organizations have much difficulty in predicting the success of projects. At any given moment in time, it’s important to know where the project stands. With specialization and distribution of people alongside the complexity of the people working on projects, it becomes harder and harder to predict that success.
    Finally, many organizations perform a lot of ad hoc development, through processes that are cobbled together and not very rigid. True, many organizations have formal processes, and for those companies it’s important that the tools don’t restrict them from using that process. But, for a lot of companies, it’s important not just to ship tools, but to ship customizable processes.
  • Story about customer presentation where people doing the different roles somehow naturally self-selected sitting in distinct role groups
    Top performing teams know its critical to break these silos because:
    Geographically distributed
    More specialized than ever before & increased specialization leading to more oppty for pockets of information
    Need the agility to react to changes in the requirements or business environment
    Need visibility into the data to make the right decisions
    Shorter cycles to act
  • It’s not just about the developer anymore.
    Applications are so complex these days, that a single development project involves a number of different roles across the entire IT organization.
    BUILD
    Further, modern teams are:
    Geographically distributed
    More specialized than ever before
    Increased specialization leading to pockets of information
    More engagement of business people
    Shorter cycles to act
    Importance of the “abilities”
    Communication has never been more important
  • Success depends on communication
    We can help with communication by giving:
    Process guidance that shows teams how to build software solutions together
    Architectures that clearly delineate roles in the software development process
    Tools that are so tightly integrated that the barriers to communication are eliminated
  • Announcing Visual Studio Team System
    To help IT teams become top performers, Microsoft needs to do more than provide developer tools…we need to provide development tools.
    To that end, we are expanding the Visual Studio product line to include new tools for a variety of roles in the IT lifecycle.
    Microsoft’s announcements around Team System include…
    Visual Studio Team System, an extensible lifecycle tools platform that significantly expands the Visual Studio product line and helps software teams collaborate to reduce the complexity of delivering modern service-oriented solutions
    Microsoft’s offerings now include a comprehensive set of proven process frameworks, best practices, prescriptive architecture guidance, and integrated lifecycle tools that enable IT organizations to successfully deliver custom solutions on the Windows platform
    Numerous industry partners have agreed to extend our lifecycle tools:
    GSIs: Accenture, Avanade, Capgemini, EDS, Fujitsu, Unisys
    ISVs: Amberpoint, Avicode, Borland, Compuware, Serena Telelogic
    With Visual Studio Team System, organizations can:
    Reduce the complexity of delivering modern service-oriented solutions that are designed for operations
    Facilitate collaboration among all members of a software team (including architects, developers, testers, and operations managers), speeding development time and ensuring the predictability and reliability of the development process
    Customize and extend the Team System with their own internal tools and process frameworks or choose from over 450 supplemental products from over 190 partners
  • But, it’s not just about making Connected Systems easier. We still need to address the fundamentals of developer tools and continue to set and move the bar for developer productivity and platform support.
  • Announcing
    Of course, a big part of MSS is the integrated tools
    We’ve designed our tools from the ground up to…
    Reduce the complexity of delivering modern solutions by constructing intuitive user interfaces and baking the process guidance directly into the product
    Facilitate communication and collaboration among members of a software delivery team through deep integration of features
    Enable a vibrant partner ecosystem through a set of Web service-based APIs for ISVs and businesses to plug into
  • Announcing
    Of course, a big part of MSS is the integrated tools
    We’ve designed our tools from the ground up to…
    Reduce the complexity of delivering modern solutions by constructing intuitive user interfaces and baking the process guidance directly into the product
    Facilitate communication and collaboration among members of a software delivery team through deep integration of features
    Enable a vibrant partner ecosystem through a set of Web service-based APIs for ISVs and businesses to plug into
  • Team Architect Edition enables software architects and infrastructure architects to collaborate more effectively on delivering service oriented applciations.
    We will deliver three major designers in VSTS:
    The DAD: enables you to visually author your Web services and service oriented architectures
    The LID: enables you to visually author your network infrastructure
    The CD: enables you to visually author your code
    Now, these three designers are great in and of themselves. However, the “secret sauce” of VSTS is that these designers work well with one another. First, the diagrams you author in the DAD are always synchronized with code. The CD, of course, is a class visualization tool that is always synchronized with code as well. When you author your Web services architecture, those changes are immediately represented in the CD.
    But, most importantly…the architecture you describe in the DAD can be immediately validated against the network infrastructure you describe in the LID. This saves a lot of time when it comes time to deployment as you can have the confidence in knowing that the application you’ve built will, in fact, work in the network topology you’ll need to deploy in.
    This is what we refer to as “designing for operations”, and it’s a key component of our Dynamic Systems Initiative.
  • Announcing
    Of course, a big part of MSS is the integrated tools
    We’ve designed our tools from the ground up to…
    Reduce the complexity of delivering modern solutions by constructing intuitive user interfaces and baking the process guidance directly into the product
    Facilitate communication and collaboration among members of a software delivery team through deep integration of features
    Enable a vibrant partner ecosystem through a set of Web service-based APIs for ISVs and businesses to plug into
  • Team Developer Edition enables advanced developers to verify the performance and quality of the code they write.
    Static code analysis: think of Static Code Analysis as grammar checking for your code. Compilers check your syntax, similar to spell checkers. But, static code analysis tools analyze the semantic meaning behind your code and can detect performance problems, security errors, and more. This is a productization of tools that we’ve used internally for years.
    Code profiling analyzes your code as it’s running to give you more information on how your application is running. We’ll actually ship two code profilers in VSTS: a sampling based profiler and an instrumented profiler. A sampling profiler polls your application and retrieves information about it. Once you get that data, you can use the instrumented profiler. The instrumented profiler injects probes into your code at compile time. As your application runs, those probes fire off data which is collected by the profiler. This is a productization of tools we’ve built and used internally for years.
    Code coverage and unit testing work hand in hand. Unit testing is an attribute based unit testing framework similar to JUnit and NUnit. But, unit testing only tells you how well your code has been tested. It doesn’t tell you how effective your testing is. Code coverage tells you how much of your code has been exercised by unit tests.
    Optional anecdote about code profiling:
    Last year, we brought a very large ISV up to Microsoft to profile their code. They used our code profiler after using several others already in the marketplace and were able to see an immediate 10-15% performance gain. We’ve always considered our code profiling tools as one of our competitive advantages. We’re productizing it and putting it in the box for you to use.
    Optional anecdote about static code analysis:
    As part of our trustworthy computing initiative, we have built a number of tools internally to help us detect errors in our code base. These tools, called PREfast and PREfix, were originally developed in Microsoft Research. We’re productizing all of these tools and making them available to you in the box in Team System.
  • Announcing
    Of course, a big part of MSS is the integrated tools
    We’ve designed our tools from the ground up to…
    Reduce the complexity of delivering modern solutions by constructing intuitive user interfaces and baking the process guidance directly into the product
    Facilitate communication and collaboration among members of a software delivery team through deep integration of features
    Enable a vibrant partner ecosystem through a set of Web service-based APIs for ISVs and businesses to plug into
  • Team Test Edition is load testing software for Web professionals to test the performance capacity of their Web applications and services.
    Load testing includes a Web test recorder that records interaction between the user and the browser which can then be replayed on a test infrastructure
    The Load Testing solution itself enables you to customize how you execute distributed load tests on a test infrastructure.
    Team Test Edition also includes test case management tools for organizing load tests, unit tests, and manual tests in one location.
    The Load Testing software will work on any HTTP or HTTPS based application, be it .NET Framework-based or not. Third-parties can customize the load testing software to support other protocols.
  • Announcing
    Of course, a big part of MSS is the integrated tools
    We’ve designed our tools from the ground up to…
    Reduce the complexity of delivering modern solutions by constructing intuitive user interfaces and baking the process guidance directly into the product
    Facilitate communication and collaboration among members of a software delivery team through deep integration of features
    Enable a vibrant partner ecosystem through a set of Web service-based APIs for ISVs and businesses to plug into
  • Team Foundation is server software for managing collaboration and assets across teams.
    Team Foundation includes enterprise-grade change management tools for managing assets and work items. This is not SourceSafe, it’s built from the ground up on the .NET Framework and Web services to support large teams. We’re already using it inside of Microsoft and will roll it out broadly once we ship the product. It includes all the facilities for branching, changesets, merging, diff, etc. that you’d expect. The Work Item tracking system is a productization of the same tool that all of Microsoft already uses to manage bugs and track work items.
    We’ve integrated with Microsoft Project and Microsoft Excel as well, so that if you’re a casual stakeholder in the project, or just someone who prefers to work in Office, you can do so. The data in Office and the data in Team Foundation are always synchronized.
    As you work and check in, resolve work items, resolve bugs, etc., the Team Foundation gathers a lot of metrics on your project and developers. This information is stored in a SQL 2005 data warehouse. All of this information can be accessed via SQL Reporting Services. We’ll actually ship 50+ reports in the box, and all the reports have associated Web parts which can be displayed in the Project Portal.
    The Project Portal is Sharepoint-based. It’s created for every project portfolio so that you can manage developers, source code, and project status.
  • Announcing
    Of course, a big part of MSS is the integrated tools
    We’ve designed our tools from the ground up to…
    Reduce the complexity of delivering modern solutions by constructing intuitive user interfaces and baking the process guidance directly into the product
    Facilitate communication and collaboration among members of a software delivery team through deep integration of features
    Enable a vibrant partner ecosystem through a set of Web service-based APIs for ISVs and businesses to plug into
  • Gaps in translating work
    Which list are you operating from?
    Difficult to manage project change
    Team is disconnected
    People working on stale info
    Status from team members is pulling teeth
    Inefficiencies between team members
    Tracking, not managing
    Tools stand apart from systems
    Gathering metrics is cumbersome
    Difficulty correcting systemic problems
    Hard to find when you need them
    Process changes aren’t followed
    Painful translation from requirements to actual work.
    I spend all my time mapping and remapping data
    Gathering metrics from all over the place. Its a manual and time intensive exercise
    My metrics, your metrics
    Managing project change becomes a translation nightmare
    Where is the project, overall?
    Separate out the high level from the noise
    Choose areas that will have the most impact
    Want to use best practices
    Hard to find when you need them
    Cannot correct systemic problems in the team with systemic solutions
    People need to go out of their way to follow the process
    Need for more communication /Team is disconnected.
    People working on stale info
    From team members – what have I completed?
    In between team members – can I start work yet? Why don’t those people
  • Partners can expand Visual Studio through a Web services based infrastructure. We’re working closely with a number of partners to help them take advantage of our extensibility model so that they can build tools that are integrated not only at a visual user interface level, but also at a data and workflow level.
  • A number of partners, from large and small ISVs to large and small Systems Integrators are integrating on top of Visual Studio.
  • <number>
  • Visual Studio Team System will be delivered to customers on the following schedule:
    Throughout the year, customers will receive numerous Betas and Community Technology Previews of the Visual Studio Team System
    CTP bits are early access builds of the product and not as stable as Betas
    Removing these bits may require reformatting your drive
    Customers should only install these bits on a non-production machine
    Visual Studio 2005, including the Visual Studio 2005 Team System, will ship in the first half of calendar year 2005
    MSDN Universal and MSDN Enterprise subscribers will be shipped copies of all pre-release versions of Visual Studio and Visual Studio Team System
    Visual Studio Team System pricing or licensing terms are not yet announced, but we offer the following guidance to our customers:
    Today’s Visual Studio .NET 2003 product line (and the corresponding MSDN Universal and MSDN Enterprise subscriptions) is designed for developers. The Visual Studio Team System addresses various roles throughout the enterprise lifecycle and as such adds significant new functionality
    Visual Studio Team Developer Edition provides more functionality than the current Visual Studio .NET 2003 Enterprise Architect Edition product.
    MSDN Universal customers may migrate to their choice of Visual Studio Team Architect Edition, Visual Studio Team Developer Edition, or Visual Studio Team Test Edition at no additional cost for the duration of their MSDN Universal subscription
    Visual Studio Team Developer Edition is the default migration path for all existing MSDN Universal subscribers and contains a superset of most existing functionality
    MSDN Universal customers may also elect to migrate to the Visual Studio Team System at an additional cost to be named later
    Visual Studio Team System will be offered on a subscription basis to customers, as well as on a standalone license basis
  • Vsts intro

    1. 1. The Visual Studio Vision Build the right product for customers Reduce development complexity Improve software team communication Foster a vibrant partner ecosystem
    2. 2. Visual Studio 2005 “Personalized productivity” Hobbyists Students Enthusiasts Novices Project Managers Web Professionals VB6 Devs Part-Timers Solo Professionals Testers Consultants Architects Enterprise Devs
    3. 3. The Software Lifecycle What We’ve Heard  “Building software today is very difficult”  “My team is spread out and specialized”  “Tools today don’t work well together”  “I need to be able to predict the success of my projects”  “My organization needs customizable process guidance”
    4. 4. Silos in the IT Lifecycle Project Manager Infrastructure Architect Business Stakeholder Developer Tester Solution Architect
    5. 5. Development Teams Infrastructure Architect Solution Architect Developer Tester End User Project Manager
    6. 6. Communication Barriers Developers don’t understand operations policy Solution Infrastructure Architect Increase communication Architect collaboration and via product integration     IT Operations doesn’t understand application structure Reduce complexity through operations knowledge Pockets of information within disciplines Unclear delineation of responsibilities Conflicting best practices and architectures Conflicting strategic goals and objectives
    7. 7. 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
    8. 8. Expanding Visual Studio Developer Solution Architect Tester Project Manager Infrastructure Architect Design for Operations Predictability & Visibility Increased Reliability Quality Early & Often
    9. 9. Team Communication Enterprise SCC, reporting, issue tracking, project management Quality Early and Often Static Analysis, performance profiling, unit testing, load testing Designing for Operations SOA Designer, Logical datacenter designer, validations Platform for Innovation Web service based, open protocols, client APIs, extending today’s VSIP
    10. 10. Visual Studio Team System Visual Studio Team Edition Visual Studio Team Edition Visual Studio Team Edition Software Architects Software Developers Software Testers Application Designer Dynamic Code Analyzer Load Testing System Designer Static Code Analyzer Manual Testing Logical Datacenter Designer Code Profiler Test Case Management Deployment Designer Unit Testing Code Coverage Class Designer (in Visual Studio Standard Edition and higher) Visio for Enterprise Architects (in MSDN Premium Subscription) Team Explorer (includes Team Foundation Server CAL) Visual Studio Team Foundation Server Change Management Reporting Integration Services Team Build Work Item Tracking Project Portal Project Management o du Sl aus V i t i a ss ec o P r Visual Studio Professional Edition
    11. 11. Visual Studio Team System Visual Studio Team Edition Visual Studio Team Edition Visual Studio Team Edition Software Architects Software Developers Software Testers Application Designer Dynamic Code Analyzer Load Testing System Designer Static Code Analyzer Manual Testing Logical Datacenter Designer Code Profiler Test Case Management Deployment Designer Unit Testing Code Coverage Class Designer (in Visual Studio Standard Edition and higher) Class Designer (in Visual Studio Standard Edition and higher) Class Designer (in Visual Studio Standard Edition and higher) Visio for Enterprise Architects (in MSDN Premium Subscription) Team Explorer (includes Team Foundation Server CAL) Visual Studio Team Foundation Server Change Management Reporting Integration Services Team Build Work Item Tracking Project Portal Project Management o du Sl aus V i t i a ss ec o P r Visual Studio Professional Edition
    12. 12. Team Edition (Architects)  Application Designer     Logical Datacenter Designer    Whiteboard mode for application design Validation against logical infrastructure Visualize relationships of distributed systems Settings and constraints editor SDM generation and compiler System Designer and Deployment Designer   Binds application design to datacenter design Enables creation of composable systems
    13. 13. Team Edition (Architects) Problem Space  Customers have communication problems between  Architects and Developers   Development and Operations   Deployment problems caught too late Customers recognize value of modeling tools     Developers do not work within architectural guidelines 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
    14. 14. 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
    15. 15. Application Designer Service-Oriented Architecture model Port Details editor
    16. 16. Logical Infrastructure Designer Services assigned to logical infrastructure Architecture validated against operational settings and constraints
    17. 17. Class Designer Class Designer and two-way code synch
    18. 18. Team Edition (Architects) V2 Roadmap  Support for Indigo service framework  Contract Designer  Business Process Designer
    19. 19. 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
    20. 20. Visual Studio Team System Visual Studio Team Edition Visual Studio Team Edition Visual Studio Team Edition Software Architects Software Developers Software Testers Application Designer Dynamic Code Analyzer Load Testing System Designer Static Code Analyzer Manual Testing Logical Datacenter Designer Code Profiler Test Case Management Deployment Designer Unit Testing Unit Testing Code Coverage Class Designer (in Visual Studio Standard Edition and higher) Visio for Enterprise Architects (in MSDN Premium Subscription) Team Explorer (includes Team Foundation Server CAL) Visual Studio Team Foundation Server Change Management Reporting Integration Services Team Build Work Item Tracking Project Portal Project Management o du Sl aus V i t i a ss ec o P r Visual Studio Professional Edition
    21. 21. Team Edition (Developers)  Static code analysis   Code profiling      Support for managed and native code 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
    22. 22. 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
    23. 23. 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:        Includes ETW events Sequence view examines running threads GC view of object allocation and lifetime Caller-callee, callstack, and function views Code coverage    Instrumented – IceCAP, used by Windows Base and SQL Server Sampling – LOP, used throughout MX, including Xbox Basic Block Coverage Based on the BBCover technology that Windows & Visual Studio use Application Verifier
    24. 24. Static Code Analysis Static Code Analyzer
    25. 25. Code Coverage Code Coverage
    26. 26. Unit Testing Integrated Unit Testing
    27. 27. 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
    28. 28. Visual Studio Team System Visual Studio Team Edition Visual Studio Team Edition Visual Studio Team Edition Software Architects Software Developers Software Testers Application Designer Dynamic Code Analyzer Load Testing System Designer Static Code Analyzer Manual Testing Logical Datacenter Designer Code Profiler Test Case Management Deployment Designer Unit Testing Code Coverage Class Designer (in Visual Studio Standard Edition and higher) Visio for Enterprise Architects (in MSDN Premium Subscription) Team Explorer (includes Team Foundation Server CAL) Visual Studio Team Foundation Server Change Management Reporting Integration Services Team Build Work Item Tracking Project Portal Project Management o du Sl aus V i t i a ss ec o P r Visual Studio Professional Edition
    29. 29. Team Edition (Testers)  Load testing      Web services load testing via protocolbased script Load patterns: constant, step, custom Perf counter collection and threshold monitoring Test case management Application Verifier
    30. 30. Team Edition (Testers) Problem Space   Poorly written applications reflect poorly on the platform Testers are underserved and second class in Microsoft’s 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
    31. 31. Team Edition (Testers)    Testing is 1st class in Visual Studio Tests are Source Code Test Authoring & Execution Environment    Load testing     Test View Test Explorer (Test Case Management UI) Web services load testing via protocol-based script Load patterns: constant, step, custom Perf counter collection and threshold monitoring Unit Testing  Similar to NUnit
    32. 32. Load Testing Creation Load Testing Web recorder
    33. 33. Load Testing Load Testing Perf Counter integration and monitoring
    34. 34. Test Case Management Test Case Management
    35. 35. Team Edition (Testers) V2 Roadmap  Functional UI testing   Test Lab management    For Avalon, Windows.Forms, Win32, and IE Setup, tear down, distribution, and baselining Historical code coverage trends on a per-method basis Test case prioritization
    36. 36. Visual Studio Team System Visual Studio Team Edition Visual Studio Team Edition Visual Studio Team Edition Software Architects Software Developers Software Testers Application Designer Dynamic Code Analyzer Load Testing System Designer Static Code Analyzer Manual Testing Logical Datacenter Designer Code Profiler Test Case Management Deployment Designer Unit Testing Code Coverage Class Designer (in Visual Studio Standard Edition and higher) Visio for Enterprise Architects (in MSDN Premium Subscription) Team Explorer (includes Team Foundation Server CAL) Visual Studio Team Foundation Server Change Management Reporting Integration Services Team Build Work Item Tracking Project Portal Project Management o du Sl aus V i t i a ss ec o P r Visual Studio Professional Edition
    37. 37. Team Foundation Server  Portfolio creation and navigation    Project management     Microsoft Project and Excel integration Change management   Project Creation Wizard Process editor for customized guidance Branching, changesets, shelving Migration from ClearCase and VSS Reporting and analytics Project portal
    38. 38. Team Foundation Server Problem Space  Fragmented information     Communication is manual     Can’t relate and query work items, work, processes and artifacts Tools sets are incomplete or poorly integrated Difficulty integrating tools with existing infrastructure 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
    39. 39. Team Foundation Server Today’s problems, our solutions  Fragmented information  Integrated Information      Communication is manual  Stream-lined communication      Life cycle tools are expensive and complex  Automated Data Capture Complete Lifecycle Toolset Common Linking Service Extensible Team Foundation SDK with web service based APIs 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
    40. 40. Team Foundation Server Capabilities  Work item tracking      Easy, Integrated into development process Design your own process – Fields, Forms, States, Rules Extensive linking – bugs, reports, artifacts Notifications          Easy, integrated into development environment Integrated check in experience Scalable and robust Parallel development Notifications    Scripted “nightly” build Reporting Integrates many of the Team System tools Metrics warehouse  Source Code Control  Build automation 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
    41. 41. Work Items Everywhere Assign work items to resources using Microsoft Project Author work items in Microsoft Excel Work items show up in Visual Studio View project status in Microsoft Excel or Microsoft Project
    42. 42. Change Management Check In “Shelve” work in progress Build rules enforced during check-in process
    43. 43. Build Server
    44. 44. Reporting
    45. 45. Project Portal SharePoint-based Project Portal
    46. 46. Project Creation Project Creation Wizard
    47. 47. MSF Process Guidance  Integrated throughout Team System    Includes two process methodologies    Framework for GSIs and customers to implement custom software development process Harvests proven guidance from in- & outside of MS Instantiation of an agile software development process Instantiation of a formal software development process Customizable content, policies, workflow
    48. 48. 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
    49. 49. Team Foundation Server V2 Roadmap  Work flow    Advanced Distributed development   Automated Check in acceptance testing, approval and review Inter-work item flow Replication, Offline Better traceability
    50. 50. Visual Studio Team System Visual Studio Team Edition Visual Studio Team Edition Visual Studio Team Edition Software Architects Software Developers Software Testers Application Designer Dynamic Code Analyzer Load Testing System Designer Static Code Analyzer Manual Testing Logical Datacenter Designer Code Profiler Test Case Management Deployment Designer Unit Testing Code Coverage Class Designer (in Visual Studio Standard Edition and higher) Visio for Enterprise Architects (in MSDN Premium Subscription) Team Explorer (includes Team Foundation Server CAL) Visual Studio Team Foundation Server Change Management Reporting Integration Services Team Build Work Item Tracking Work Item Tracking Project Portal Project Management o du Sl aus V i t i a ss ec o P r Visual Studio Professional Edition
    51. 51. Project Management Problem Space     Gaps in translating work Team is disconnected Tracking, not managing Difficult to implement process changes
    52. 52. Project Management Goals  Shape the Project    Office Integration Rich Reporting Instrument the Process   MSF 4.0 Integration Process Customization
    53. 53. 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
    54. 54. Project Creation Project Creation Wizard
    55. 55. Project Management Assign work items to resources using Microsoft Project Author work items in Microsoft Excel Work items show up in Visual Studio View project status in Microsoft Excel or Microsoft Project
    56. 56. Project Portal SharePoint-based Project Portal
    57. 57. Team System Partner 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
    58. 58. Broad Industry Support
    59. 59. 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
    60. 60. Team System Version 2 Project Expanded project estimation and management tools management tools Integration with enterprise planning and portfolio management tools Integration with enterprise management tools Dynamic Systems Initiative Integration Expanding role-based lifecycle tools with…
    61. 61. MSDN Transition “License” “Software Assurance” Visual Studio Team Suite with MSDN Premium Subscription Visual Studio Team Edition for Software Architects with MSDN Premium Subscription Visual Studio Team Edition for Software Developers with MSDN Premium Subscription Visual Studio Team Edition for Software Testers with MSDN Premium Subscription Visual Studio Professional Edition with MSDN Premium Subscription with MSDN Professional Subscription
    62. 62. 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  Visual Studio Team Suite “Step Up” pricing with MSDN Premium Subscription MSDN Universal Architect N/C Upgrade or with MSDN Premium Subscription  Developer N/C Upgrade or Tester N/C Upgrade with MSDN Premium Subscription Team Foundation Server available separately on a Server/CAL pricing model Visual Studio Team Foundation Server Server/CAL Each Team System client product includes one CAL for Team Foundation with MSDN Premium Subscription
    63. 63. Upgrading to Team System Promotional 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
    64. 64. Developer Roadmap Windows “Longhorn”
    65. 65. Our Philosophy Commitment to… Overall customer satisfaction Transparency in features and roadmap Increased partner readiness Community involvement in design

    ×