Common Phase Pattern: Inputs, Steps, Outputs
The Common Phase Pattern in TOGAF 10 ADM provides a standardized structure for architecture development phases B, C, and D. This pattern ensures consistency and repeatability across the architecture development process. INPUTS: Each phase begins with inputs derived from previous phases, the Archit… The Common Phase Pattern in TOGAF 10 ADM provides a standardized structure for architecture development phases B, C, and D. This pattern ensures consistency and repeatability across the architecture development process. INPUTS: Each phase begins with inputs derived from previous phases, the Architecture Vision, and baseline architecture documentation. These inputs include business requirements, organizational constraints, existing architecture models, and stakeholder feedback. They serve as the foundation for phase activities and guide the architect's work throughout the phase. STEPS: The steps within each phase represent the core activities and tasks performed by architects. These sequential and iterative activities involve analyzing requirements, developing architecture models, evaluating alternatives, and making design decisions. Steps typically include reviewing inputs, identifying stakeholders, defining scope, developing architecture content, and ensuring compliance with enterprise standards and principles. OUTPUTS: Each phase produces documented deliverables that feed into subsequent phases. These outputs include architecture models, baseline and target architecture descriptions, gap analysis reports, migration plans, and recommendations. Outputs are formally reviewed and approved by stakeholders, ensuring alignment with organizational objectives. The Common Phase Pattern emphasizes that each phase (B, C, D) follows a similar logical flow: starting with defined inputs, executing structured activities, and producing measurable outputs. This pattern promotes consistency across the Business, Information Systems, and Technology Architecture phases. It enables architects to apply proven methodologies systematically, improve communication with stakeholders through standardized deliverables, and facilitate knowledge transfer within architecture teams. The pattern also incorporates feedback loops and governance gates, ensuring quality control and stakeholder approval at critical junctures. This structured approach reduces rework, improves traceability, and ensures that architecture decisions are well-documented and justified. By following the Common Phase Pattern, organizations achieve more predictable, repeatable, and successful architecture development outcomes aligned with strategic business objectives.
Common Phase Pattern: Inputs, Steps, Outputs in TOGAF 10 Foundation
Common Phase Pattern: Inputs, Steps, Outputs in TOGAF 10 Foundation
Why It Is Important
The Common Phase Pattern is fundamental to understanding how the TOGAF ADM (Architecture Development Method) operates. Each phase within the ADM follows a consistent and repeatable pattern, which ensures:
1. Consistency: All phases follow the same logical structure, making the methodology predictable and reliable.
2. Quality Assurance: By following structured inputs, steps, and outputs, organizations can ensure that each phase delivers comprehensive and well-documented results.
3. Governance: The pattern provides clear decision points and deliverables, enabling proper project governance and stakeholder reviews.
4. Knowledge Transfer: New practitioners can quickly understand how to execute any phase by learning the common pattern once.
5. Scalability: The pattern can be applied to projects of any size or complexity, from simple updates to enterprise-wide transformations.
What Is the Common Phase Pattern?
The Common Phase Pattern is a standardized structure that applies to each of the nine ADM phases. It provides a framework consisting of three key components:
Inputs: The artifacts, information, and documentation that feed into a phase. These come from previous phases, stakeholder requirements, or existing organizational assets.
Steps: The specific activities and processes performed during the phase to transform inputs into outputs. These are the core work activities.
Outputs: The deliverables and work products that result from executing the phase steps. These become inputs for subsequent phases or provide final architecture documentation.
This pattern ensures that each phase is comprehensive, well-defined, and produces documented evidence of work completed.
How It Works
Phase Execution Cycle:
Step 1: Preparation
Before beginning a phase, review the required inputs. These inputs come from:
• Previous ADM phases
• External sources (stakeholder requirements, enterprise repository)
• Business drivers and strategic initiatives
• Existing architecture documentation
Step 2: Process Execution
Execute the steps defined for the phase. These typically include:
• Gathering and analyzing information
• Creating or refining architecture artifacts
• Performing assessments and evaluations
• Obtaining stakeholder feedback and approval
• Documenting decisions and rationale
Step 3: Output Generation
Produce the required outputs. Each phase generates specific deliverables such as:
• Architecture views and diagrams
• Architecture definitions and specifications
• Gap analyses
• Implementation roadmaps
• Recommendations and risks
Step 4: Quality Review
Ensure outputs meet quality standards and stakeholder expectations before passing them to the next phase.
Step 5: Phase Gate
Obtain approval from stakeholders and decision-makers before proceeding to the next phase.
Common Phase Pattern: Detailed Structure
1. Phase Inputs
Inputs can be categorized as:
External Inputs:
• Request for Architecture Work (from stakeholders)
• Business goals and strategies
• Organizational policies and standards
• Regulatory and compliance requirements
Internal Inputs:
• Outputs from previous ADM phases
• Enterprise repository content
• Existing architecture documentation
• Previous business transformation initiatives
2. Phase Steps
While each ADM phase has specific steps, the general categories of activities include:
• Information Gathering: Collect data from stakeholders, systems, and documentation
• Analysis: Examine current state, identify gaps, and evaluate options
• Design/Development: Create architecture artifacts, models, and specifications
• Validation: Confirm alignment with business requirements and strategic objectives
• Documentation: Record findings, decisions, and recommendations
• Stakeholder Engagement: Review with and obtain feedback from relevant stakeholders
3. Phase Outputs
Common outputs across ADM phases include:
• Architecture Artifacts: Diagrams, models, and visual representations
• Architecture Specifications: Detailed descriptions of components, services, and interfaces
• Gap Analysis: Identification of differences between current and target states
• Recommendations: Suggested improvements and transition strategies
• Risk Assessment: Identified risks and mitigation strategies
• Architecture Repository Updates: Updated content in the enterprise architecture repository
How to Answer Questions Regarding Common Phase Pattern in Exams
Question Types You May Encounter:
Type 1: "Which of the following is an input to [specific phase]?"
How to Answer:
• Identify the phase being referenced
• Consider what information would logically be needed to start that phase
• Eliminate options that are clearly outputs or activities rather than inputs
• Remember that inputs often come from previous phases
• Common inputs include stakeholder requirements, business drivers, and existing documentation
Example: If asked about inputs to Phase B (Business Architecture), think: "What must I know before defining business processes?" Answer: Business goals, current organizational structure, stakeholder requirements.
Type 2: "Which step is typically performed during [phase]?"
How to Answer:
• Focus on the primary objective of the phase
• Consider the logical sequence of ADM phases
• Eliminate options that are clearly from different phases
• Look for verbs indicating action (define, analyze, validate, develop)
• Remember that steps are activities that transform inputs into outputs
Example: For Phase C (Information Systems Architecture), relevant steps include defining data architecture, identifying systems, and mapping applications.
Type 3: "What would be an output of [phase]?"
How to Answer:
• Identify what deliverables that phase should produce
• Consider what would be useful for the next phase
• Outputs are typically documented artifacts, not abstract concepts
• Remember that outputs can be specific models, gap analyses, or roadmaps
• Eliminate options that are inputs or are outputs of different phases
Example: Phase D (Technology Architecture) would output technology standards, architecture decisions, and potentially an infrastructure roadmap.
Type 4: "Arrange these in the correct order [inputs, steps, outputs]"
How to Answer:
• Use logical thinking about the workflow
• Inputs provide the foundation (listed first)
• Steps are the activities that consume inputs and produce outputs (listed second)
• Outputs are the results (listed last)
• Look for cause-and-effect relationships
• If unsure, think about what must exist before each element
Exam Tips: Answering Questions on Common Phase Pattern
Tip 1: Understand the ADM Cycle
Know the nine phases in order (Preliminary, A, B, C, D, E, F, G, H). This helps you understand what information is available as inputs at each stage.
Tip 2: Think Logically About Dependencies
Remember that outputs from one phase become inputs to the next. If you're unsure about a specific phase, consider what the previous phase would have produced.
Tip 3: Focus on the Phase Objective
Each phase has a primary goal. The steps performed should logically support that goal. Use this to eliminate incorrect answer options.
Tip 4: Distinguish Between Similar Concepts
Be careful to distinguish between:
• Inputs vs. Activities: Inputs are things you receive; activities are what you do with them
• Steps vs. Outputs: Steps are processes; outputs are documented results
• Current Phase vs. Adjacent Phases: Don't confuse what belongs to the phase being tested
Tip 5: Use Keywords
• Input keywords: "provided," "received," "documented," "from stakeholders"
• Step keywords: "analyze," "define," "develop," "review," "assess," "validate"
• Output keywords: "document," "specification," "model," "roadmap," "recommendation"
Tip 6: Remember Stakeholder Involvement
Steps almost always include stakeholder engagement (interviews, workshops, reviews). If an option mentions getting stakeholder feedback, it's likely a step.
Tip 7: Consider Practical Artifacts
Outputs are tangible things: documents, diagrams, models, specifications, and analysis reports. Abstract concepts are typically not outputs.
Tip 8: Watch for Phase-Specific Terminology
Each phase has specific focus areas:
• Phase A: Architecture Vision
• Phase B: Business Architecture
• Phase C: Information Systems Architecture
• Phase D: Technology Architecture
• Phase E: Opportunities and Solutions
• Phase F: Migration Planning
• Phase G: Implementation Governance
• Phase H: Architecture Change Management
Know what each phase focuses on to correctly identify its inputs, steps, and outputs.
Tip 9: Practice with Real Scenarios
Consider real-world examples. If a question mentions "defining technical standards," that's likely Phase D output, not Phase B.
Tip 10: Review Phase Gates and Decision Points
Steps include review and approval activities (phase gates). These are important decision points where stakeholders evaluate outputs before proceeding.
Common Pitfalls to Avoid
• Confusing inputs and outputs: Remember the flow is unidirectional—inputs → steps → outputs
• Mixing phases: Each phase has specific deliverables; don't assume outputs from one phase apply to another
• Overthinking: Use the logical flow of the ADM; if something doesn't fit the phase's objective, it's probably not correct
• Forgetting stakeholder involvement: Almost every step includes stakeholder engagement in some form
• Missing the governance aspect: Steps include review, approval, and sign-off activities, not just technical work
Practice Questions
Question 1: Which of the following is typically a step performed during Phase C (Information Systems Architecture)?
A) Define the technology infrastructure
B) Analyze information assets and define data architecture
C) Develop implementation roadmaps
D) Establish the architecture vision
Answer: B - Phase C focuses on information systems, so analyzing information assets and data architecture is appropriate.
Question 2: The output of Phase B (Business Architecture) would typically be used as an input to which phase?
A) Phase A
B) Phase C
C) Phase E
D) Phase G
Answer: B - Outputs from Business Architecture inform the Information Systems Architecture phase.
Question 3: Which of the following best describes the relationship between inputs, steps, and outputs in an ADM phase?
A) Inputs are completed before any steps are considered; outputs are generated only after all steps are done
B) Inputs are reviewed continuously throughout; steps transform them; outputs are delivered incrementally
C) Steps are independent of inputs; outputs are determined by the phase objective
D) Outputs must be finalized before stakeholder review steps can occur
Answer: A - This correctly describes the logical flow of the common phase pattern.
🎓 Unlock Premium Access
TOGAF 10 Foundation + ALL Certifications
- 🎓 Access to ALL Certifications: Study for any certification on our platform with one subscription
- 2806 Superior-grade TOGAF 10 Foundation practice questions
- Unlimited practice tests across all certifications
- Detailed explanations for every question
- TOGAF Foundation: 5 full exams plus all other certification exams
- 100% Satisfaction Guaranteed: Full refund if unsatisfied
- Risk-Free: 7-day free trial with all premium features!