EM-TEC-02 · Subject model · W1
Business application and software system
A system used by the organization, business application, module and purpose. The vendor's product, the purchased license and the running instance differ.
Queued for research
Claude: not-started; Grok: not-started.
Research note, in Russian: Entire research brief pending
Subject boundary and candidate types
- BusinessApplication
- SoftwareSystem
- ApplicationModule
- ApplicationUsage
Deep research questions
- When does a product support several business applications?
- Where is the boundary of an integrated system made of several products?
- How does a module differ from an independently managed application?
Verifiable invariants
- A system has a justified boundary
- Usage carries an organizational context
- Purchasing a product does not create a running instance
End-to-end acceptance scenario
One ERP product, two installations and three business applications form an explicit graph without merging.
Negative case
The vendor's ERP name automatically denotes all installations and business functions.
Approaches to compare
- AISMM/WM-SFT and ArchiMate: product, system and architecture
- CSDM: business application, service and runtime instance
- SPDX/OpenTelemetry/Google SRE: delivery, observation and reliability; choose by boundary
Candidates in the live catalogue
- WM-SFT-002 · Deployed System · 0.2.0-legacy · not installed automatically
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.