Skip to Content
MetamodelEnvironmentsEnvironment Fields

Environment Fields


1. Description

  • What it’s for: A description of this environment — its purpose, characteristics, and role in the solution delivery.

  • What to include:

    • What this environment is used for.
    • Who has access and under what conditions.
    • Any notable characteristics — e.g. data restrictions, scale differences from Production, or specific configuration.
  • Examples:

    • "Development environment used by the internal engineering team. Shared environment with synthetic data only. Deployed to Azure UK South. Accessible via VPN."
    • "Production environment serving live customer traffic. Hosted on Azure UK South with geo-redundancy to UK West. Governed by the change management policy — all deployments require a change request."
    • "User Acceptance Testing environment. Configured to mirror Production scale. Used by the business acceptance team and third-party integration partners for pre-go-live validation."

Relationships

Physical Model

RelationshipWhat to link
Contains TechnologyTechnologies running in this environment (e.g. the specific versions of runtimes, databases, platforms deployed here)
Contains ApplicationApplications deployed to this environment
Contains ServiceBackend services running in this environment
Contains APIAPIs deployed and accessible in this environment
Contains StreamEvent streams and message queues operating in this environment
Contains Data StoreData stores hosted in this environment
Contains Infrastructure EnvironmentChild infrastructure environments — use this for hierarchical decomposition (e.g. a Production environment containing region-specific infrastructure environments)

Quality

RelationshipWhat to link
Uses DeployabilityThe deployment mechanism for this environment — the CI/CD pipeline, IaC tooling, or release process used to deploy into it

Work

RelationshipWhat to link
Has TaskTasks related to completing or updating the environment specification
Has Acceptance CriteriaBusiness acceptance criteria for this environment
Has Implementation Acceptance CriteriaTechnical criteria for verifying the environment is correctly set up and configured
Has FAQFrequently asked questions about this environment

RAID

RelationshipWhat to link
Has RiskRisks associated with this environment (e.g. single-region deployment risk, access control gaps, data residency risk)
Has AssumptionAssumptions made about this environment (e.g. assumed hosting platform, assumed access controls)
Has IssueKnown issues affecting this environment

Reference

RelationshipWhat to link
Implements Business ReferenceStandards, policies, or regulatory documents that govern this environment (e.g. change management policy, security baseline, data residency requirements)
Last updated on