Microsoft Visual Studio 2008 Unleashed

Chapter 27. Architecture Edition

IN THIS CHAPTER

• Team Architect Artifacts

• Designing Your Application

• Defining a System

• Defining Your Infrastructure

• Deploying Your Application

• Implementing Your Application

Most developers will agree that having a solid architecture and visualization of your code will lead to a better overall product and development experience. More often than not, however, architecture documents are created at the beginning of the project (if at all) in a tool like Visio only to become quickly outdated during the build phase. It seems there is never time enough to go back and update the diagrams. You are left to watch them rapidly deteriorate into “original design” or “system vision” documents—new labels put on what once represented the ...