This post originated from an RSS feed registered with .NET Buzz by Damir Tomicic. Original Post: The Whitehorse modeling tools are officially now known as Visual Studio 2005 Team Architect Feed Title: Damir Tomicic : community powered Feed URL: http://tomicic.de/SyndicationService.asmx/GetRss Feed Description: stuff about .NET, community and life - in several languages. Latest .NET Buzz Posts Latest .NET Buzz Posts by Damir Tomicic Latest Posts From Damir Tomicic : community powered

The time of the rumors is over - Keith Short explaines: "...The Whitehorse modeling tools are officially now known as Visual Studio 2005 Team Architect to emphasize the integration with the other capabilities of the Team System. Anyone interested in these tools should check out the Visual Studio 2005 Team System link...". Michael Platt explaines the main elements of Team System (aka Burton) in his last posting. And last but least, Sam Guckenheimer introduces his new blog related to Burton. 

Burton will move into direct competition with e.g. Rational Suite, including and offering everything from requirements management to design, modeling, development, testing and maintenance built into VS 2005. Do we need that? Sure, we do. Visio or Enterprise Architect, VSS and several third-party tools will be replaced with one in-the-box solution for distributed, team-oriented enterprise application development ... It cannot be stated too often that if you are developing software, you need a process. Of course, everyone of you will have its own answers to these questions. Bijan Javidis project ".NET Development Process" is the best example of an lightweigth process model, which could be easily implemented with Burton. This process is a well documented, mature solution that works for the most of the small and medium-size development projects. We do implement it in our daily work and it works very well for us.

And hey, it's good that there's competition. What about usable and affordable Rational version? Perhaps some day ... ;-)