Architecture Documentation: C4, arc42

Understands main types of architecture documentation: system overview, component diagrams, sequence diagrams, deployment diagrams. Knows C4 model notation at a basic level. Can document simple architectural decisions using templates.

Independently applies C4 model and arc42 to document the architecture of team services and their integrations. Authors ADRs that clearly capture context, decision, and consequences of technical choices. Understands trade-offs between diagram-as-code tools (Structurizr, PlantUML) and visual editors. Keeps documentation aligned with CI/CD pipelines and deployment topology.

Independently initiates ADR creation for key product decisions with technical justification. Reviews architectural documentation for product requirements compliance. Maintains an up-to-date registry of technical decisions.

Creates comprehensive architecture documentation with architects: system context, container diagrams, component diagrams (C4). Documents data flows, external system integrations, deployment topology. Keeps documentation up to date.

Designs end-to-end architecture documentation using all four C4 levels from system context to code. Produces comprehensive arc42 documentation covering quality requirements, runtime views, and deployment scenarios. Mentors engineers on writing effective ADRs that capture architectural drivers, alternatives considered, and trade-off analysis. Scales documentation practices across multiple solution domains using templates and automated validation.

Designs the architecture documentation strategy for complex multi-service systems using C4 and arc42. Establishes ADR conventions including numbering, lifecycle states, and superseding rules. Mentors developers on creating meaningful component and container diagrams rather than superficial overviews. Integrates documentation generation into CI pipelines using Structurizr DSL or similar diagram-as-code tools.

Establishes architectural documentation process for the product, including RFCs and design docs. Defines technical specification templates with business context. Ensures traceability from business requirements to architectural decisions.

Designs the structure and process for maintaining architecture documentation for large systems. Implements diagrams-as-code approach (Mermaid, PlantUML, Structurizr DSL). Ensures coherence between ADRs, architecture diagrams, and API documentation.

Defines architecture documentation strategy at the product and portfolio level using C4 and arc42 as canonical frameworks. Establishes documentation governance including review gates, freshness policies, and cross-team consistency standards. Conducts architecture reviews ensuring solution documentation captures integration points, quality attribute scenarios, and deployment constraints. Drives ADR adoption as the primary mechanism for capturing and communicating architectural decisions.

Defines architecture documentation strategy at the team and product level, selecting appropriate C4 depth and arc42 sections per service criticality. Establishes best practices for ADR authoring including templates, status workflows, and linking to implementation PRs. Conducts regular architecture documentation reviews to prevent drift between diagrams and actual system state. Champions documentation-as-code culture with automated rendering and publishing pipelines.

Defines architectural documentation standards for the division. Introduces culture of writing — design docs, RFCs, post-mortems as mandatory artifacts. Integrates architectural decisions into product roadmap.

Defines architecture documentation standards for the organization: required artifacts, detail levels, review process. Coordinates architecture documentation across teams, ensuring a unified system landscape view.

Defines architecture documentation strategy at the organizational level, establishing enterprise C4 and arc42 standards across all solution domains. Creates a federated documentation governance model enabling autonomous teams while maintaining enterprise-wide architectural coherence. Establishes ADR repositories with cross-cutting search, impact analysis, and architectural knowledge management. Mentors leads and architects on evolving documentation practices to support organizational scaling, M&A integration, and technology radar alignment.

Defines architecture documentation strategy at the organizational level, standardizing C4 and arc42 usage across all engineering departments. Establishes enterprise ADR governance with centralized registries, cross-domain linking, and automated staleness detection. Drives adoption of architecture documentation toolchains (Structurizr, Backstage, architectural fitness functions) at scale. Mentors leads and architects on building self-sustaining documentation ecosystems that remain accurate as the organization evolves.

Shapes enterprise approach to architectural knowledge management. Defines governance process for cross-team architectural decisions, builds knowledge base of technical trade-offs at organizational level.

Shapes the company's architectural knowledge strategy: unified architecture knowledge base, enterprise architecture integration, governance processes. Defines how architecture documentation supports strategic technical decision-making.