Agile Architecture Method Explained

From Guidance Share
Revision as of 21:45, 21 December 2008 by JD (talk | contribs)
(diff) ←Older revision | Current revision (diff) | Newer revision→ (diff)
Jump to navigationJump to search

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

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.

We wrote this guide to accomplish the following:

  • To help you design more effective architectures.
  • To help you choose the right technologies.
  • To help you make more effective choices for key engineering decisions.


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