Summary

You have seen how Visual Studio Team Architect can be used to move software modeling beyond just raw documentation. The models you create with it are much more: They are real tools that help increase productivity and reduce errors.

In this chapter, you looked at the standard approach for modeling applications. You first created an application diagram to represent the interfaces, services, and database that existed in the example. You then created a system diagram to group key application elements. Next, you learned how the logical datacenter diagram can be used to represent a physical infrastructure environment. This diagram became the basis of a test deployment for the application. Finally, you saw how the Class Designer can be leveraged to build diagrams and code at the same time.

These tools form the basis for modeling with Visual Studio 2005. They also represent a milestone step in what is sure to be a great future for visually modeling applications and code.