A hierarchical set of software architecture diagrams (Context, Container, Component, Code) for different zoom levels.

The Open Group Architecture Framework - enterprise architecture methodology with Architecture Development Method (ADM), content framework, and reference models for business transformation.

Open and independent enterprise architecture modeling language by The Open Group. Provides uniform representation across business, application, and technology layers with standardized viewpoints.

Two-dimensional classification schema for organizing enterprise architecture artifacts. Six interrogatives (what, how, where, who, when, why) across six perspectives (planner to operator).

Ministry of Defence Architecture Framework (withdrawn 15 Jan 2021). Former UK defence framework now superseded by the NATO Architecture Framework (NAF) V4.

Successor to MODAF with updated guidance for defence/mission architectures. NATO-published (see official site, ~100 pages) and encourages ArchiMate for viewpoint modeling.

Open-source tool for creating diagrams from plain text. Supports UML, C4, ERD, sequence, class, and many other diagram types with text-based syntax.

JavaScript-based diagramming tool that renders Markdown-inspired text definitions. Integrates with GitHub, GitLab, and documentation tools.

Unified Modeling Language - standardized visual modeling language with 14 diagram types including class, sequence, activity, use case, and state diagrams.

Enterprise architecture management platform with dynamic modeling, dependency mapping, and change impact analysis. Connects architecture to business outcomes.

Business Process Model and Notation - graphical representation for specifying business processes, workflows, and orchestrations.

Entity Relationship Diagram - visual representation of database schema showing entities, attributes, and relationships between data.

Scaled Agile Framework - enterprise-scale agile methodology for coordinating multiple teams. Features Agile Release Trains (ARTs), Program Increments (PIs), and portfolio management.

Iterative agile framework with sprints, defined roles (Product Owner, Scrum Master, Dev Team), ceremonies (standup, planning, review, retro), and artifacts (backlog, increment).

Visual workflow management with WIP limits, continuous flow, and pull-based work. Focus on visualizing work, limiting work-in-progress, and optimizing flow efficiency.

Describes system architecture using five concurrent views: logical, process, development, physical, and scenarios (use cases).

Organizes system into layers where each layer provides services to the layer above and uses services from the layer below.

Also known as Ports and Adapters, creates loosely coupled application components that can be easily connected to their software environment.

Separates software elements into rings, with dependencies pointing inward toward policies (business rules) and away from details (frameworks, databases).

Architecture Decision Records document important architectural decisions with context, decision, and consequences.

The workflow for creating, reviewing, and maintaining Architecture Decision Records throughout a project lifecycle.

A chronological record of all architectural decisions, providing traceability and context for future changes.

Structured descriptions of quality attribute requirements including stimulus, response, and response measure.

Approaches to handle growth in users, data, or transaction volume including horizontal and vertical scaling.

Techniques for ensuring system uptime including redundancy, failover, and graceful degradation.

Defense-in-depth approach with multiple security layers including authentication, authorization, encryption, and monitoring.

Strategies for improving system performance including caching, load balancing, and asynchronous processing.