Solution architects versus enterprise architects

While all IT architects create, implement, and maintain some type of IT architecture, there is little consensus about the names of IT architects. Some of the often used names are:

  • Enterprise architect
  • Solution architect
  • Information architect
  • Software architect
  • Infrastructure architect
  • Security architect
  • Project architect
  • Systems architect
  • Application architect

Since not everyone knows exactly what these people do and what their exact expertise is, I propose to use only two names: Enterprise Architect and Solution Architect. A clear distinction can be made between the roles of a solution architect and that of an enterprise architect.

Solution architects create IT solutions, usually as member of a project team. A solution architect is finished when the project is finished. Solution architects are the technical conscience and authority of a project, are responsible for the architectural decisions in the project and work closely with the project manager. Where the project manager manages the process of a project, the solution architect manages the technical solution the project builds, based on requirements.

Enterprise architects continuously align the overall IT landscape of an organization with the business activities the organization performs. Enterprise architects enable transformations of the overall IT landscape (including the IT infrastructure) over the years in a structured manner. An enterprise architect is therefore never finished (as opposed to the solution architect in a project, who is finished when the project is finished). Enterprise architects typically work in close corporation with the CIO and the business units, where they try to align the needs of the business with the current and future IT landscape. Enterprise architects build bridges and act as advisors to the business and to the IT department.

In short: Solution architects are the people that design, implement and deploy new (infrastructure) solutions in projects. Enterprise architects set the boundaries the solution architect has to stay within, based on business needs.


This entry was posted on Friday 15 February 2013

Earlier articles

Quantum computing

Security at cloud providers not getting better because of government regulation

The cloud is as insecure as its configuration

Infrastructure as code

DevOps for infrastructure

Infrastructure as a Service (IaaS)

(Hyper) Converged Infrastructure

Object storage

Software Defined Networking (SDN) and Network Function Virtualization (NFV)

Software Defined Storage (SDS)

What's the point of using Docker containers?

Identity and Access Management

Using user profiles to determine infrastructure load

Public wireless networks

Supercomputer architecture

Desktop virtualization

Stakeholder management

x86 platform architecture

Midrange systems architecture

Mainframe Architecture

Software Defined Data Center - SDDC

The Virtualization Model

What are concurrent users?

Performance and availability monitoring in levels

UX/UI has no business rules

Technical debt: a time related issue

Solution shaping workshops

Architecture life cycle

Project managers and architects

Using ArchiMate for describing infrastructures

Kruchten’s 4+1 views for solution architecture

The SEI stack of solution architecture frameworks

TOGAF and infrastructure architecture

The Zachman framework

An introduction to architecture frameworks

How to handle a Distributed Denial of Service (DDoS) attack

Architecture Principles

Views and viewpoints explained

Stakeholders and their concerns

Skills of a solution architect architect

Solution architects versus enterprise architects

Definition of IT Architecture

What is Big Data?

How to make your IT "Greener"

What is Cloud computing and IaaS?

Purchasing of IT infrastructure technologies and services

IDS/IPS systems

IP Protocol (IPv4) classes and subnets

Infrastructure Architecture - Course materials

Introduction to Bring Your Own Device (BYOD)

Fire prevention in the datacenter

Where to build your datacenter

Availability - Fall-back, hot site, warm site

Reliabilty of infrastructure components

Human factors in availability of systems

Business Continuity Management (BCM) and Disaster Recovery Plan (DRP)

Performance - Design for use

Performance concepts - Load balancing

Performance concepts - Scaling

Performance concept - Caching

Perceived performance

Ethical hacking

The first computers

Open group ITAC /Open CA Certification


Recommended links

Ruth Malan
Gaudi site
Esther Barthel's site on virtualization
Eltjo Poort's site on architecture


Feeds

 
XML: RSS Feed 
XML: Atom Feed 


Disclaimer

The postings on this site are my opinions and do not necessarily represent CGI’s strategies, views or opinions.

 

Copyright Sjaak Laan