J.D. Meier's Blog

Software Engineering, Project Management, and Effectiveness

Abstract for Application Architecture Guide 2.0

Abstract for Application Architecture Guide 2.0

  • Comments 12

A few people have asked me for an abstract on the patterns & practices Application Architecture Guide 2.0 project (a work in progress).  Here it is.

Conceptual Framework
A picture is worth a thousand words.  Here's the conceptual framework for the guide:

AppArchMetaFrame

Tagline

"How to put the legos together"

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

Key Features

  • Canonical app frame - 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.
  • App Types - 5-7 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.
  • Arch Frame - a common set of categories for 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.
  • Principles, patterns and practices - Using the frames as backdrops, the guide will overlay relevant principles, patterns, and practices.
  • Technologies and capabilities - a description/overview of the Microsoft custom app dev platform and the main technologies and capabilities within it.

Key Scenarios

  • Help you choose the right architecture for your application.
  • Help you choose the right technologies
  • Help you make more effective choices for key engineering decisions.
  • Help you map appropriate strategies and patterns.
  • Help you map relevant patterns & practices solution assets.

My Related Posts

  • patterns & practices App Arch Guide 2.0 Project
  • App Arch Meta-Frame
  • App Types
  • Architecture Frame
  • App Arch Guidelines
  • Layers and Tiers
  • Layers and Components
  • Services Layer
  • Scenario Frames for Presentation, Business, Data and Services
  • patterns & practices Security Engineering
  • patterns & practices Performance Engineering
  • Key Software Trends
    • Today we posted our Arch Frame to CodePlex.  Wednesdays are ship days (I don't ship on Fridays.) 

    • As part of our patterns & practices App Arch Guide 2.0, I put together a short list of resources

    • I added a brief over deck of our patterns & practices App Arch Guide 2.0 project to codeplex: App

    • As part of our patterns & practices App Arch Guide 2.0 project , we'll be creating step-by-step How

    • As part of our patterns & practices Application Architecture Guide 2.0 project , we've been hunting

    • As part of our patterns & practices Application Architecture Guide 2.0 project , we've been hunting

    • Today we released our patterns & practices App Arch Guide 2.0 Beta 1 .  This is our guide to

    • [FromJ.DMeier’sBlog:http://blogs.msdn.com/jmeier/default.aspx]Todaywereleasedourpatterns

    • It would help to use entity data model in the Layered Architecture Sample application to take advantage of the ORM capabilities.

      Any plans for this?

    • @Binoj Antony -

      Good feedback - I'll pass it along.

    • I presented our new patterns & practices Agile Architecture Method for the first time at the patterns

    • One of the questions I get asked is how did we execute our patterns & practices Application Architecture

    Page 1 of 1 (12 items)