Application Architecture Guide

From Guidance Share

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

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

Next diff →
Line 27: Line 27:
== Chapters == == Chapters ==
Forewords Forewords
-* [Agile Architecture Method Explained - Foreword by S. Somasegar | Foreword by S. Somasegar]+* [[Agile Architecture Method Explained - Foreword by S. Somasegar | Foreword by S. Somasegar]]
-* [Agile Architecture Method Explained - Foreword by Scott Guthrie | Foreword by Scott Guthrie]+* [[Agile Architecture Method Explained - Foreword by Scott Guthrie | Foreword by Scott Guthrie]]

Revision as of 22:30, 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 with the following:

  • design more effective architectures
  • choose the right technologies
  • make more effective choices for key engineering decisions


Key Features

The guide includes the following:

  • Architecture Frame - is a map of some of the most important elements of architecture, including scenarios, quality attributes, application types, architecture styles and key engineering hot spots.
  • Application Types - a set of canonical application archetypes to illustrate common application types. Each archetype will be described in terms of the target scenarios, technologies, patterns and infrastructure it contains. Each archetype will be mapped to the canonical app frame. They are illustrative of common app types and not comprehensive or definitive.
  • Application Feature Frame - a common set of hot spots for key engineering decisions.
  • Quality Attributes - a set of qualities/abilities that shape your application architecture: performance, security, scalability, manageability, deployment, communication, etc.
  • Layered Application Reference Example - describes at a meta-level, the tiers and layers that an architect should consider. Each tier/layer will be described in terms of its focus, function, capabilities, common design patterns and technologies.
  • Principles, patterns and practices - using the frames as backdrops, the guide overlays relevant principles, patterns, and practices.


Part I, Fundamentals Part II, Design Part III, Layers Part IV, Archetypes



Introduction Architecture and Design Solutions At a Glance Fast Track Part I, Fundamentals Chapter 1 - Fundamentals of Application Architecture Chapter 2 - .NET Platform Overview Chapter 3 - Architecture and Design Guidelines Part II, Design Chapter 4 - Designing Your Architecture Chapter 5 - Deployment Patterns Chapter 6 - Architectural Styles Chapter 7 - Quality Attributes Chapter 8 - Communication Guidelines Part III, Layers Chapter 9 - Layers and Tiers Chapter 10 - Presentation Layer Guidelines Chapter 11 - Business Layer Guidelines Chapter 12 - Data Access Layer Guidelines Chapter 13 - Service Layer Guidelines Part IV, Archetypes Chapter 14 - Application Archetypes Chapter 15 - Web Applications Chapter 16 - Rich Internet Applications (RIA) Chapter 17 - Rich Client Applications Chapter 18 - Services Chapter 19 - Mobile Applications Chapter 20 - Office Business Applications (OBA) Chapter 21 - SharePoint Line-Of-Business (LOB) Applications Appendix Cheat Sheet - patterns & practices Pattern Catalog Cheat Sheet - Presentation Technology Matrix Cheat Sheet - Data Access Technology Matrix Cheat Sheet - Workflow Technology Matrix Cheat Sheet - Integration Technology Matrix


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

Personal tools