EM-LND-18 · Landscape · W3
Enterprise landscape
A composition of selected domain landscapes for specific management questions. Not a universal copy of all enterprise data and not a kernel.
Queued for research
Claude: not-started; Grok: not-started.
Research note, in Russian: Entire research brief pending
Subject boundary and candidate types
- EnterpriseLandscape
- EnterpriseViewScope
Deep research questions
- Which questions justify including each contour?
- How to act when local meanings conflict?
- How to assess completeness without mandatorily installing all domains?
Verifiable invariants
- The composition is chosen explicitly
- Ownership of facts stays in the domains
- A cross-context transition preserves restrictions
End-to-end acceptance scenario
Assemble different overviews for a three-person service business and a holding, leaving unneeded domains inactive.
Negative case
The enterprise is obliged to install every subject model from the registry.
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
The boundary and the reuse / extension / new model route are not chosen yet.
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.