An  Application is a Business Software System that provides a set of  Functionality(ies) that End Users see as a single unit.

Essentially  Applications are architectural constructions resulting from the combinaison of the following four criteria:

1) A group of  Functionality that End Users see as a single unit.

2) A managed asset (Managed Application) associated with a budget line in the context of an Application Portfolio.

3) A body of code that is seen by developers as a single unit.

4) A group of deployable software units (Deployable Application Packages) that must be installed together on one or multiple execution nodes (Computing System).

 Application is a Mezzo enterprise asset  that sits between Application System and Application Component in the decomposition of Business Software Systems.

Example: " Payroll" is an  Application that is part an " HR System" which is an Application System.

The "Payroll"  Application includes, among other things, the "Salary and Wage Calculation" Application Component.

An  Application Component is a functionnal unit of software (java class, COBOL Program, Batch) that is  a consistent, indivisible unit of processing of an Application producing and consuming its Information Outcome Events though APIs (Application Interface).

a)  Application Components are assembled and orchestrated in Applications.

b)  Application Components cannot be directly deployed to Computing Systems: they need to be organized in Deployable Application Packages.

 Application Component is a Micro enterprise asset that sits at the lowest level of Business Software System decomposition.

Example: the "Salary and Wage Calculation" component is an  Application Component that is part of the "Payroll" Application.

An  Application Environment Scenario is a story involving the partners of an Application (Partner Application) interacting in order to achieve Information Outcome Events in a specific Eco-System (Application Environment).

This includes:

- A course of events represented by Application Flows depicting the story towards the delivery of expected Information Outcome Events.

- Interacting Partner Applications who participate to the story in the considered Application Environment.

An  Application Interface is a Business Service Interface that occurs between Business Software Systems.

The interface is described by messages exchanged between endpoints (provider, consumer..).

An  Application System is a Business Software System which is an assembly of multiple Applications or other  Application Systems that, together, fulfill a set of  Macro  Functionality(ies) delivered to Business Operations.

 Application Systems are used in the context of IT Strategic planning to define and evolve other time the hight level structure of the enterprise IT Architecture.

 Application System is a  Macro enterprise asset that sit at the top of Business Software System decomposition hierarchy.

Example: "HR System" is an  Application System whereas "Payroll" is an Application that is part of the "HR system".

An  Application System Environment is an operating context in which an Application System defines its interactions with its partners (Partner System) in the form of API connections (Software Connection).

It also represents End Users that interact with the system.

An  Application System Scenario is a story involving the components of an Application System (Applications), interacting in order to produce Information Outcome Events.

This includes:

1) A course of events represented by Application Flows depicting the story towards the delivery of expected Information Outcome Events.

2) Interacting Applications who participate to the story.

A  Department Type is a Mezzo Org-Unit which serves as an administrative unit template in both government and business Organizations.

Examples:

- Sales department;

- Finance department;

- Logistics department..

An  Enterprise is a macro Enduring Initiative that delivers added-value Products (goods & services) to its target  Customers.

It requires a formal organization of groups of people and resources to achieve its purposes.

A  Functionality is a Business Resource Capability offered by Business System Assets (software or hardware) and aimed at delivering Information Outcomes.

A  Functionality describes WHAT a software or hardware system can provide.

 Functionality(ies) are used to express the Business System features required by people when performing their job (see Job-to-be-done).

For internal customers, these jobs correspond to Business-Process Steps described in Business Process (see Instrument)

For enterprise Customers, these jobs correspond to Job-to-be-done in the context of Customer Journeys.

A  MicroService is a small autonomous unit of software, emphasizing self-management and lightweightness as the means to improve software agility, scalability, and autonomy.

1)  MicroServices are automous or assembled and orchestrated as components of Applications.

2)  MicroServices can be directly deployed to Computing Systems.  MicroServices are both a logical unit of software and a Deployable Package.

3)  MicroServices owns their own data store and dot not have any shared stores with other components.

 MicroService is a Micro enterprise asset that sits at the lower level of Business Software System decomposition.

A  NoSQL Data Schema represents a set of data stored in a NOSQL database management system and used in Application Deployment Architectures.

An  Organizational Position is a type of position held by people when part of a Department Type.

Examples:

- Sales representative

- Developer

- Storekeeper

- Architect

A  Relational Schema is a set of relational Table , keys, indexes and associated items that represent the structure of a relational database. A relational database can have multiple schemas.

A  Software Technology is an elementary Software Technology System  used as an enabler by Software Modules.

Examples :

- Application server,

- Message server,

- Storage,

- Business information sharing,

- Operating systems,

- Navigators, etc

A  System Process is a Action Process that occurs inside Business Systems (software systems or hardware systems). Its performers can only be Business Software Systems or Concrete Hardware Systems.

During its course of action, a  System Process consumes or produces Data Assets:

1) It may memorize or access Data Assets in its Process Store.

2) It may receive Data Assets at its boundary: Consumed Outcome.

3) It may signal the production of Data Assets at its boundary: Delivered Outcome.

The course of actions of a  System Process is constrained by the application of rules ( System Rule Enforcement) that define what is allowed and not allowed to do.

A  Business Software System is a Business System used by Business Operations, that represents all granularities of software - ranging from MicroServices to enterprise wide Application Systems - used by Business Operations.

All  Business Software Systems share the following characteristics:

1) They provide  Functionalitys.

2) They expose APIs (Application Interfaces) through which they deliver Information Outcome Events.

3) They handle datastores defined by Physical Data Domains.

4) They perform and participate to System Processes.

A  Physical Data Domain is subset of the metadata of an enterprise’s data store.

For instance, a "Sales"  Physical Data Domain contains a "Client" Table and a "Order" Table.

Each Physical Data Entity in a  Physical Data Domain has CRUD characteristics. For instance, the "Client" Table in the "Sales"  Physical Data Domain, has all CRUD characteristics.

 Physical Data Domains define functional data boundaries used both for Data Allocation to Business Systems (see Resource Agent Store) and data governance for data stewardship (see Data Catalog).

A  Software Module is a Business Software System that is part of an application system.

A  Software Module is either an Application, Application Component or a MicroService.

All share the ability to be composed of sub-Application Components and have dependencies to enabling Software Technology(ies).