---
title: "VS 2005 Team System Modeling Strategy and FAQ"
url: "https://osherove.com/blog/2005/6/5/vs-2005-team-system-modeling-strategy-and-faq.md"
canonical: "https://osherove.com/blog/2005/6/5/vs-2005-team-system-modeling-strategy-and-faq.html"
published: "2005-06-05T21:24:00"
updated: "2005-06-05T21:24:00"
tags: ["Architecture"]
author: "Roy Osherove"
description: "This looks interesting: Summary: Customers and partners are keen to understand Microsoft's strategy for model-driven development and its support in Visual Studio Team System. When we explain our strategy to them, they…"
usage: "Licensed under CC BY 4.0 — reuse, quote and adapt with attribution (Roy Osherove, link to the original page)."
license: "https://creativecommons.org/licenses/by/4.0/"
---

# VS 2005 Team System Modeling Strategy and FAQ

By Roy Osherove June 5, 2005 In [Architecture](https://osherove.com/blog/category/architecture)

**Historical article** · Originally published June 5, 2005; technical details may be outdated.

[This looks interesting:](http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnvs05/html/vstsmodel.asp)

_**Summary:** Customers and partners are keen to understand Microsoft's strategy for model-driven development and its support in Visual Studio Team System. When we explain our strategy to them, they frequently express interest in some of the same topics, and raise some of the same concerns. In this document we set out our strategy for model-driven development as a series of questions and responses that address these topics and concerns. The first five questions deal with the main pillars of our strategy, which we have described with detailed answers and explanations. Other frequently asked questions are gathered in a conventional FAQ in the last section. (15 printed pages)_

## More in Architecture

[All posts in Architecture](https://osherove.com/blog/category/architecture)

- Jun 18, 2005

    ### [Why payroll systems are a pain to design - Temporal Data (and some great resources on it)](https://osherove.com/blog/2005/6/18/why-payroll-systems-are-a-pain-to-design-temporal-data-and-s.html)

- Jun 5, 2005

    ### [What's legacy code?](https://osherove.com/blog/2005/6/5/whats-legacy-code.html)

- May 2, 2005

    ### [Regulator 2005 & GUI threads goo- news on both?](https://osherove.com/blog/2005/5/2/regulator-2005-amp-gui-threads-goo-news-on-both.html)

- May 2, 2005

    ### [What does SOA really mean? One big hype machine](https://osherove.com/blog/2005/5/2/what-does-soa-really-mean-one-big-hype-machine.html)


---

## About the author

**Roy Osherove**: Senior Solutions Architect at AWS working on AI for production and AI-driven development; author of The Art of Unit Testing and Elastic Leadership, with about 20 years of consulting and training on unit testing, TDD, team leadership and continuous delivery.

### Sites

- [RobotPaper](https://robotpaper.ai/): This blog: AI patterns and anti-patterns, AI and coding agents, and engineering leadership.
- [osherove.com](https://osherove.com): Roy's personal site. Author of The Art of Unit Testing and Elastic Leadership; consulting and training on unit testing, TDD, team leadership and continuous delivery, plus about 20 years of blog posts.
- [The Art of Unit Testing](https://www.artofunittesting.com): The Art of Unit Testing, 3rd Edition (Manning): readable, maintainable, trustworthy unit tests, plus TDD workshops in C#, JavaScript, Java and Kotlin.
- [5whys.com](https://www.5whys.com): Roy's writing on software team leadership: self-organizing teams, surviving chaos, learning mode and the Elastic Leadership model.
- [Pipeline Driven](https://pipelinedriven.org): Continuous delivery and DevOps practices: build patterns, pipeline-friendly testing, DevOps metrics and enterprise DevOps.
- [Elastic Leadership](https://www.elasticleadership.com): Elastic Leadership, Roy's framework for software team leaders (survival, learning and self-organizing modes).

### Social

- X: https://x.com/royosherove
- LinkedIn: https://www.linkedin.com/in/osherove/

### Contact

- Contact form: https://forms.gle/jQSx5KoXvrVA1JCK7

### License

Licensed under CC BY 4.0 — reuse, quote and adapt with attribution (Roy Osherove, link to the original page). License: https://creativecommons.org/licenses/by/4.0/