.png)
overview
1
fundamentals
2
get tools
3
start learning
What is software architecture? (overview) Understanding code involves multiple tasks. Tooling can help you visualize and understand the organization, relationships, and behavior of the code. For example, to examine the existing relationships and patterns in the code, generate dependency graphs. To communicate the intended architecture of your system, create layer diagrams. You can then use these diagrams to keep the code consistent with the design. To understand how the code implements a method, generate sequence diagrams. To explore the structure of existing classes, create class diagrams. Read on >>
View this content about the process of software architecture, and then prepare your environment by installing the tools that you'll use to build applications.
Introducing Visual Studio: General and Architecture Overview Modern software development is anything but simple. Accordingly, the tools that support today's development teams have many moving parts, and Visual Studio 2010 is no exception. One way to get a handle on this product family is to start with a broad look at the components and how they fit together. Once we've done this, we can look more closely at the piece that ties everything else together: Team Foundation Server. Read on >>
For help picking the right version of Visual Studio, review the Visual Studio 2010 comparison chart.
Use the following resources to help you learn more about understanding code, requirements analysis, systems design, and the lifecycle of designing software.
GENERATE A SOURCE CODE DEPENDENCY GRAPH In this walkthrough, you can use any project to generate a dependency graph of your object model. A dependency graph lets you determine the hierarchy and reference structure of your objects and is a great way to visualize, and clean up your object design. This feature requires Visual Studio Ultimate.
UNDERSTANDING YOUR SYSTEMS: EXPLORE YOUR APPLICATION ARCHITECTURE Making changes in an existing system can mean you often don’t know what you are going to break until it’s too late. This is time-consuming and costly, and it can result in numerous bug fixes required immediately after a release. Architecture Explorer provides a dependency view to help you determine which items are connected to the one you are changing, from any level (method, class, namespace, assembly, or solution). Whitepaper for the Video (no longer available)
CHANGE YOUR DESIGN USING VISUALIZATION AND MODELING TOOLS This walkthrough demonstrates tools that are available in Visual Studio 2010 Ultimate that help ensure a software system meets its users' needs. These tools include Unified Modeling Language (UML) diagrams, layer diagrams, code-based dependency graphs, sequence diagrams, and class diagrams. |
Related Topics Designing and Modeling Video Series Microsoft Application Architecture Guide Visual Studio Application Lifecycle Management Visual Studio Application Lifecycle Management: Documentation Architecture Developer Center Books
|
.png "read document"){kind=icon}
.png "download"){kind=icon}
.png "play video"){kind=icon}
.jpg)
.jpg)
.jpg)