11.2 Change Classification: Simplification, Incremental, and Re-Architecting Changes

11.2 Change Classification: Simplification, Incremental, and Re-Architecting Changes

When drivers of change arise during the operational life of an enterprise architecture, the architecture organization must possess an objective, standardized mechanism to assess and categorize them. Applying the full weight of the Architecture Development Method (ADM) to every minor software upgrade would paralyze organizational delivery with stifling bureaucracy. Conversely, treating disruptive business model pivots as routine maintenance leads to uncontrolled architectural drift, fragmented systems, and catastrophic strategic misalignment. To balance governance agility against operational risk, the TOGAF Standard classifies architecture change into three categories: Simplification Change, Incremental Change, and Re-Architecting Change.

---

TOGAF's Three Classes of Architecture Change

TOGAF describes an approach to change management that classifies each required architectural change into one of three categories:

To decide which class applies, TOGAF lists four activities: register all events that may affect the architecture; allocate and manage resources for architecture tasks; have the process or role responsible for architecture resources assess what should be done; and evaluate the impacts.

TOGAF's Rule of Thumb: Count the Stakeholders

TOGAF offers a guideline for maintenance versus redesign:

• If the change impacts two or more stakeholders, it is likely to require an architecture redesign and re-entry to the ADM.
• If the change impacts only one stakeholder, it is more likely to be a candidate for change management.
• If the change can be allowed under a dispensation, it is more likely to be a candidate for change management.

TOGAF's own examples:

• A change with significant impact on the business strategy may require redoing the whole Enterprise Architecture: a re-architecting approach.
• New technology or standards may require refreshing the Technology Architecture but not the whole Enterprise Architecture: an incremental change.
• A change at the infrastructure level, for example ten systems reduced to one, may not change the architecture above the physical layer but will change the Technology Architecture baseline description: a simplification change handled via change management.

A refreshment cycle, either partial or complete re-architecting, may also be needed when the Foundation Architecture must be realigned with the business strategy, when substantial change is needed to components and guidelines used in deploying the architecture, or when significant standards used in the product architecture change.

The governance body must set criteria for deciding whether a Change Request needs only an architecture update or a new ADM cycle, and TOGAF warns it to avoid "creeping elegance" by focusing on changes that relate directly to business value. An Architecture Compliance report should state whether the change is compliant with the current architecture; if not, an exemption may be granted with valid rationale.

---

Scenario Analysis: Borderline Case Studies

Practitioners frequently encounter borderline scenarios where the classification requires rigorous architectural judgment:

Case Study 1: The Multi-CRM Rationalization Dilemma

An enterprise has six regional sales divisions running separate commercial off-the-shelf CRM instances acquired through historical acquisitions. An architectural proposal emerges to migrate all divisions to the enterprise-standard corporate CRM. Business capabilities remain identical; only complexity, maintenance overhead, and software licensing are reduced.

• Classification: Simplification Change.
• Rationale: The change eliminates technical redundancy and streamlines operations without altering the enterprise's strategic capabilities or principles. Governed via Phase H change management and Architecture Board approval without issuing a new Request for Architecture Work.

Case Study 2: The Core Database Version Upgrade

A high-volume payments platform running on an approved database platform requires an upgrade from version 12 to version 15 to preserve security compliance. No interface contracts change; existing data schemas and application code remain intact.

• Classification: Incremental Change.
• Rationale: The modification derives more value from the existing investment, by keeping the platform supported, without changing the architecture's structure, and it affects a single stakeholder group. Under TOGAF's guideline it is a candidate for change management rather than re-entry to the ADM.

Case Study 3: The Connected Vehicle Telematics Platform

A traditional automobile manufacturer decides to build an in-vehicle IoT telematics ecosystem, offering dynamic over-the-air software updates, autonomous driving telemetry streaming, and subscription-based digital features. This fundamentally disrupts the existing manufacturing-centric business architecture, introduces massive new data ingestion requirements, and establishes a brand-new direct-to-consumer revenue stream.

• Classification: Re-Architecting Change.
• Rationale: This initiative requires brand-new business capabilities, alters the corporate business model, and invalidates the existing Architecture Vision. A formal Request for Architecture Work is issued, triggering Phase A to define a new Architecture Vision.

---

Common Exam Traps & Practitioner Pitfalls

• The 'Scope Creep Disguise' (Anti-Pattern): Delivery teams attempting to implement a Re-Architecting Change incrementally across multiple minor releases to bypass executive scrutiny and formal Phase A Architecture Board approval. The enterprise architect must recognize cumulative architectural drift and mandate a new Request for Architecture Work.
• The 'Simplification Panic': Misclassifying system rationalization as re-architecting, forcing an organization through months of bureaucratic ADM restarts when the fundamental architecture vision remains unchanged.
• The 'Cloud Migration Myth': Assuming that every cloud migration is automatically a Re-Architecting Change. Migrating an existing virtual machine image unchanged into an Infrastructure-as-a-Service (IaaS) cloud ('lift-and-shift') is an Incremental or Simplification Change; refactoring a legacy monolithic mainframe application into a global event-driven serverless architecture is a Re-Architecting Change.