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.
Research draft, second pass
A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.
Bundle → Layer → Finding → Questions Missing, in the backlog
Not described yet. This gap is in the card backlog.
Note: Research contour: bundles not designed yet; questions are listed as open questions.
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise landscape
- Entry kind
- landscape
- Domain
- EnterpriseLND
- Industry
- Cross-industry
- Tags
- EM-LND-06W1landscapeSoftwareLandscapeLandscapeMembershipLandscapeDependency
What it is Filled
Composition, interactions, ownership, criticality and evolution of software across products. PLMM is a candidate; its status and version require a separate decision.
Why it exists Filled
Composition, interactions, ownership, criticality and evolution of software across products. PLMM is a candidate; its status and version require a separate decision.
Distinguishing features Derived, awaiting review
- Product internals are not copied
- Dependency versions are pinned
- Graph incompleteness is visible
What robots and AI may and may not do Derived, awaiting review
Must not
- Negative case: A PLMM legacy installation is declared a finished canonical landscape.
Note: Negative case of the research brief, not yet a rule for agents.
Moral aspects Missing, in the backlog
Not described yet. This gap is in the card backlog.
Owners Filled
Steward
Куратор мета-моделей Vercy
Master systems
- Реестр моделей
- sources.yaml
- vercy.lock
- политики
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 Incomplete
Identity and identifiers required Derived, awaiting review
- SoftwareLandscape
- LandscapeMembership
- LandscapeDependency
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Capabilities and actions required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Hazards and failure modes required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Standards and interfaces required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Context of use required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Sources Filled
- 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
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
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.