In-Depth

Requirements Patterns With VSTS

Learn some simple yet powerful requirements patterns that you can apply to most projects and processes.

 Listen to the audio and watch the slides! (Running time: 1 hour, 3 minutes) Some projects use VB.NET, some use C#, some use Managed C++, and some use a combination of those. Some projects are Web-based, while others run on a desktop or in a console. But no matter how they differ, all projects are the same in one regard: They all have requirements. So requirements definition and management should be at the core of any good process. In this session, you'll learn how Visual Studio 2005 Team System helps you define, store, track, and report requirements. You'll also learn some simple yet powerful requirements patterns that you can apply to most projects and processes.

comments powered by Disqus

Featured

  • Visual Studio 2026 Gives Copilot Built-In Skills -- and Makes Them Prove Their Worth

    Microsoft is moving Agent Skills beyond bring-your-own instructions by shipping expert-authored workflows with the IDE, while keeping them off by default until testing shows their benefits justify the additional token use.

  • Copilot AI Billing Shock Met with Meters, Caps and Token-Saving Tools

    GitHub is layering spending limits, expanded credit allowances and increasingly granular usage reporting onto Copilot, while Microsoft is reworking Visual Studio and VS Code to expose -- and reduce -- the cost of agentic development.

  • The AI-Powered Software Development Lifecycle

    René van Osnabrugge makes the case that AI's biggest opportunity in software development is not faster coding -- it's reducing the friction everywhere else in the SDLC.

  • Copilot Usage-Based Billing Gets a Token Dashboard

    Microsoft is keeping Visual Studio's new built-in Agent Skills switched off by default while a public dashboard measures whether their performance gains justify the additional tokens they may consume.

Subscribe on YouTube