Requirements Patterns With VSTS -- Visual Studio Magazine

Requirements Patterns With VSTS

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

By Martin L. Shoemaker
05/01/2006

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.

Printable Format

comments powered by Disqus

Featured

Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.
Diving Deep into .NET MAUI

Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.
Copilot AI Boosts Abound in New VS Code v1.96

Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.
AdaBoost Regression Using C#

Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.
Versioning and Documenting ASP.NET Core Services

Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.