Break methodology and TOGAF Testing Phases

1. Preliminary Phase

Objective: Determine the testing principles and strategy within the architecture approach.

Test Activities:

• Define a testing strategy aligned with the architectural vision.
• Establish standards and guidelines for test automation, tools, and testing processes.
• Ensure testers participate in architecture workshops.
• If test policy is seen as a foundational standard for your organization’s architecture approach. Download the template and compare!

2. Phase A: Architecture Vision

Objective: Validate the architectural vision.

Test Activities:

• Review high-level business use cases and identify potential risks and dependencies.
• Define acceptance criteria for the architectural vision.
• Ensure testing goals are linked to business objectives.
• If the test policy is treated as part of the high-level principles governing the architecture’s scope. Download the break template and compare!

3. Phase B: Business Architecture

Objective: Analyze business processes and functions.

Test Activities:

• Validate business models and workflows for feasibility.
• Develop test cases for business processes (e.g., process validation or end-to-end scenarios).
• Identify areas requiring user acceptance testing (UAT).

4. Phase C: Information Systems Architectures

Objective: Design application and data architecture.

Test Activities:

• Define test cases for data integrity, data migration, and security.
• Develop test criteria for system integration.
• Implement testing of architectural models (e.g., mock-ups or simulations).

5. Phase D: Technology Architecture

Objective: Design the technical infrastructure.

Test Activities:

• Validate infrastructure components through load and performance tests.
• Test the technical architecture for scalability and fault tolerance.
• Conduct iterative validation of proofs-of-concept.

6. Phase E: Opportunities and Solutions

Objective: Determine solutions and their implementation planning.

Test Activities:

• Review solution scenarios and identify testing impact and risks.
• Ensure test automation is included in proposed tools and platforms.
• Align tests with the planned implementation strategy (e.g., Agile or Waterfall).

7. Phase F: Migration Planning

Objective: Plan the transition to the target architecture.

Test Activities:

• Develop migration test plans for transitioning from legacy to new systems.
• Validate the migration strategy using mock tests and pilot migrations.
• Create regression tests to ensure existing functionality is preserved.

8. Phase G: Implementation Governance

Objective: Monitor and validate the implementation.

Test Activities:

• Conduct validation tests and quality checks on implemented components.
• Monitor implementation performance using automated tests.
• Ensure continuous integration and testing to maintain compliance with architectural principles.
• Double check the test policy with the Break test method template sections! Your test policy may contain more, but it should at least include the sections of the template.

9. Phase H: Architecture Change Management

Objective: Manage changes to the architecture.

Test Activities:

• Develop tests for new architectural adjustments.
• Implement regression tests to ensure existing architectural elements are unaffected.
• Validate that changes comply with architectural standards.