1 / 45

Visual Studio 2005 Team System: Managing the Software Development Lifecycle

Visual Studio 2005 Team System: Managing the Software Development Lifecycle. <Speaker Name> <Speaker Title> Microsoft Corporation. http://msdn.microsoft.com/teamsystem. The Visual Studio Vision. Build the right product for customers. Reduce development complexity.

Download Presentation

Visual Studio 2005 Team System: Managing the Software Development Lifecycle

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Visual Studio 2005 Team System: Managing the Software Development Lifecycle <Speaker Name> <Speaker Title> Microsoft Corporation http://msdn.microsoft.com/teamsystem

  2. The Visual Studio Vision Build the right product for customers Reduce development complexity Improve software team communication • Foster a vibrant partner ecosystem

  3. Project Managers Hobbyists Web Professionals Solo Professionals Testers Students VB6 Devs Consultants Architects Enthusiasts Part-Timers Enterprise Devs Novices Visual Studio 2005“Personalized productivity”

  4. The Software LifecycleWhat 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”

  5. InfrastructureArchitect Business Stakeholder Developer Tester Project Manager Silos in the IT Lifecycle

  6. Developer InfrastructureArchitect Project Manager End User Tester SolutionArchitect Development Teams

  7. IT Operations doesn’tunderstand applicationstructure Reduce complexitythrough operationsknowledge Increase communication and collaborationvia product integration Infrastructure Architect Developers don’tunderstand operationspolicy Solution Architect Communication Barriers • Pockets of information within disciplines • Unclear delineation of responsibilities • Conflicting best practices and architectures • Conflicting strategic goals and objectives

  8. IncreasedReliability QualityEarly & Often Design forOperations Predictability& Visibility Developer Tester SolutionArchitect ProjectManager InfrastructureArchitect Expanding Visual Studio

  9. Enterprise SCC, reporting, issue tracking, project management Team Communication Static Analysis, performance profiling, unit testing, load testing Quality Early and Often Designing for Operations SOA Designer, Logical datacenter designer, class designer, validations Platform for Innovation Web service based, open protocols, client APIs, extending today’s VSIP

  10. Code Coverage Code Profiler Version Control Work Item Tracking Team Reporting Project Portal Integration Services Project Management Static Code Analyzer Class Designer Unit Testing Dynamic Code Analyzer Visio and UML Modeling Deployment Designer Team Build Application Designer Test Case Management Logical Datacenter Designer Load/Web Testing Visual Studio Professional Edition Team Foundation Client (includes CAL) Manual Testing Process and Architecture Guidance Visual Studio Industry Partners Visual Studio Team System Visual StudioTeam Architect Visual StudioTeam Developer Visual StudioTeam Test Visual StudioTeam Foundation

  11. Team Architect EditionProblem 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

  12. Team Architect Edition • Application Designer • Whiteboard mode for application design • Validation against logical datacenter • Logical Datacenter Designer • Settings and constraints editor • SDM generation and compiler • Click-once support • Deployment Designer • Validation Engine

  13. Team Developer Edition • 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

  14. Team Test Edition • 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

  15. Team Foundation • 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

  16. 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

  17. Broad Industry Support

  18. Developer Roadmap Windows “Longhorn”

  19. Questions Speaker Name, <alias>

  20. Screenshots

  21. Team Architect EditionProblem 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

  22. Application Designer Service-OrientedArchitecture model Port Details editor

  23. Logical Infrastructure Designer Services assignedto logical infrastructure Architecture validatedagainst operationalsettings and constraints

  24. Class Designer Class Designerand two-way code synch (part of VS Standard and above)

  25. Team Developer EditionProblem 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

  26. Static Code Analysis Static Code Analyzer

  27. Code Coverage Code Coverage

  28. Unit Testing Integrated Unit Testing

  29. Team Test EditionProblem Space

  30. Load Testing Creation Load Testing Web recorder

  31. Load Testing Load Testing Perf Counter integrationand monitoring

  32. Test Case Management Test Case Management

  33. Team FoundationProblem Space • Fragmented information • Can’t 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

  34. Project ManagementProblem Space • Gaps in translating work • Team is disconnected • Tracking, not managing • Difficult to implement process changes

  35. 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

  36. Change ManagementCheck In “Shelve”work in progress Build rules enforcedduring check-inprocess

  37. Build Server

  38. Reporting

  39. Project Portal SharePoint-basedProject Portal

  40. Project Creation Project Creation Wizard

  41. Project Creation Project Creation Wizard

  42. 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

  43. Change ManagementCheck In “Shelve”work in progress Build rules enforcedduring check-inprocess

  44. Project Portal SharePoint-basedProject Portal

More Related