Architecture Partitioning

Architecture Partitioning in TOGAF 10 Foundation - Complete Guide

Introduction to Architecture Partitioning

Architecture Partitioning is a fundamental concept in the TOGAF ADM (Architecture Development Method) that involves dividing an enterprise architecture into manageable segments or domains. This guide will help you understand this critical concept for your TOGAF 10 Foundation exam.

Why Architecture Partitioning is Important

Architecture Partitioning serves several crucial purposes in enterprise architecture:

• Complexity Management: Large enterprises have complex structures that are difficult to manage as a single unit. Partitioning breaks them into manageable pieces.
• Parallel Development: Different teams can work on different partitions simultaneously, improving efficiency and reducing time-to-delivery.
• Clear Ownership: Each partition can be assigned to specific stakeholders, creating clear accountability and ownership.
• Risk Management: Issues in one partition are less likely to cascade across the entire enterprise architecture.
• Flexibility: Partitions can be updated, modified, or replaced independently without affecting the entire architecture.
• Scalability: As organizations grow, new partitions can be added without redesigning the entire architecture.
• Stakeholder Alignment: Different stakeholders can focus on the partitions most relevant to their interests and roles.

What is Architecture Partitioning?

Definition: Architecture Partitioning is the process of dividing an enterprise architecture into discrete, manageable parts or segments called partitions. Each partition represents a cohesive set of business capabilities, applications, infrastructure, or organizational units.

Key Characteristics:

• Partitions are logical groupings rather than strictly physical divisions
• They should be loosely coupled but highly cohesive
• Each partition should have clear boundaries and defined interfaces
• Partitions can be organized along various dimensions such as business units, geographies, technologies, or business capabilities
• Partitions may be hierarchical, with higher-level partitions containing lower-level ones

Types of Architecture Partitions

Business Domain Partitions: Based on business units or functional areas (e.g., Sales, Marketing, Finance)

Capability-Based Partitions: Organized around business capabilities rather than organizational structure

Technology Partitions: Based on technology domains (e.g., Database, Network, Security)

Geographic Partitions: Divided by location or region

Process-Based Partitions: Grouped around business processes

Application Partitions: Focused on application domains or portfolios

How Architecture Partitioning Works

Step 1: Identify Partitioning Dimensions

Determine the most appropriate way to divide the architecture. This could be based on:

• Business structure and reporting hierarchy
• Business capabilities and value streams
• Technology domains and infrastructure layers
• Geographic distribution
• Regulatory or compliance requirements

Step 2: Define Partition Boundaries

Establish clear, unambiguous boundaries for each partition:

• What is included in this partition?
• What is explicitly excluded?
• Where are the interfaces between partitions?
• What interactions occur across partition boundaries?

Step 3: Establish Partition Governance

Create governance structures for each partition:

• Assign ownership and accountability
• Define decision-making authority
• Establish review and approval processes
• Create escalation paths for cross-partition issues

Step 4: Document Interfaces

Clearly document how partitions interact:

• Data flows between partitions
• Service invocations and dependencies
• Integration points and protocols
• Constraints and constraints on communication

Step 5: Apply the ADM to Each Partition

The ADM (Architecture Development Method) can be applied at the partition level:

• Each partition can undergo its own architecture phases
• Partition-level decisions must align with enterprise-wide principles
• Different partitions may be at different stages of the ADM
• Iteration cycles for partitions may be shorter than enterprise-wide cycles

Step 6: Manage Partition Dependencies

Monitor and manage relationships between partitions:

• Identify critical dependencies
• Ensure dependency chains don't create bottlenecks
• Establish clear SLAs (Service Level Agreements) for partition interactions
• Plan for changes that might affect multiple partitions

Partitioning Strategies in TOGAF ADM

Horizontal Partitioning: Dividing by organizational level (e.g., enterprise, domain, department)

Vertical Partitioning: Dividing by business capability or value stream

Matrix Partitioning: Combining multiple dimensions (e.g., both business unit and technology domain)

Benefits and Challenges

Benefits:

• Enables iterative and incremental architecture development
• Allows parallel work streams across teams
• Reduces architectural complexity
• Facilitates easier change management
• Improves stakeholder engagement
• Enables focused governance

Challenges:

• Poorly defined boundaries can create redundancy or gaps
• Cross-partition dependencies can become complex
• Inconsistent decisions across partitions can lead to fragmentation
• Partition governance overhead can be significant
• Evolving business needs may require repartitioning

Exam Tips: Answering Questions on Architecture Partitioning

Tip 1: Understand the "Why" Before the "How"

Exam questions often ask why partitioning is used. Remember that the primary reasons are complexity management, enabling parallel work, and clear ownership. If asked about the purpose, emphasize these key drivers.

Tip 2: Know the Relationship to ADM Phases

Partitioning is relevant throughout the ADM cycle, especially in:

• Phase A (Architecture Vision): High-level partitioning strategy is defined
• Phase B, C, D (Business, Information Systems, Technology): Detailed architecture for each partition
• Phase E (Opportunities and Solutions): Partitions help identify implementable projects

When answering questions, connect partitioning decisions to the appropriate ADM phase.

Tip 3: Remember "Loosely Coupled, Highly Cohesive"

This is a golden principle in architecture partitioning. Expect questions asking about the characteristics of well-partitioned systems. The answer should emphasize that partitions should have minimal dependencies on each other (loosely coupled) while internal to each partition components should work well together (highly cohesive).

Tip 4: Distinguish Between Different Partitioning Approaches

The exam may ask you to identify the most appropriate partitioning approach for a scenario. Consider:

• If the organization is structured by business units → use business domain partitioning
• If the focus is on reusability and flexibility → use capability-based partitioning
• If dealing with infrastructure and operations → use technology partitioning
• If supporting global operations → consider geographic partitioning

Tip 5: Watch for Governance Questions

Questions may ask about how to govern partitioned architectures. Key points to remember:

• Each partition needs clear ownership
• There should be enterprise-wide standards that apply across all partitions
• Partitions need defined interfaces and integration points
• There should be centralized governance for cross-partition decisions

Tip 6: Recognize Partitioning in Scenarios

Exam scenarios may describe a situation without explicitly mentioning "partitioning." Look for clues:

• Multiple teams working on different areas
• Different business units with distinct needs
• Plans to implement in phases
• Need to manage complex systems

When you see these clues, think about how architecture partitioning could address the challenges.

Tip 7: Understand Partition-Level ADM Application

A key concept is that the ADM can be applied at the partition level. This means:

• Each partition can have its own architecture vision aligned with enterprise vision
• Each partition can develop its own business, information systems, and technology architectures
• Partitions may be at different maturity levels at any given time
• The ADM cycle for a partition may be shorter than the enterprise cycle

Questions may ask how to apply the full ADM to a partitioned architecture.

Tip 8: Focus on Practical Benefits

Always connect partitioning concepts to practical organizational benefits:

• Speed: Parallel development across partitions
• Risk: Issues contained within partitions
• Accountability: Clear ownership and responsibility
• Change: Easier to modify specific areas

If asked about benefits, explain using these practical outcomes rather than abstract concepts.

Tip 9: Be Aware of Partitioning Anti-Patterns

The exam may present scenarios showing poor partitioning. Common anti-patterns to recognize:

• Overly Fragmented: Too many small partitions creating management overhead
• Tightly Coupled: Partitions with heavy interdependencies
• Misaligned: Partitions that don't match organizational structure or business capabilities
• Inconsistent Standards: Different partitions following different architectural principles

When you encounter these, be ready to explain why they're problematic and suggest better approaches.

Tip 10: Practice with Scenario-Based Questions

Architecture Partitioning is often tested through scenarios. When answering:

1. Identify the complexity being managed
2. Determine the most appropriate partitioning dimension
3. Explain how boundaries should be defined
4. Describe governance structure for the partitions
5. Discuss interfaces and dependencies
6. Link back to ADM phases and enterprise principles

Tip 11: Remember Common Exam Question Formats

Expect questions like:

• "Which approach to architecture partitioning is MOST appropriate for...?" - Compare different strategies and select the best fit
• "What is a key characteristic of well-partitioned architecture?" - Look for answers mentioning loose coupling and high cohesion
• "How does partitioning support the ADM?" - Explain how partitions enable iterative development
• "Which of these represents poor partitioning practice?" - Identify anti-patterns
• "What governance structure is needed for a partitioned architecture?" - Describe ownership, standards, and decision-making

Tip 12: Align Partitioning with Other TOGAF Concepts

Partitioning doesn't exist in isolation. Connect it to:

• Architecture Principles: Partitions should respect enterprise principles
• Reference Models: Use TOGAF's modular framework when defining partitions
• Building Blocks: Partitions contain multiple building blocks
• Stakeholder Management: Partitions help identify and manage stakeholder groups
• Architecture Governance: Partitions require tailored governance approaches

Key Takeaways for Your Exam

• Architecture Partitioning is about dividing complexity into manageable segments
• Partitions should be loosely coupled and highly cohesive
• Different partitioning approaches suit different organizational contexts
• Partitions require clear boundaries and defined interfaces
• Each partition needs clear ownership and governance
• The ADM can be applied at the partition level
• Partitioning enables parallel work and faster delivery
• Partitioning must align with organizational structure and business capabilities
• Cross-partition dependencies must be carefully managed
• Partitioning is a strategic decision that should be made early in architecture development

Final Exam Advice: When answering questions on Architecture Partitioning, always think about the business context and organizational goals. The best partitioning strategy is one that aligns the architecture with how the organization operates and evolves. Use the ADM as your framework for thinking through partitioning decisions, and always emphasize the practical benefits: complexity management, parallel development, clear ownership, and flexibility for change.