← Back to catalogue
Published

Business application and software system

EM-TEC-02 · em-tec-02

A system used by the organization, business application, module and purpose. The vendor's product, the purchased license and the running instance differ.

Enterprise profiles Enterprise subject EnterpriseTEC

Bundle → Layer → Finding → Questions Filled

2 bundles · 2 layers · 4 findings · 8 questions

Application boundary What the organisation calls a system and why it has that boundary.

Application and system

Business application, software system and module as separate records.

Justified boundary

The boundary of a business application and the reason for it.

  1. Which business purpose does this application serve?
  2. Why does the boundary include these products or modules and not others?

Module

A module inside an application versus an independently managed application.

  1. Is this a module of an application or an application managed on its own?
  2. Which products together form this integrated system?
Product, licence and instance Vendor product, purchased licence and running installation kept apart.

Product to installation

The graph from vendor product to installations to business applications.

Installations

Running installations of a product, each with its own record.

  1. Which installations of the vendor product exist, and where do they run?
  2. Does a purchased licence have a running installation behind it?

Usage context

Organisational usage of an application by units and roles.

  1. Which units and roles use this application, and for what?
  2. Which business applications share one installation or product?

Classifiers Filled

Family
Enterprise profiles
Category
Enterprise subject
Entry kind
subject
Domain
EnterpriseTEC
Industry
Cross-industry
Tags
EM-TEC-02W1subjectBusinessApplicationSoftwareSystemApplicationModuleApplicationUsage

What it is Filled

A system used by the organization, business application, module and purpose. The vendor's product, the purchased license and the running instance differ.

Why it exists Filled

A system used by the organization, business application, module and purpose. The vendor's product, the purchased license and the running instance differ.

Distinguishing features Filled

  • A vendor product, a purchased licence and a running instance are three different things.
  • One product can support several business applications, and one application can combine several products.
  • Every application record carries the organisational context of its use.
  • Distinct from the software product record, which covers how software is built rather than used.

What robots and AI may and may not do Filled

Must not

  • Treat a vendor's ERP name as covering all installations and business functions.
  • Create a running instance record from a purchase alone.
  • Merge separate installations because they run the same product.
  • Decommission or change an application without its owner's approval.
  • Report licence compliance to a vendor on its own initiative.

Only with a human decision

  • Changing application boundaries or retiring an application.
  • Responding to a vendor licence audit.

May

  • Build the graph from product to installations to business applications.
  • Flag licences with no installation and installations with no licence record.
  • List units and roles using an application.

Moral aspects Filled

  • Applications hold personal data, so unclear boundaries blur who is responsible for it.
  • Wrong licence records can lead to financial penalties or service loss.

Who is affected

  • Business users and their units
  • IT and application owners
  • Software vendors and resellers

Owners Filled

Steward

The CTO, the CIO or the service owner accountable for the system.

Master systems

  • Software catalogue
  • Source control
  • CI/CD pipeline
  • CMDB
  • Observability platform

Links to other meta-models Filled

neighbor

  • EM-TEC-01
  • EM-TEC-03

references

  • WM-SFT-002 - conceptual-candidate

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Identified by an application identifier in the software catalogue; installations by instance identifier and environment.

Direct properties not applicable Not applicable

Not applicable

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

Recognition optional Filled

  • A record names a business purpose, an owner, products used and installations.
  • Often confused with the vendor product name or the server it runs on.

Capabilities and actions required Filled

  • The product, installation and application graph supports impact and licence analysis.
  • Usage records show which units depend on which systems.

Hazards and failure modes required Filled

  • Phantom applications that exist only as purchases.
  • Shadow systems used without any catalogue record.
  • Merged records that hide separate installations.

Standards and interfaces required Filled

  • The Open Group ArchiMate application component and application service.
  • ISO/IEC 19770-2 software identification tags.
  • ISO/IEC 19770-3 entitlement schema for licences.

Context of use required Filled

  • Used in IT portfolio management, licence management and architecture work.
  • Applies to on-prem, hosted and SaaS applications alike.

Sources Filled

  1. AISMM/WM-SFT and ArchiMate: product, system and architecture
  2. CSDM: business application, service and runtime instance
  3. SPDX/OpenTelemetry/Google SRE: delivery, observation and reliability; choose by boundary
  4. SPDX Specification 2.3 - Checked live (HTTP 200) on 2026-10-07.
  5. OpenTelemetry Resource Semantic Conventions - Checked live (HTTP 200) on 2026-10-07.

Open 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?
  • Установить границу и решение reuse/extend/new по действующим спецификациям.
  • Подтвердить semantic crosswalk, права и source mastership.
  • Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.

Machine files

Provenance

enterprise research programme · published-partial

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

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