Files
tom_analysis_agent/skills/operating-capabilities/assets/sources.yaml

83 lines
3.5 KiB
YAML

# The register of frameworks the capability catalogue cites.
#
# A capability's entry is written in our own words. A framework is named as a
# source, by the title of the part drawn on, and never quoted. `status` says
# whether a person has checked the entry's references against the framework:
# every reference here was drafted from general knowledge of the framework and is
# `unverified` until someone has.
schema_version: 1
status: unverified
frameworks:
itil-4:
name: ITIL 4
publisher: PeopleCert
version: "4"
licence: Proprietary; cited by practice name, not reproduced.
google-sre:
name: "Site Reliability Engineering: How Google Runs Production Systems"
publisher: Google / O'Reilly
version: "2016"
licence: Published under a no-derivatives licence; cited by chapter title, not reproduced.
finops-framework:
name: FinOps Framework
publisher: FinOps Foundation
version: "2024"
licence: Openly licensed with attribution; cited by capability name.
nist-csf-2:
name: NIST Cybersecurity Framework
publisher: National Institute of Standards and Technology
version: "2.0"
licence: Public domain; cited by function and category.
iso-20000-1:
name: ISO/IEC 20000-1
publisher: ISO/IEC
version: "2018"
licence: Proprietary; cited by requirement title, not reproduced.
iso-27001:
name: ISO/IEC 27001
publisher: ISO/IEC
version: "2022"
licence: Proprietary; cited by control theme, not reproduced.
eu-dora:
# The EU regulation. Not the DevOps Research and Assessment programme's metrics.
name: Regulation (EU) 2022/2554, the Digital Operational Resilience Act
publisher: European Union
version: "2022"
licence: Public law; cited by article.
dora-metrics:
# The research programme's delivery metrics. Not the EU regulation above.
name: DevOps Research and Assessment (DORA) software delivery metrics
publisher: Google Cloud
version: "2023"
licence: Publicly published research; cited by metric name.
# Socio-technical and organisational frameworks: how people, teams and
# responsibilities are structured around what is operated.
team-topologies:
name: "Team Topologies: Organizing Business and Technology Teams for Fast Flow"
publisher: Matthew Skelton and Manuel Pais, IT Revolution
version: "2019"
licence: Proprietary; cited by the names of its team types and interaction modes, not reproduced.
platform-as-a-product:
# The practice of running an internal platform as a product for the teams that
# use it. Cited from the CNCF's write-up of it, the most widely referenced one.
name: CNCF Platforms White Paper (platform as a product)
publisher: Cloud Native Computing Foundation, TAG App Delivery
version: "2023"
licence: Openly published; its licence is to be confirmed; cited by section, not reproduced.
# Measuring how well the work flows, at three layers. None replaces another.
space-framework:
name: "The SPACE of Developer Productivity"
publisher: Forsgren, Storey, Maddila, Zimmermann, Houck and Butler, ACM Queue
version: "2021"
licence: Published article; cited by its five dimensions, not reproduced.
devex-framework:
name: "DevEx: What Actually Drives Productivity"
publisher: Noda, Storey, Forsgren and Greiler, ACM Queue
version: "2023"
licence: Published article; cited by its three dimensions, not reproduced.
sfia:
name: Skills Framework for the Information Age
publisher: SFIA Foundation
version: "9"
licence: Proprietary; cited by skill name, not reproduced.