← Back to catalogue
Published

Software product landscape

EM-LND-06 · em-lnd-06

Support cross-product upgrade, retirement and security response decisions using accountable ownership, assessed criticality and evidence-bounded dependency impact.

Enterprise profiles Enterprise landscape EnterpriseLND

Bundle → Layer → Finding → Questions Filled

2 bundles · 3 layers · 6 findings · 14 questions

Landscape scope This bundle records landscape membership, authority and dated snapshots.

Landscape membership

This layer references authoritative product records and identifies the landscape's own statements.

Member products

This finding records membership references and accountable product owners.

  1. Which product and shared platform records are referenced by this landscape record?
  2. Which authoritative product record does this membership record reference?
  3. Which owner is accountable for the product data referenced by this membership record?

Landscape authority

This finding distinguishes landscape-owned statements from referenced product information.

  1. Which statements does this landscape record own, and which does it reference from product records?

Landscape snapshot

This finding records the date and change references of a landscape snapshot.

  1. What date does this snapshot represent, and which change records are linked to it?
Dependencies and impact This bundle records dependency evidence, assessment gaps and product criticality.

Dependency graph

This layer separates declared constraints, observed deployments and unresolved dependency evidence.

Dependency record

This finding records declared and observed versions separately while preserving assumptions and observation gaps.

  1. Which shared platform and declared version constraint does this dependency record reference, or what declaration gap is recorded?
  2. What observed, declared, assumed or unconfirmed evidence status and supporting source are recorded for this dependency?
  3. Which deployed version, environment and observation time are recorded for this dependency, or what observation gap is explicit?

Visible gaps

This finding records unresolved dependencies and their limits on impact conclusions.

  1. Which unknown or unconfirmed dependencies are recorded in this landscape record?
  2. What limit do the recorded gaps place on this impact assessment?
  3. Which open questions must be resolved before this impact assessment can support its stated decision?

Software criticality

This layer references accountable and dated criticality assessments.

Criticality assessment

This finding identifies assessment authority, criteria and consequences or an explicit assessment gap.

  1. Which authoritative criticality assessment does this membership record reference, or what assessment gap is recorded?
  2. Which criticality rating, business consequences and assessment criteria are recorded in this criticality assessment?
  3. Which accountable role and assessment date are recorded in this criticality assessment?

Classifiers Filled

Family
Enterprise profiles
Category
Enterprise landscape
Entry kind
landscape
Domain
EnterpriseLND
Industry
Cross-industry
Tags
EM-LND-06W1landscapeSoftwareLandscapeLandscapeMembershipLandscapeDependency

What it is Filled

A referenced view of software products, shared platforms, dependencies, ownership, criticality and changes across dated snapshots.

Why it exists Filled

Support cross-product upgrade, retirement and security response decisions using accountable ownership, assessed criticality and evidence-bounded dependency impact.

Distinguishing features Filled

  • A landscape refers to products without becoming a second authoritative record of any product it includes.
  • A dependency distinguishes its declared version constraint from the deployed version observed in a stated environment and at a stated time.
  • Unknown or unconfirmed dependencies remain visible and limit impact conclusions.
  • Criticality is recorded through a dated assessment or explicitly delegated to an authoritative product assessment.
  • Dated snapshots and linked change records support comparison across the landscape's evolution.
  • The landscape describes relationships across products while a single software product contour describes one product internally.

What robots and AI may and may not do Filled

Must not

  • Copy product internals into the landscape and treat the copy as authoritative.
  • Report a dependency without its evidence status and either its observed version, environment and observation time or an explicit observation gap.
  • Treat a declared version constraint or assumed version as an observed deployment version.
  • Present an incomplete graph as complete impact.
  • Invent or independently change a product criticality rating.

Only with a human decision

  • An accountable decision owner must accept an impact assessment before using it to authorize a release or retirement.
  • An accountable product owner must approve a new or changed product criticality assessment.

May

  • Assemble an impact graph from product records and dependency records with their evidence status and observation gaps.
  • List unknown or unconfirmed dependencies as open questions.
  • Compare two snapshots of the landscape and report what changed.
  • Reference authoritative product criticality assessments and flag missing assessments.

Moral aspects Filled

  • Overstated completeness can lead teams to ship changes that break products nobody listed.
  • Product owners stay accountable for their own data; a landscape must not silently take over that role.

Who is affected

  • Product owners and engineering teams
  • Users of dependent products
  • Platform teams

Owners Filled

Steward

The software portfolio steward is accountable for the software landscape record, its membership and its dependency and impact views.

Master systems

  • The product register holds authoritative product identities and accountable owners.
  • The service catalogue holds authoritative shared platform and service records.
  • The dependency inventory holds authoritative declared software dependencies.
  • The deployment inventory holds authoritative observed versions and deployment relationships.
  • The criticality assessment register holds authoritative product criticality assessments.
  • The software landscape register holds landscape membership, source references and dated snapshots.

Links to other meta-models Filled

references

  • PLMM - conceptual-candidate
  • WM-XCT-039 - conceptual-candidate

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Identified by a landscape identifier and version, with members referenced by their own product identifiers.

Direct properties not applicable Not applicable

Not applicable

Enterprise record contour: physical properties belong to referenced world models.

Recognition optional Filled

  • A record listing several products, a shared platform and pinned dependency edges.
  • Often confused with a product record or with an inventory of installed software.

Capabilities and actions required Filled

  • Impact of a platform change can be traced to the products that pin it.
  • Snapshots can be compared to show how the landscape evolved.

Hazards and failure modes required Filled

  • Stale pins that no longer match what runs in production.
  • False confidence when unknown dependencies are drawn as absent.
  • Duplicate product records created by landscape tooling.

Standards and interfaces required Filled

  • ISO/IEC/IEEE 42010 for architecture descriptions, views and viewpoints.
  • ArchiMate from The Open Group for modelling application and technology layers.
  • CycloneDX from OWASP and SPDX from the Linux Foundation for component and dependency inventories.

Context of use required Filled

  • Used by organisations running several software products on shared platforms.
  • Relevant when planning upgrades, retirements or security response across products.

Sources Filled

  1. Vercy composition and whole-object: a separate landscape object and delegation
  2. ArchiMate/ISO 42010: views, questions and representation rules
  3. Compare participant subject models and the practical assembly of a permitted context
  4. Vercy Whole-Object Description Profile - Checked live (HTTP 200) on 2026-10-07.
  5. The Open Group ArchiMate Forum - Checked live (HTTP 200) on 2026-10-07.
  6. The Open Group ArchiMate Overview - Checked live (HTTP 200) on 2026-10-07.
  7. Vercy Model Agent Protocol - Checked live (HTTP 200) on 2026-10-07.

Open questions

  • What is PLMM entitled to describe on its own?
  • How to reconcile AISMM 3.1 runtime and 3.2 README with PLMM legacy?
  • How to build impact from incomplete data?
  • Согласовать runtime и repository версии AISMM/PLMM и роль ELMM; совместимость сейчас не доказана.
  • Установить границу и решение reuse/extend/new по действующим спецификациям.
  • Подтвердить semantic crosswalk, права и source mastership.
  • Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.

Machine files

Provenance

enterprise research programme · published-partial

Built from: enterprise/models/em-lnd-06/brief.json, ver-cy/world-models/card-supplements/em-lnd-06.json

Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.