Understand what the Applications Inventory governs

The Applications Inventory governs the application — the discrete, nameable software solution that an organization owns, operates, licenses, or depends upon to support business capabilities and deliver value to its users and operations. An application record in this inventory represents exactly one application: one named solution with one primary owner, one defined purpose, and one identified cost profile. It does not represent a module, a component, a library, a database, a queue, or an integration — each of those entity classes has its own inventory type in the Enterprise Model.

The boundary between an application and a system is the most common ambiguity practitioners encounter. A system is a broader collection of applications, data stores, and infrastructure components that work together to deliver a complex capability — for example, an order-to-cash system that comprises an order management application, a billing application, a payment processing application, and the integrations and data stores that connect them. In the Applications Inventory, each discrete application within a system has its own record. The system itself is understood through the relationships between those records in the Enterprise Model, not through a single system-level record in the Applications Inventory.