Gartner Blog Network

Role of the Application Architect

by Michael Blechar  |  December 8, 2010  |  6 Comments

As I prepare to shut down operations for the year, I reflect on some of the most frequently asked questions I get when I visit Gartner clients – What is an application architect?,  What does the application architect do?, and How does the role of the application architect relate to others, such as application developers, enterprise architects and solution architects? This led me to co-author with Bruce Robertson the following three research notes (which were just published today) to address these questions:

Application Architecture Overview, Part 1: General Context and Scope*
Application Architecture Overview, Part 2: Enterprise-Level Scope and Roles*
Application Architecture Overview, Part 3: Project-Level Scope and Roles*

Part of the confusion is that MANY roles contribute to the application architecture, not just the work of the “application architect”. For example, the role of the enterprise solution architect (ESA) addresses the conceptual/planning level of the application architecture in collaboration with other architects focused on the needs of the technology, business and information architectures. The ESA ensures that the application portfolio evolves at an appropriate rate and does not become unviable as the other related architectures change. The ESA also provides the reusable standards, guidelines, patterns and frameworks to application development projects, including those related to application architecture.

At the project-level, solution architects make sure that all aspects of the application solution architecture are optimized (as much as possible given other constraints of time and budget) by working with subject matter experts (SMEs) in the areas of technology, information and application architectures and disciplines. The application architect is the SME focused on designing application interfaces and software services to maximize reuse based on the business processes and governance rules for sharing.

As organizations move to service-oriented architectures (SOAs) where applications are composed via the assembly of reusable application interfaces and services, the role of the application architect becomes crucial to help reduce development time and costs while also enabling application and business agility. So, to net this out, implementing the role of the application architect is a critical success factor for SOA.

Happy Holidays!

*Available to Gartner clients or for a fee


Mike Blechar
VP Distinguished Analyst
17 years at Gartner
43 years IT industry

Michael Blechar is vice president and distinguished analyst in the Information Management Research area of Gartner's Research and Advisory Services. Mr. Blechar specializes in the area of metadata management/repositories, information and data services…Read Full Bio

Thoughts on Role of the Application Architect

  1. Mireille Lucas says:

    Finally something clear! tHANK YOU.

  2. Anit says:

    An applications architecture describes the structure and behaviour of applications used in a business, focused on how they interact with each other and with users. It is focused on the data consumed and produced by applications rather than their internal structure

  3. says:

    This is the 2nd post, of your website I actually read through.
    And yet I actually enjoy this specific one, “Role of the
    Application Architect” the most. Cya ,Chara

  4. U produced a number of good tips inside your blog, “Role of the Application Architect”.
    I will you should be returning to your page soon.

    Thank you -Lucinda

  5. […] Role of the Application Architect. | Comment | […]

  6. It’s fantastic that you are getting ideas from this article as well as from our argument made here.

Leave a Reply

Your email address will not be published. Required fields are marked *

Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.