EM-LND-06 · Landscape · W1
Software product landscape
Composition, interactions, ownership, criticality and evolution of software across products. PLMM is a candidate; its status and version require a separate decision.
Partially published; research continues
Claude: complete-frozen-study-and-single-audit-remediated; Grok: complete-reconciled.
Published results
Research note, in Russian: Canonical/runtime promotion remains governed by the package allocation, identity and dependency holds.
Subject boundary and candidate types
- SoftwareLandscape
- LandscapeMembership
- LandscapeDependency
Deep research 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?
Verifiable invariants
- Product internals are not copied
- Dependency versions are pinned
- Graph incompleteness is visible
End-to-end acceptance scenario
Three products and a shared platform yield an impact graph and questions about gaps, without creating a second SoftwareProduct.
Negative case
A PLMM legacy installation is declared a finished canonical landscape.
Approaches to compare
- Vercy composition and whole-object: a separate landscape object and delegation
- ArchiMate/ISO 42010: views, questions and representation rules
- Compare participant subject models and the practical assembly of a permitted context
Candidates in the live catalogue
- PLMM · Product Landscape Meta-Model · 0.1.0-legacy · not installed automatically
Semantic fit requires boundary research; a published model does not by itself complete this card. - WM-XCT-039 · Managed IT Service Graph · 0.1.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card.
Result requirements
Every card is executed together with the full research contract: definitions, fields and cardinalities, lifecycle, sources, data mastership, rights, the five object facets, at least eight invariants, positive and negative examples, dependencies, migration and applicability limits.