A  Business System is a man made artifact (Concrete Hardware System or Business Software System) which exposes  Functionalityies and can produce Business Outcome Events.

A  Business System performs System Processes and participates to System Processes or to Business Processes.

In System Processes, a  Business System is always an active participant (System Process Participant).

In Business Processes, a  Business System is either an active participant (Automated Participant) or an Instrument used by Org-Units.

A  Business System Environment Sxcenario is a story involving the partners of a Business System (Partner System), interacting in order to achieve Business Outcome Events in a specific Eco-System (Business System Environment).

This includes:

- A course of events represented by Object Flows depicting the story towards the delivery of expected Outcomes.

- Interacting partners who participate to the story in the considered Eco-System.

A  Business System Interaction Process is a black-box behavior involving the components of a Business System, interacting in order to produce Business Outcome Events.

This includes:

1) A course of events represented by Resource Flows depicting the steps towards the delivery of expected Business Outcome Events.

2) Interacting Business Systems who participate to the story.

A  Data Asset  represents the abstract structure of any kind of data that can be processed and memorized by a Business Software System.

A  Data Asset is either a Data Entity or a  Data Property.

Only Data Entitys can have identity and states.  Data Propertys only handle raw data.

 Data Assets are managed in Data Catalogs.

A  Data Domain is subset of the enterprise’s data that are meant to be manipulated together in the context of business operations.

For instance, a "Sales"  Data Domain contains at least the following entities: Customers, Orders, Products.

Each Data Entity in a  Data Domain has CRUD characteristics. For instance, Products are read-only in a "Sales"  Data Domain, while Customers and Orders have all CRUD characteristics.

 Data Domains define functional data boundaries used both for Data Allocation to Business Systems (see Data Stores) and Data Governance for data stewardship (Data Catalogs).

A  Mezzo Business System is a Business System that corresponds to the mezzo systemic level.

Example:

. Application

. Department Type

A  Micro Business System is a that Business System correspond to the micro systemic level.

Examples:

. Organizational Position

. MicroService

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.

An  Information Outcome Event is a Business Outcome Event that signals the happening of a change in the state of Data Assets, produced by Business Systems for the benefits of an internal or external party.

Example:

- Order received

- Payment rejected

A  Requirement is a generic statement used in system engineering to constrain what a Business System Asset should or should not be.

The  Requirement concept is kept in  SysFEAT to maintain compatibility with traditional system engineering methodologies.
The preferred approach is to follow capability-based engineering, as promoted by modern enterprise & system architecture (see OMG - UAF - View - Strategic Views) and agile frameworks (see SAFe© - SAFe Requirements Model).

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.