Organization, requirements, and bounded contexts

These concepts establish who wants the system, what outcomes matter, what the organization can do, and where language or ownership boundaries lie.

Source: mde/metamodels/cim/cim-organization.emf.

Requirement

Represents requirement in the CIM vocabulary. It specializes TraceableElement with the details needed for this modeling concern.

Direct supertypes: TraceableElement. Inherited attributes and marker capabilities are documented in the shared kernel; this section lists every attribute declared by this class.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
mandatory	Boolean [1]	Whether delivery is required for the modeled scope. This is the distinction between a real obligation and useful context, and it influences readiness decisions. Semantic validation: RequirementHasFitCriterionOrAcceptanceCriteria (requirement has fit criterion or acceptance criteria) in mde/validation/cim/rules/organization-intent.evl the feature participates in a semantic validation condition. ProductionBlockingRequirementIsMandatory (production blocking requirement is mandatory) in mde/validation/cim/rules/organization-intent.evl the flag must be enabled for this rule to pass. Transformation role: ETL rule Requirement2BusinessRule in mde/transformations/cim-to-pim/root-scaffolding.etl reads or derives this feature while refining Requirement.	Either true or false. Example: false.
productionBlocking	Boolean [1]	Whether failure to satisfy the requirement must stop production readiness. It separates a release gate from a requirement that may be consciously deferred. Semantic validation: ProductionBlockingRequirementIsMandatory (production blocking requirement is mandatory) in mde/validation/cim/rules/organization-intent.evl the flag must be enabled for this rule to pass. Transformation role: ETL rule Requirement2BusinessRule in mde/transformations/cim-to-pim/root-scaffolding.etl reads or derives this feature while refining Requirement.	Either true or false. Example: true.
fitCriterion	String [1]	The observable condition by which stakeholders decide that the requirement has been met; without it, a requirement cannot be reviewed consistently after transformation. Semantic validation: RequirementHasFitCriterionOrAcceptanceCriteria (requirement has fit criterion or acceptance criteria) in mde/validation/cim/rules/organization-intent.evl the value must be present and non-blank.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: At least 95% of confirmed orders complete within 2 minutes..
requirementType	RequirementType [1]	The kind of obligation being modeled, behavior, quality, security, privacy, compliance, or governance, so downstream rules can apply the appropriate interpretation.	Exactly one of: FUNCTIONAL, BUSINESS_RULE, QUALITY, SECURITY, PRIVACY, COMPLIANCE, AUDIT, REPORTING, DATA_GOVERNANCE. Example: FUNCTIONAL.
sourceType	RequirementSourceType [1]	Where the requirement came from, such as a stakeholder, regulation, workshop, existing system, or explicit assumption. Provenance matters when its authority is questioned. Generation role: The artifact generator references this feature in mde/generation/awspsm-to-artifacts/lib/trace.eol. The artifact generator references this feature in mde/generation/awspsm-to-artifacts/lib/validation.eol.	Exactly one of: STAKEHOLDER, REGULATION, POLICY_DOCUMENT, WORKSHOP, EXISTING_SYSTEM, ASSUMPTION, AI_ASSISTANT. Example: STAKEHOLDER.
priority	Priority [1]	The relative urgency of the requirement within the increment. It helps reviewers order unresolved work without confusing priority with mandatory production blocking.	Exactly one of: LOW, MEDIUM, HIGH, CRITICAL. Example: LOW.

Relationships

Relationship	Kind and multiplicity	Meaning in the model
acceptanceCriteria → AcceptanceCriterion	containment, [*]	Contains the acceptance criterion element(s) that make up this requirement; the contained objects belong to this model element.
supportsGoals → BusinessGoal	reference, [*]	References the business goal element(s) used as supports goals by this requirement; the target may be shared elsewhere in the model.
constrains → ModelElement	reference, [*]	References the model element element(s) used as constrains by this requirement; the target may be shared elsewhere in the model.
dependsOn → Requirement	reference, [*]	References the requirement element(s) used as depends on by this requirement; the target may be shared elsewhere in the model.
conflictsWith → Requirement	reference, [*]	References the requirement element(s) used as conflicts with by this requirement; the target may be shared elsewhere in the model.

RequirementRelationship

Represents requirement relationship in the CIM vocabulary. It specializes SemanticRelationship with the details needed for this modeling concern.

Direct supertypes: SemanticRelationship. Inherited attributes and marker capabilities are documented in the shared kernel; this section lists every attribute declared by this class.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
rationale	String [1]	The reason two requirements are related. Recording it prevents a dependency, conflict, refinement, or duplicate link from becoming an unexplained diagram line. Generation role: The artifact generator references this feature in mde/generation/awspsm-to-artifacts/awspsm2artifacts.egx. The artifact generator references this feature in mde/generation/awspsm-to-artifacts/lib/validation.eol.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: The choice protects the business outcome while keeping the design independently deployable..
blocking	Boolean [1]	Whether this relationship itself blocks progress, for example, an unresolved conflict or dependency, rather than merely documenting a useful connection. Generation role: The artifact generator references this feature in mde/generation/awspsm-to-artifacts/lib/trace.eol. The artifact generator references this feature in mde/generation/awspsm-to-artifacts/lib/validation.eol.	Either true or false. Example: false.
kind	RequirementRelationshipKind [1]	The precise semantics of the requirement link. A REFINES link carries a different transformation and review meaning from CONFLICTS_WITH or DERIVES_FROM.	Exactly one of: DEPENDS_ON, CONFLICTS_WITH, REFINES, DUPLICATES, DERIVES_FROM. Example: DEPENDS_ON.

Relationships

Relationship	Kind and multiplicity	Meaning in the model
source → Requirement	reference, [1]	References the requirement element(s) used as source by this requirement relationship; the target may be shared elsewhere in the model.
target → Requirement	reference, [1]	References the requirement element(s) used as target by this requirement relationship; the target may be shared elsewhere in the model.

AcceptanceCriterion

Represents acceptance criterion in the CIM vocabulary. It specializes TraceableElement with the details needed for this modeling concern.

Direct supertypes: TraceableElement. Inherited attributes and marker capabilities are documented in the shared kernel; this section lists every attribute declared by this class.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
givenContext	String [1]	The precondition under which the requirement is evaluated. It anchors the test in a recognizable business situation instead of an implementation state. Semantic validation: AcceptanceCriterionUsesGivenWhenThen (acceptance criterion uses given when then) in mde/validation/cim/rules/organization-intent.evl the value must be present and non-blank.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Orders processing.
whenAction	String [1]	The event or action that exercises the requirement, forming the executable middle of a Given/When/Then statement. Semantic validation: AcceptanceCriterionUsesGivenWhenThen (acceptance criterion uses given when then) in mde/validation/cim/rules/organization-intent.evl the value must be present and non-blank.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Acceptance Criterion When Action.
thenOutcome	String [1]	The business-observable result that must follow the action; it is more useful than a technical assertion because it can survive model refinement. Semantic validation: AcceptanceCriterionUsesGivenWhenThen (acceptance criterion uses given when then) in mde/validation/cim/rules/organization-intent.evl the value must be present and non-blank.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Acceptance Criterion Then Outcome.
measurableTarget	String [1]	A numeric or otherwise verifiable threshold for the outcome, allowing a reviewer or generated test to decide pass/fail without interpretation. Semantic validation: AutomatableAcceptanceCriterionHasTarget (automatable acceptance criterion has target) in mde/validation/cim/rules/organization-intent.evl the value must be present and non-blank.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Acceptance Criterion Measurable Target.
automatableTestCandidate	Boolean [1]	Whether the criterion is sufficiently precise to become an automated test candidate. It highlights where human judgment or further clarification is still required. Semantic validation: AutomatableAcceptanceCriterionHasTarget (automatable acceptance criterion has target) in mde/validation/cim/rules/organization-intent.evl the flag must be enabled for this rule to pass.	Either true or false. Example: false.

Relationships

This class declares no direct relationships.

BusinessGoal

Represents business goal in the CIM vocabulary. It specializes TraceableElement with the details needed for this modeling concern.

Direct supertypes: TraceableElement. Inherited attributes and marker capabilities are documented in the shared kernel; this section lists every attribute declared by this class.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
successCriterion	String [1]	The outcome that makes the goal successful, expressed before architecture is chosen so the PIM and PSM remain accountable to business value. Semantic validation: BusinessGoalHasSuccessCriterion (business goal has success criterion) in mde/validation/cim/rules/organization-intent.evl the value must be present and non-blank.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: At least 95% of confirmed orders complete within 2 minutes..
timeHorizon	String [1]	When the goal is expected to matter, such as this quarter, launch, or a multi-year horizon, so urgency is not confused with the goal's intrinsic value.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Business Goal Time Horizon.
businessValue	String [1]	The benefit created by achieving the goal, giving capability and architecture decisions a reason beyond technical completeness. Semantic validation: BusinessGoalExplainsValueAndRisk (business goal explains value and risk) in mde/validation/cim/rules/organization-intent.evl the value must be present and non-blank.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: READY.
failureConsequence	String [1]	The business cost of missing the goal. It exposes risk that may not appear in functional requirements and supports prioritization of readiness work. Semantic validation: BusinessGoalExplainsValueAndRisk (business goal explains value and risk) in mde/validation/cim/rules/organization-intent.evl the value must be present and non-blank.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Business Goal Failure Consequence.
priority	Priority [1]	Records precedence value for priority for business goal. It keeps deterministic ordering or precedence explicit during review and transformation, so later steps do not have to infer it. Semantic validation: CriticalGoalHasOwnerAndKpi (critical goal has owner and kpi) in mde/validation/cim/rules/organization-intent.evl the feature participates in a semantic validation condition.	Exactly one of: LOW, MEDIUM, HIGH, CRITICAL. Example: LOW.

Relationships

Relationship	Kind and multiplicity	Meaning in the model
measuredBy → KPI	reference, [*]; opposite measures	References the kpi element(s) used as measured by by this business goal; the target may be shared elsewhere in the model.
refinedBy → BusinessCapability	reference, [*]	References the business capability element(s) used as refined by by this business goal; the target may be shared elsewhere in the model.
owners → Stakeholder	reference, [*]; opposite ownsGoals	References the stakeholder element(s) used as owners by this business goal; the target may be shared elsewhere in the model.

KPI

Represents kpi in the CIM vocabulary. It specializes TraceableElement with the details needed for this modeling concern.

Direct supertypes: TraceableElement. Inherited attributes and marker capabilities are documented in the shared kernel; this section lists every attribute declared by this class.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
metricName	String [1]	The human-recognizable name of the measure used to judge a goal, such as order completion rate or grant-processing latency. Semantic validation: KPIIsMeasurable (kpiis measurable) in mde/validation/cim/rules/organization-intent.evl the value must be present and non-blank. Transformation role: ETL rule KPI2ReadinessCheck in mde/transformations/cim-to-pim/root-scaffolding.etl assigns or materializes this feature while refining KPI. Generation role: The artifact generator references this feature in mde/generation/awspsm-to-artifacts/lib/cfn.eol.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: KPIExample.
metricDefinition	String [1]	The exact population, numerator, denominator, and observation rule for the metric. It prevents teams from reporting the same KPI with incompatible calculations. Semantic validation: KPIHasMeasurementMethod (kpihas measurement method) in mde/validation/cim/rules/organization-intent.evl the value must be present and non-blank. KPIHasRecognisableOperator (kpihas recognisable operator) in mde/validation/cim/rules/organization-intent.evl the value must satisfy a numeric or ordering boundary.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: A confirmed order is one accepted for fulfillment by the business..
operator	String [1]	The comparison operation used to evaluate the target, such as >=, <=, or =; it gives the acceptance threshold an unambiguous direction. Semantic validation: KPIHasMeasurementMethod (kpihas measurement method) in mde/validation/cim/rules/organization-intent.evl the feature participates in a semantic validation condition. KPIHasRecognisableOperator (kpihas recognisable operator) in mde/validation/cim/rules/organization-intent.evl the value must be present and non-blank. Generation role: The artifact generator references this feature in mde/generation/awspsm-to-artifacts/lib/iam.eol. The artifact generator references this feature in mde/generation/awspsm-to-artifacts/lib/values.eol.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: >=.
targetValue	String [1]	The desired value of the metric, retained as business intent before a concrete monitoring implementation exists. Semantic validation: KPIIsMeasurable (kpiis measurable) in mde/validation/cim/rules/organization-intent.evl the value must be present and non-blank. Transformation role: ETL rule KPI2ReadinessCheck in mde/transformations/cim-to-pim/root-scaffolding.etl assigns or materializes this feature while refining KPI.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: READY.
unit	String [1]	The unit in which the metric is measured, percent, seconds, currency, count, or another domain unit, so a bare target value cannot be misinterpreted. Semantic validation: KPIIsMeasurable (kpiis measurable) in mde/validation/cim/rules/organization-intent.evl the value must be present and non-blank.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: milliseconds.
measurementFrequency	String [1]	How often the measure is evaluated. This influences whether an eventual CloudWatch metric, report, or human review can provide timely feedback. Semantic validation: KPIHasMeasurementMethod (kpihas measurement method) in mde/validation/cim/rules/organization-intent.evl the value must be present and non-blank.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: PT5M.
dataSource	String [1]	The authoritative source from which the metric is calculated, preserving the accountability chain from business goal to operational evidence. Semantic validation: KPIHasMeasurementMethod (kpihas measurement method) in mde/validation/cim/rules/organization-intent.evl the value must be present and non-blank. Transformation role: ETL rule KPI2ReadinessCheck in mde/transformations/cim-to-pim/root-scaffolding.etl assigns or materializes this feature while refining KPI.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Kpi Data Source.
acceptanceThreshold	String [1]	The tolerance around the target that distinguishes acceptable variation from failure; it is especially important for noisy operational measures.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Kpi Acceptance Threshold.

Relationships

Relationship	Kind and multiplicity	Meaning in the model
measures → BusinessGoal	reference, [?]; opposite measuredBy	References the business goal element(s) used as measures by this kpi; the target may be shared elsewhere in the model.

Stakeholder

Represents stakeholder in the CIM vocabulary. It specializes TraceableElement with the details needed for this modeling concern.

Direct supertypes: TraceableElement. Inherited attributes and marker capabilities are documented in the shared kernel; this section lists every attribute declared by this class.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
stakeholderType	String [1]	Stores the controlled classification or strategy represented by stakeholder type on the stakeholder. The field keeps the model explicit and reviewable during review and transformation instead of leaving the decision to an inferred default. Semantic validation: StakeholderConcernIsDeclared (stakeholder concern is declared) in mde/validation/cim/rules/organization-intent.evl the value must be present and non-blank.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: BUSINESS.
concern	String [1]	Stores the reasoning behind concern on the stakeholder. The field records design review and decision traceability as an explicit, reviewable input. Semantic validation: StakeholderConcernIsDeclared (stakeholder concern is declared) in mde/validation/cim/rules/organization-intent.evl the value must be present and non-blank. Transformation role: ETL rule Stakeholder2ManualDecision in mde/transformations/cim-to-pim/root-scaffolding.etl assigns or materializes this feature while refining Stakeholder.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Customer privacy and fulfillment reliability..
influenceLevel	String [1]	Records the influence level value for the stakeholder. This keeps the decision explicit even when the element's class or relationships remain unchanged. The repository contains no direct EVL rule, ETL assignment, or artifact-generator read for this declared field. For now, it remains a model-level fact for review and future refinement.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: INFO.
contactRole	String [1]	For a stakeholder, the model records the contact role value. Keeping the fact with its owning element lets validation and refinement inspect it before artifact generation. Transformation role: ETL rule Stakeholder2ManualDecision in mde/transformations/cim-to-pim/root-scaffolding.etl assigns or materializes this feature while refining Stakeholder.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: order-manager.

Relationships

Relationship	Kind and multiplicity	Meaning in the model
ownsGoals → BusinessGoal	reference, [*]; opposite owners	References the business goal element(s) used as owns goals by this stakeholder; the target may be shared elsewhere in the model.
providesRequirements → Requirement	reference, [*]	References the requirement element(s) used as provides requirements by this stakeholder; the target may be shared elsewhere in the model.

Actor

Represents actor in the CIM vocabulary. It specializes TraceableElement with the details needed for this modeling concern.

Direct supertypes: TraceableElement. Inherited attributes and marker capabilities are documented in the shared kernel; this section lists every attribute declared by this class.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
organizationBoundary	String [1]	The organizational boundary in which the actor operates. It helps distinguish internal responsibility from a partner, regulator, or external system crossing the domain boundary.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: orders-team.
authenticationExpectation	String [1]	The business expectation for proving who the actor is. It is an input to PIM identity and authentication modeling, not an AWS mechanism by itself. Semantic validation: ExternalActorDeclaresAuthExpectations (external actor declares auth expectations) in mde/validation/cim/rules/organization-intent.evl the value must be present and non-blank. Transformation role: ETL rule Actor2Principal in mde/transformations/cim-to-pim/boundaries-security.etl reads or derives this feature while refining Actor. ETL rule Actor2Principal in mde/transformations/cim-to-pim/boundaries-security.etl assigns or materializes this feature while refining Actor.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Actor Authentication Expectation.
authorizationExpectation	String [1]	The business expectation for what the actor may do after authentication; it preserves the distinction between identity and permission. Semantic validation: ExternalActorDeclaresAuthExpectations (external actor declares auth expectations) in mde/validation/cim/rules/organization-intent.evl the value must be present and non-blank. Transformation role: ETL rule Actor2Principal in mde/transformations/cim-to-pim/boundaries-security.etl assigns or materializes this feature while refining Actor.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Actor Authorization Expectation.
interactionExpectation	InteractionExpectation [1]	Whether the actor needs an immediate response, delayed response, notification, back-office handling, or human review. This shapes synchronous versus asynchronous refinement.	Exactly one of: IMMEDIATE_RESPONSE_EXPECTED, RESPONSE_CAN_BE_DELAYED, NOTIFICATION_EXPECTED, BACK_OFFICE_PROCESSING, HUMAN_REVIEW_REQUIRED. Example: IMMEDIATE_RESPONSE_EXPECTED.
actorType	ActorType [1]	The role the participant plays in the domain, human, organization, department, external system, time, or regulator, so behavior is not designed around an incorrect caller assumption. Semantic validation: ActorHasTypeAndTrustLevel (actor has type and trust level) in mde/validation/cim/rules/organization-intent.evl the related value or object must be explicitly provided. HumanActorHasRole (human actor has role) in mde/validation/cim/rules/organization-intent.evl the feature participates in a semantic validation condition. Transformation role: ETL rule Actor2Principal in mde/transformations/cim-to-pim/boundaries-security.etl assigns or materializes this feature while refining Actor.	Exactly one of: HUMAN, ORGANIZATION, DEPARTMENT, EXTERNAL_ORGANIZATION, EXTERNAL_SYSTEM, TIME, REGULATOR. Example: HUMAN.
trustLevel	TrustLevel [1]	The trust boundary assigned to the actor. External or regulated actors trigger stronger authorization, audit, and data-handling expectations in semantic validation. Semantic validation: ActorHasTypeAndTrustLevel (actor has type and trust level) in mde/validation/cim/rules/organization-intent.evl the related value or object must be explicitly provided. ExternalActorDeclaresAuthExpectations (external actor declares auth expectations) in mde/validation/cim/rules/organization-intent.evl the feature participates in a semantic validation condition. Transformation role: ETL rule Actor2Principal in mde/transformations/cim-to-pim/boundaries-security.etl assigns or materializes this feature while refining Actor.	Exactly one of: TRUSTED_INTERNAL, PARTIALLY_TRUSTED, UNTRUSTED_EXTERNAL, REGULATED_EXTERNAL. Example: TRUSTED_INTERNAL.

Relationships

Relationship	Kind and multiplicity	Meaning in the model
playsRoles → Role	reference, [*]; opposite assignedTo	References the role element(s) used as plays roles by this actor; the target may be shared elsewhere in the model.
issuesCommands → Command	reference, [*]; opposite issuedBy	References the command element(s) used as issues commands by this actor; the target may be shared elsewhere in the model.
issuesQueries → Query	reference, [*]; opposite issuedBy	References the query element(s) used as issues queries by this actor; the target may be shared elsewhere in the model.
observesEvents → BusinessEvent	reference, [*]	References the business event element(s) used as observes events by this actor; the target may be shared elsewhere in the model.

Role

Represents role in the CIM vocabulary. It specializes TraceableElement with the details needed for this modeling concern.

Direct supertypes: TraceableElement. Inherited attributes and marker capabilities are documented in the shared kernel; this section lists every attribute declared by this class.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
responsibility	String [1]	Stores the accountable person, team, or identity for responsibility on the role. The field records accountability and access review as an explicit, reviewable input. Semantic validation: PrivilegedRoleHasPermissionSummary (privileged role has permission summary) in mde/validation/cim/rules/organization-intent.evl the value must be present and non-blank. RoleAssignedToActor (role assigned to actor) in mde/validation/cim/rules/organization-intent.evl the feature participates in a semantic validation condition.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Reserve inventory for a confirmed order..
businessPermissionSummary	String [1]	Records the business permission summary value for role. It keeps this decision explicit during review and transformation, so later steps do not have to infer it. Semantic validation: PrivilegedRoleHasPermissionSummary (privileged role has permission summary) in mde/validation/cim/rules/organization-intent.evl the value must be present and non-blank. Transformation role: ETL rule Role2Principal in mde/transformations/cim-to-pim/boundaries-security.etl reads or derives this feature while refining Role. ETL rule Role2Principal in mde/transformations/cim-to-pim/boundaries-security.etl assigns or materializes this feature while refining Role.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Role Business Permission Summary.
privileged	Boolean [1]	Records whether privileged applies to role. It preserves an explicit architectural or governance decision through review and transformation, so later steps do not have to infer it. Semantic validation: PrivilegedRoleHasPermissionSummary (privileged role has permission summary) in mde/validation/cim/rules/organization-intent.evl the flag must be enabled for this rule to pass. Transformation role: ETL rule Role2Principal in mde/transformations/cim-to-pim/boundaries-security.etl assigns or materializes this feature while refining Role.	Either true or false. Example: false.

Relationships

Relationship	Kind and multiplicity	Meaning in the model
assignedTo → Actor	reference, [*]; opposite playsRoles	References the actor element(s) used as assigned to by this role; the target may be shared elsewhere in the model.

ExternalSystem

Represents external system in the CIM vocabulary. It specializes Actor with the details needed for this modeling concern.

Direct supertypes: Actor. Inherited attributes and marker capabilities are documented in the shared kernel; this section lists every attribute declared by this class.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
owningOrganization	String [1]	The organization accountable for the external system, useful when ownership, escalation, or data-sharing responsibility differs from the system's name. Semantic validation: ExternalSystemDeclaresPurposeAndTrust (external system declares purpose and trust) in mde/validation/cim/rules/organization-intent.evl the value must be present and non-blank. Transformation role: ETL rule ExternalSystem2Adapter in mde/transformations/cim-to-pim/boundaries-security.etl assigns or materializes this feature while refining ExternalSystem.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: orders-team.
businessPurpose	String [1]	Why the domain interacts with the system. It keeps an integration tied to a business capability rather than allowing an endpoint to become an unexplained technical dependency. Semantic validation: ExternalSystemDeclaresPurposeAndTrust (external system declares purpose and trust) in mde/validation/cim/rules/organization-intent.evl the value must be present and non-blank. Transformation role: ETL rule ExternalSystem2Adapter in mde/transformations/cim-to-pim/boundaries-security.etl assigns or materializes this feature while refining ExternalSystem.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Reserve inventory for a confirmed order..
trustRationale	String [1]	The argument for the system's trust level, including contractual, operational, or regulatory grounds for allowing it into a business flow. Semantic validation: ExternalSystemDeclaresPurposeAndTrust (external system declares purpose and trust) in mde/validation/cim/rules/organization-intent.evl the value must be present and non-blank.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: The choice protects the business outcome while keeping the design independently deployable..
contractualSla	String [1]	The service promise the external party makes about availability, latency, or support. It supplies a realistic assumption for PIM resilience and timeout policies. Transformation role: ETL rule ExternalSystem2Adapter in mde/transformations/cim-to-pim/boundaries-security.etl assigns or materializes this feature while refining ExternalSystem. ETL rule ExternalSystem2Adapter in mde/transformations/cim-to-pim/boundaries-security.etl reads or derives this feature while refining ExternalSystem.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: External System Contractual Sla.
storesBusinessData	Boolean [1]	Whether data crosses the integration boundary and is retained by the external party; this is material to privacy, residency, and deletion analysis. Semantic validation: ExternalSystemDataExchangeIsExplicit (external system data exchange is explicit) in mde/validation/cim/rules/organization-intent.evl the flag must be enabled for this rule to pass.	Either true or false. Example: false.
sendsBusinessEvents	Boolean [1]	Whether the system can originate domain-significant events, distinguishing a push/event integration from a passive lookup endpoint. Semantic validation: ExternalSystemDataExchangeIsExplicit (external system data exchange is explicit) in mde/validation/cim/rules/organization-intent.evl the flag must be enabled for this rule to pass.	Either true or false. Example: false.
receivesBusinessEvents	Boolean [1]	Whether the system consumes domain events, which drives outbound delivery, retry, idempotency, and contract considerations. Semantic validation: ExternalSystemDataExchangeIsExplicit (external system data exchange is explicit) in mde/validation/cim/rules/organization-intent.evl the flag must be enabled for this rule to pass.	Either true or false. Example: false.

Relationships

Relationship	Kind and multiplicity	Meaning in the model
exchangedInformation → InformationItem	reference, [*]	References the information item element(s) used as exchanged information by this external system; the target may be shared elsewhere in the model.
producedEvents → BusinessEvent	reference, [*]; opposite causedByExternalSystems	References the business event element(s) used as produced events by this external system; the target may be shared elsewhere in the model.
consumedEvents → BusinessEvent	reference, [*]; opposite consumedByExternalSystems	References the business event element(s) used as consumed events by this external system; the target may be shared elsewhere in the model.

BusinessCapability

Represents business capability in the CIM vocabulary. It specializes TraceableElement with the details needed for this modeling concern.

Direct supertypes: TraceableElement. Inherited attributes and marker capabilities are documented in the shared kernel; this section lists every attribute declared by this class.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
maturity	String [1]	The capability's current organizational maturity, indicating whether it is stable enough to drive automation or still requires discovery and governance work.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: DEFINED.
responsibility	String [1]	The outcome the capability owns. It provides the semantic center for grouping commands, queries, entities, processes, and later serverless services. Semantic validation: CapabilitySupportsGoal (capability supports goal) in mde/validation/cim/rules/organization-intent.evl the feature participates in a semantic validation condition. CapabilityHasOwnerOrResponsibility (capability has owner or responsibility) in mde/validation/cim/rules/organization-intent.evl the value must be present and non-blank. Transformation role: ETL rule Capability2Service in mde/transformations/cim-to-pim/boundaries-security.etl assigns or materializes this feature while refining BusinessCapability.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Reserve inventory for a confirmed order..
ownerName	String [1]	The accountable business owner, kept as explicit intent even when the technical implementation is distributed across services. Semantic validation: CapabilityHasOwnerOrResponsibility (capability has owner or responsibility) in mde/validation/cim/rules/organization-intent.evl the value must be present and non-blank. Transformation role: ETL rule Capability2Service in mde/transformations/cim-to-pim/boundaries-security.etl assigns or materializes this feature while refining BusinessCapability.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: orders-team.
criticality	CapabilityCriticality [1]	How damaging capability failure would be. Criticality influences resilience, observability, governance, and the urgency of resolving transformation hotspots. Semantic validation: CriticalCapabilityHasRequirementsAndNfrs (critical capability has requirements and nfrs) in mde/validation/cim/rules/organization-intent.evl the feature participates in a semantic validation condition.	Exactly one of: SUPPORTING, IMPORTANT, CORE, MISSION_CRITICAL. Example: SUPPORTING.

Relationships

Relationship	Kind and multiplicity	Meaning in the model
owner → Actor	reference, [?]	References the actor element(s) used as owner by this business capability; the target may be shared elsewhere in the model.
supports → BusinessGoal	reference, [*]	References the business goal element(s) used as supports by this business capability; the target may be shared elsewhere in the model.
realizesRequirements → Requirement	reference, [*]	References the requirement element(s) used as realizes requirements by this business capability; the target may be shared elsewhere in the model.
containsCommands → Command	reference, [*]; opposite targetCapability	References the command element(s) used as contains commands by this business capability; the target may be shared elsewhere in the model.
containsQueries → Query	reference, [*]; opposite targetCapability	References the query element(s) used as contains queries by this business capability; the target may be shared elsewhere in the model.
containsEvents → BusinessEvent	reference, [*]	References the business event element(s) used as contains events by this business capability; the target may be shared elsewhere in the model.
managesEntities → DomainEntity	reference, [*]; opposite owningCapability	References the domain entity element(s) used as manages entities by this business capability; the target may be shared elsewhere in the model.
ownsProcesses → BusinessProcess	reference, [*]; opposite owningCapability	References the business process element(s) used as owns processes by this business capability; the target may be shared elsewhere in the model.
constrainedBy → NonFunctionalRequirement	reference, [*]	References the non functional requirement element(s) used as constrained by by this business capability; the target may be shared elsewhere in the model.

CapabilityDependency

Represents capability dependency in the CIM vocabulary. It specializes SemanticRelationship with the details needed for this modeling concern.

Direct supertypes: SemanticRelationship. Inherited attributes and marker capabilities are documented in the shared kernel; this section lists every attribute declared by this class.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
dependencyReason	String [1]	For a capability dependency, the model records the reasoning behind dependency reason. Keeping the fact with its owning element lets validation and refinement inspect it before artifact generation. Semantic validation: CapabilityDependencyIsMeaningful (capability dependency is meaningful) in mde/validation/cim/rules/organization-intent.evl the value must be present and non-blank. CriticalDependencyHasRationale (critical dependency has rationale) in mde/validation/cim/rules/organization-intent.evl the value must be present and non-blank.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Capability Dependency Dependency Reason.
criticalPath	Boolean [1]	Records whether critical path applies to capability dependency. It preserves an explicit architectural or governance decision through review and transformation, so later steps do not have to infer it. Semantic validation: CriticalDependencyHasRationale (critical dependency has rationale) in mde/validation/cim/rules/organization-intent.evl the flag must be enabled for this rule to pass.	Either true or false. Example: false.

Relationships

Relationship	Kind and multiplicity	Meaning in the model
source → BusinessCapability	reference, [1]	References the business capability element(s) used as source by this capability dependency; the target may be shared elsewhere in the model.
target → BusinessCapability	reference, [1]	References the business capability element(s) used as target by this capability dependency; the target may be shared elsewhere in the model.

BoundedContextCandidate

Represents bounded context candidate in the CIM vocabulary. It specializes TraceableElement with the details needed for this modeling concern.

Direct supertypes: TraceableElement. Inherited attributes and marker capabilities are documented in the shared kernel; this section lists every attribute declared by this class.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
languageBoundary	String [1]	The vocabulary boundary inside which terms should keep one meaning. It is the DDD reason for separating concepts that happen to share a name. Semantic validation: BoundedContextHasBoundaryDefinition (bounded context has boundary definition) in mde/validation/cim/rules/organization-intent.evl the value must be present and non-blank. Transformation role: ETL rule BoundedContext2Service in mde/transformations/cim-to-pim/boundaries-security.etl assigns or materializes this feature while refining BoundedContextCandidate.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Orders owned by the fulfillment team..
ownershipBoundary	String [1]	The team or business ownership boundary that makes the context a plausible autonomous design unit. Semantic validation: BoundedContextHasBoundaryDefinition (bounded context has boundary definition) in mde/validation/cim/rules/organization-intent.evl the value must be present and non-blank. Transformation role: ETL rule BoundedContext2Service in mde/transformations/cim-to-pim/boundaries-security.etl assigns or materializes this feature while refining BoundedContextCandidate.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: orders-team.
externalIntegrationBoundary	Boolean [1]	Whether the context is also an integration seam with systems outside the modeled domain, where contracts and failure handling need extra attention. Transformation role: ETL rule BoundedContext2Service in mde/transformations/cim-to-pim/boundaries-security.etl assigns or materializes this feature while refining BoundedContextCandidate.	Either true or false. Example: false.

Relationships

Relationship	Kind and multiplicity	Meaning in the model
glossaryTerms → UbiquitousLanguageTerm	containment, [*]; opposite context	Contains the ubiquitous language term element(s) that make up this bounded context candidate; the contained objects belong to this model element.
capabilities → BusinessCapability	reference, [*]	References the business capability element(s) used as capabilities by this bounded context candidate; the target may be shared elsewhere in the model.
entities → DomainEntity	reference, [*]	References the domain entity element(s) used as entities by this bounded context candidate; the target may be shared elsewhere in the model.
commands → Command	reference, [*]	References the command element(s) used as commands by this bounded context candidate; the target may be shared elsewhere in the model.
queries → Query	reference, [*]	References the query element(s) used as queries by this bounded context candidate; the target may be shared elsewhere in the model.
events → BusinessEvent	reference, [*]	References the business event element(s) used as events by this bounded context candidate; the target may be shared elsewhere in the model.
policies → Policy	reference, [*]	References the policy element(s) used as policies by this bounded context candidate; the target may be shared elsewhere in the model.

UbiquitousLanguageTerm

Represents ubiquitous language term in the CIM vocabulary. It specializes TraceableElement with the details needed for this modeling concern.

Direct supertypes: TraceableElement. Inherited attributes and marker capabilities are documented in the shared kernel; this section lists every attribute declared by this class.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
term	String [1]	The preferred domain word. It is the name that should appear consistently in requirements, model elements, generated explanations, and stakeholder conversations. Semantic validation: UbiquitousLanguageTermHasDefinition (ubiquitous language term has definition) in mde/validation/cim/rules/organization-intent.evl the value must be present and non-blank. UbiquitousLanguageTermIsUniqueInContext (ubiquitous language term is unique in context) in mde/validation/cim/rules/organization-intent.evl the value must be present and non-blank. Transformation role: ETL rule UbiquitousLanguageTerm2BusinessRule in mde/transformations/cim-to-pim/root-scaffolding.etl assigns or materializes this feature while refining UbiquitousLanguageTerm.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Ubiquitous Language Term Term.
definition	String [1]	The meaning agreed by the bounded context, preventing a familiar word from silently carrying a different business concept in another model area. Semantic validation: UbiquitousLanguageTermHasDefinition (ubiquitous language term has definition) in mde/validation/cim/rules/organization-intent.evl the value must be present and non-blank. Generation role: The artifact generator references this feature in mde/generation/awspsm-to-artifacts/lib/validation.eol.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: A confirmed order is one accepted for fulfillment by the business..
synonyms	String [1]	Words that stakeholders may use interchangeably, recorded so the modeler can recognize them without promoting all of them to official vocabulary. Semantic validation: UbiquitousLanguageTermHasDefinition (ubiquitous language term has definition) in mde/validation/cim/rules/organization-intent.evl the feature participates in a semantic validation condition.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Ubiquitous Language Term Synonyms.
forbiddenSynonyms	String [1]	Terms that should not be used because they introduce ambiguity, legacy meaning, or a conflict with another context. Semantic validation: UbiquitousLanguageTermHasDefinition (ubiquitous language term has definition) in mde/validation/cim/rules/organization-intent.evl the feature participates in a semantic validation condition.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Ubiquitous Language Term Forbidden Synonyms.
exampleUsage	String [1]	A realistic sentence showing the term in context; it is often the fastest way to resolve an apparently abstract glossary disagreement.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Ubiquitous Language Term Example Usage.

Relationships

Relationship	Kind and multiplicity	Meaning in the model
context → BoundedContextCandidate	reference; read-only, [1]; opposite glossaryTerms	References the bounded context candidate element(s) used as context by this ubiquitous language term; the target may be shared elsewhere in the model.