Skip to content
Blueprint Catalog

    ↑↓ move · Enter open · Esc close

    05 — Library · 47 frameworks and standards

    Frameworks

    Frameworks, standards, notations and methods an architect meets, and when each is worth reaching for.

    Frameworks

    Showing 9 of 47 frameworks and standards

    • FW-450

      ACORD Standards

      Standard

      ACORD

      A family of insurance industry data standards maintained by a nonprofit association of carriers, brokers and vendors: standard forms, message formats for exchanging policy, billing and claim data between distribution partners and carriers, and information and data models that define insurance concepts in shared terms.

      Use · Reach for it when exchanging data between agencies, brokers, carriers and reinsurers, or when seeding an insurance data model. Full access to the specifications generally needs membership, and each trading partner still agrees its own implementation profile.

      Governs · Insurance Products & Policy,Insurance Claims

      Terms · Reference Model,Master Data

      Related · IEC Common Information Model (CIM),DAMA-DMBOK

      Official page ↗

    • FW-290

      APQC Process Classification Framework

      Reference Model

      APQC

      A cross-industry taxonomy of business processes arranged in levels from categories down to activities and tasks, with industry-specific variants and process definitions, used as a common reference for process documentation and benchmarking.

      Use · Reach for it as a checklist when building a process inventory or comparing performance. It classifies processes, not capabilities; copying its categories into a capability map produces verbs where nouns belong.

      Governs · Process Architecture & Ownership

      Terms · Business Process,Reference Model

      Related · BPMN,TM Forum Business Process Framework (eTOM),BIZBOK Guide

      Official page ↗

    • FW-120

      arc42

      Method

      arc42 (Gernot Starke, Peter Hruschka)

      An open template for documenting software architecture in twelve sections, from goals, constraints and context through building blocks, runtime and deployment views to decisions, quality requirements, risks and a glossary.

      Use · Use it to give every system's documentation the same shape so readers know where to look. It structures the document but not the thinking; empty sections are a sign to trim, not to fill.

      Governs · Solution Design

      Terms · Architecture Decision Record,Building Block

      Related · C4 Model,ISO/IEC/IEEE 42010

      Official page ↗

    • FW-020

      ArchiMate

      Notation

      The Open Group

      A modeling language for enterprise architecture with a defined set of elements and relationships across strategy, business, application, technology and implementation layers, so one model can show how a capability is realized all the way down to infrastructure.

      Use · Use it when several architects must draw cross-layer views that a tool can check and reuse. Its rigor is the price: readers need some training, and executive audiences usually want a simplified view drawn from the model.

      Governs · Business Architecture,Application & Technology Architecture

      Terms · Viewpoint,Enterprise Architecture,Business Capability

      Related · TOGAF Standard,BPMN,UML,ISO/IEC/IEEE 42010

      Official page ↗

    • FW-260

      AsyncAPI

      Standard

      AsyncAPI Initiative

      A machine-readable format for describing message-driven and event-driven APIs: channels, operations, messages, payload schemas and protocol bindings for brokers such as Kafka, AMQP and MQTT. Its structure is deliberately close to OpenAPI.

      Use · Use it to document and govern event contracts the way OpenAPI does for HTTP. Tool support is thinner than for OpenAPI, and it does not replace a schema registry for runtime compatibility checks.

      Governs · Integration & API Delivery,API Design & Governance

      Terms · Event-Driven Architecture,API,Integration Pattern

      Related · OpenAPI Specification

      Official page ↗

    • FW-190

      AWS Well-Architected Framework

      Framework

      Amazon Web Services

      Design guidance for workloads on AWS, organized into six pillars: operational excellence, security, reliability, performance efficiency, cost optimization and sustainability, each with design principles and review questions.

      Use · Use it to run structured workload reviews before launch or after incidents. Its questions apply widely, but its answers assume AWS services, and a review finds risks without prioritizing them for you.

      Governs · Cloud Platform Operations,Solution Design

      Related · Azure Well-Architected Framework,Google Cloud Well-Architected Framework,FinOps Framework

      Official page ↗

    • FW-200

      Azure Well-Architected Framework

      Framework

      Microsoft

      Design guidance for workloads on Azure, organized into five pillars: reliability, security, cost optimization, operational excellence and performance efficiency, with design principles, checklists, tradeoff notes and service-specific guides.

      Use · Use it for workload design reviews on Azure and to make pillar tradeoffs explicit. Platform-level concerns such as landing zones and governance sit in separate Microsoft guidance.

      Governs · Cloud Platform Operations,Solution Design

      Terms · Landing Zone

      Related · AWS Well-Architected Framework,Google Cloud Well-Architected Framework,FinOps Framework

      Official page ↗

    • FW-470

      BCBS 239

      Standard

      Basel Committee on Banking Supervision

      The Basel Committee's principles for how banks gather, reconcile and report risk data, published in 2013 for systemically important banks. They cover governance and data architecture, the accuracy, completeness and timeliness of aggregation, the quality of risk reports, and how supervisors review all of this.

      Use · Reach for it to justify and scope risk data lineage, reconciliation and data ownership in a bank. It sets outcomes, not a data model or tooling, and supervisors judge compliance by evidence that reports can be produced quickly and correctly under stress.

      Governs · Risk Data Aggregation,Supervisory Data Requests,Data Ownership & Stewardship,Data Quality Management

      Terms · Data Lineage,Data Governance,System of Record

      Related · DAMA-DMBOK,BIAN

      Official page ↗

    • FW-440

      BIAN

      Reference Model

      Banking Industry Architecture Network (BIAN)

      A reference architecture for banking published by a member association of banks and vendors. It divides the bank into fine-grained, non-overlapping service domains, each owning one business responsibility, and pairs them with business objects and semantic API definitions so banks and vendors can describe systems in common terms.

      Use · Use it to partition a banking application landscape, test vendor scope against a neutral map and shape service and API boundaries. It is granular and large, and most banks map to it rather than adopt it. It starts from service domains; recent releases add a business capability model alongside them.

      Governs · Deposits & Accounts,Lending & Credit,Payments & Cards,Wealth & Investment Management,Financial Crime,Prudential Risk & Regulatory Reporting

      Terms · Reference Model,Bounded Context,API

      Related · ISO 20022,TM Forum Business Process Framework (eTOM),ArchiMate,OpenAPI Specification

      Official page ↗