Exploring the Different Types of Architects

Objective

After completing this lesson, you will be able to describe the roles and responsibilities of architects.

Introducing the Lesson: Exploring the Two Types of Architects

This lesson introduces the various architect roles and highlights their specific tasks and responsibilities:

This lesson contains the following topics:

The enterprise architect
The solution architect
How enterprise architects and solution architects work together

Enterprise Architects versus Solution Architects

The Core Analogy: City Planner vs. Building Architect

The figure illustrates the levels of the two architect roles concerning the strategic and the technological focus.

When thinking about the differences between the types of architects the following may be helpful:

An Enterprise Architect is like a City Planner. They don't design individual buildings. Instead, they look at the entire city and plan its overall structure. They define zoning laws (e.g., residential vs. commercial), design the transportation grid (roads, subways), plan utility infrastructure (power, water), and ensure the city can grow sustainably and efficiently over the next 10-20 years. Their goal is the long-term health and coherence of the entire city.
A Solution Architect is like a Building Architect. They are given a specific plot of land within the city (a business problem) and must design a functional, safe, and effective building (a technology solution) on that plot. They must follow the city planner's zoning laws and connect to the existing utility and transportation grids. They focus on the design, materials, and construction of that specific building to meet the needs of its future occupants.

One of the things noticeable regarding the two different types of architects is the relatively different emphasis or focus that they have in regards to adopting a strategic or technical orientation.

Comparison Table: Enterprise Architect vs. Solution Architect

Feature	Enterprise Architect (EA)	Solution Architect (SA)
Primary Focus	Strategic: "WHAT" and "WHY"	Tactical: "HOW"
Scope	Enterprise-wide: The entire organization, its goals, processes, and technology landscape.	Project/Solution-specific: A single business problem, application, or system integration.
Time Horizon	Long-term: 3-10 year roadmaps. Focused on the future state of the organization.	Mid-term: The lifecycle of a specific project (months to 1-2 years).
Key Question	"How can technology enable our long-term business strategy?"	"How do we build a technical solution to solve this specific business problem?"
Stakeholders	C-level executives (CIO, CTO, CEO), business unit leaders.	Project managers, business analysts, development teams, infrastructure engineers.
Key Deliverables	- IT Strategy & Roadmaps- Technology Principles & Standards- Capability Maps- Governance Frameworks- Enterprise Architecture Blueprints	- High-Level Solution Design Documents- Technology Selection for a Project- Proof-of-Concept (POC) definitions- Non-functional Requirements (NFRs) design- System Integration Diagrams
Concerns	Business-IT alignment, agility, standardization, cost optimization, risk management across the enterprise.	Meeting functional and non-functional requirements, technology fit, project constraints (budget, timeline), developer guidance.

In-Depth Description

Enterprise Architect (EA)

The Enterprise Architect operates at the highest level of an organization's technology strategy. Their job is to ensure that the company's technology landscape is not a chaotic, siloed mess but a coherent, efficient, and agile platform that supports the overall business strategy.

Key Responsibilities:

Strategic Alignment: They work closely with business leaders to understand where the company is headed and create a technology roadmap to support that vision. For example, if the business strategy is to expand into a new global market, the EA will plan the necessary architectural changes to support multiple languages, currencies, and data residency laws.
Governance and Standards: EAs define the "rules of the road" for technology. They decide which technologies are approved for use (e.g., "We will use AWS for cloud, not Google Cloud"), set standards for security and data management, and establish principles that all new projects must follow.
Holistic View: They maintain a blueprint of the entire organization's technology, data, and business processes. This allows them to identify redundancies (e.g., "Why do we have three different CRM systems?"), find opportunities for consolidation, and manage risks at a macro level.
Future-State Planning: Their focus is on the desired future state. They are constantly evaluating emerging technologies and trends to see how they can be leveraged for a competitive advantage.

Solution Architect (SA)

The Solution Architect takes the strategic direction and standards set by the EA and applies them to a specific business problem or project. They bridge the gap between the high-level enterprise strategy and the detailed technical implementation.

Key Responsibilities:

Problem Solving: They are given a specific business requirement (e.g., "We need a new mobile app for our customers") and are responsible for designing the end-to-end technical solution.
Technical Design The SA translates business requirements into a technical blueprint. This includes choosing the right technologies (from the EA's approved list), defining the system's components, how they will interact, and how data will flow between them.
Managing Constraints: They must design a solution that works within the project's constraints, such as budget, timeline, and the skills of the development team. They also address non-functional requirements like performance, scalability, and security for their specific solution.
Guidance and Collaboration: The SA works closely with the development teams, providing them with the architectural designs and guidance needed to build the solution correctly. They ensure the final product aligns with the initial design.

How They Work Together

The relationship is hierarchical and collaborative:

The Enterprise Architect provides the vision, strategy, and standards (the "city plan").
The Solution Architect takes a specific project and designs a solution that adheres to those standards while solving a concrete business problem (designs the "building" according to the "zoning laws").
The SA provides feedback to the EA. If a standard is proving impractical or a new technology used in a project shows great promise, the SA can recommend changes to the enterprise standards. This creates a healthy feedback loop.

The cooperation between enterprise architects and solution architects creates the link between the technological vision and its effective implementation.

Summary

To summarize:

	Enterprise Architect	Solution Architect
Think of them as...	The City Planner	The Building Architect
Their scope is...	Broad & Strategic (the whole organization)	Deep & Tactical (a specific project)
Their goal is...	To ensure long-term coherence and efficiency of the enterprise.	To deliver a working, effective solution for a business need.

Summary

An Enterprise Architect focuses on the "Why" and "What.". They ensure SAP BTP fits into the overall business and IT strategy. Their concern is the entire enterprise landscape and its long-term health. A Solution Architect focuses on the "How." They design a specific application or integration on SAP BTP to solve a concrete business problem. Their concern is the successful delivery of a single project or product.

Next lesson