Architecture management is the practice of providing a shared understanding of how an organisation’s systems, processes, and services are structured.

Its purpose is to ensure that the organisation’s architecture supports its strategy and objectives.

Architecture management helps guide change by defining standards, principles, and models.

It supports consistency, interoperability, and efficiency across the organisation.

Architecture management should consider both current and future states.

---

2. How This Applies to TakeCars (Car Rental Marketplace)

Architecture management is often misunderstood as “enterprise IT only”, but it is highly relevant for a growing marketplace.

a) What “architecture” means at TakeCars

Architecture is not just servers or code. It includes:

• How bookings flow end to end
• How data moves between components
• How decisions are automated vs manual
• How support, payments, and hosts interact

If this is not understood, scaling becomes chaotic.

---

b) Current vs future state (critical ITIL idea)

At TakeCars:

• Current state
  • Some manual checks
  • Some automations
  • Mixed host quality
• Future state
  • More automation
  • Clearer data ownership
  • Predictable exception handling

Architecture management exists to guide movement between these states without breaking the service.

---

c) Standards, principles, and models in TakeCars terms

Examples:

• One source of truth for booking data
• Standard pickup and return flow
• Clear separation between:
  • Booking logic
  • Payment logic
  • Support logic

Without standards, every new feature increases complexity and risk.

---

d) Why architecture management matters for reliability

Poor architecture leads to:

• Data inconsistency
• Manual workarounds
• Support errors
• Fragile integrations

Good architecture:

• Improves availability and continuity
• Reduces incident volume
• Makes improvement faster and safer

---

e) Exam-critical insight

If the exam asks:

“What is the purpose of architecture management?”

Correct logic:

• Provide shared understanding
• Support strategy and objectives
• Guide change using standards and principles
• Consider current and future states

Answers focusing only on technology diagrams are incomplete.

---

3. Key Things to Read / Remember Right Before the Exam

Architecture management (moderate–high probability)

• A general management practice
• Provides shared understanding of structure
• Guides change
• Aligns architecture with strategy

---

Common exam traps

• Architecture management is only about IT infrastructure → False
• Architecture management focuses only on current state → False
• Architecture management replaces design work → False

---

One-line memory hook

Architecture management provides structure and standards so change supports strategy instead of breaking services.

---