Application Architecture Guide

From Guidance Share

(Difference between revisions)
Jump to: navigation, search
Revision as of 22:10, 25 April 2009 (edit)
JD (Talk | contribs)

← Previous diff
Revision as of 22:13, 25 April 2009 (edit)
JD (Talk | contribs)

Next diff →
Line 2: Line 2:
-[[image:ApplicationArchitectureGuide.png|left]] This guide summarizes the patterns & practices approach to agile architecture design. An agile architecture approach is lightweight, iterative and leverages an understanding of the key hotspots where architecture and design mistakes are most often made. Agile architecture activities include identification of architecture objectives, determination of architecturally significant scenarios, identification of your application type, understanding deployment constraints, choice of architectural styles, determination of technology options, identification of key hot spots, and creation of candidate solutions. These activities are iterative, with an understanding that you may not know everything you need to know at the start and will adjust your approach as additional information becomes available. +[[image:ApplicationArchitectureGuide.png|left]] The purpose of the Application Architecture Guide is to improve your effectiveness building applications on the Microsoft platform. The primary audience is solution architects and developer leads. The guide provides design-level guidance for the architecture and design of applications. It focuses on the most common types of applications, partitioning application functionality into layers, components, and services, and walks through their key design characteristics.
-We wrote this guide to accomplish the following: + 
-* To help you design more effective architectures. +We wrote this guide to help you accomplish the following:
-* To help you choose the right technologies. +* Design more effective architectures.
-* To help you make more effective choices for key engineering decisions. +* Choose the right technologies.
 +* Make more effective choices for key engineering decisions.
 + 
 + 
 +The guide includes the following:
 +* a canonical application frame,
 +* a set of canonical application types
 +* an architecture frame, quality attributes
 +* principles, patterns, and practices
 +* technologies and capabilities.
<br clear="all" /> <br clear="all" />

Revision as of 22:13, 25 April 2009

- J.D. Meier, Alex Homer, David Hill, Jason Taylor, Prashant Bansode, Lonnie Wall, Rob Boucher Jr, Akshay Bogawat.


The purpose of the Application Architecture Guide is to improve your effectiveness building applications on the Microsoft platform. The primary audience is solution architects and developer leads. The guide provides design-level guidance for the architecture and design of applications. It focuses on the most common types of applications, partitioning application functionality into layers, components, and services, and walks through their key design characteristics.

We wrote this guide to help you accomplish the following:

  • Design more effective architectures.
  • Choose the right technologies.
  • Make more effective choices for key engineering decisions.


The guide includes the following:

  • a canonical application frame,
  • a set of canonical application types
  • an architecture frame, quality attributes
  • principles, patterns, and practices
  • technologies and capabilities.


Chapters

The following overview shows you how to execute the agile architecture method:

Personal tools