mocop
Browse · Docs · Guide · Analyze

Blueprint Catalog API

API by Mike Reams · rest

Every path is a static file, rebuilt at each release: public, read-only, no key. The schemas are inferred from the files served, so a key is required only where every record has it and nothing is closed; a later release may add keys. version in each answer is the catalog release. Content is CC BY 4.0 © Mike Reams; cite the canonical or url in each answer.

Endpoint: https://catalog.mikereams.com/

Verification: observed. Source: crawl.

Capabilities (42)

  • Anti-patterns each with the patterns that cure it
  • Books with the capabilities each teaches
  • Every business capability flattened
  • One business capability with ancestors children and crosswalk
  • Every release and what it added removed and renamed
  • Data concepts each with the capability that masters it and those that use it
  • What was added removed and renamed between release {from} and the current…
  • Domain events each with the stage that raises it and the capabilities that…
  • One worked example with its applications coverage overlaps gaps and…
  • Worked examples (fictional portfolios)
  • Export file README.md
  • Export file archimate.xml
  • Export file ardoq-capabilities.csv
  • Export file blueprint-radar.csv
  • Export file capabilities.csv
  • The export files with sizes
  • Export file leanix-business-capabilities.csv
  • Export file product-capability-map.csv
  • Export file servicenow-business-capabilities.csv
  • Frameworks and standards each with the capabilities it governs
  • The glossary
  • One glossary term
  • The industries the catalog covers
  • One industry with its L1s value streams products technology categories and…
  • The eight macro domains (the executive layer)
About · Contact · Privacy