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 Deployment Architecture describes one possible deployment configuration of an Application.

It contains Deployable Packages to host, prescribed type of hosting and required  Software Physical Channels (with communication protocols, port numbers...) to communicate with each other.

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..).

 Application Portfolios are Enduring Initiatives aimed at managing a set of Applications delivering functionalities required by enterprise operations.

The purpose of  Application Portfolios is efficiency: managed Applications must provide expected functionalities in the best cost / performance ratio.

An  Application Scenario is a story involving the components of an Application (Application Component or MicroService), 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 Application Components who participate to the story.

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 Deployment Architecture describes one possible deployment configuration of an Application System.

It contains chosen deployment architectures for component applications and identifies communication protocols (and port numbers) they use to communicate with each other.

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.

An  Architecture Governance Committee is an organization of resources and people (persons and committees) who make up a body for the purpose of administering an Enterprise.

Enterprise stakeholders draw up the rules that govern the actions and conduct of an enterprise and ensure that these rules are followed.

An  Architecture Governance Committee includes sets of dedicated resources and activities that support interactions and decision-making among the stakeholders involved in architecting the Enterprise.

 Architecture principles are general guidelines (Policy) that serve as constraints that guide design decisions and shape the overall structure of a system. They:

- Establish boundaries for design choices.

- Ensure consistency across the system

- Promote desired qualities (Condition Property: e.g., scalability, maintainability)

- Align architecture with business goals and requirements

 Architecture principles act as guardrails, helping architects make informed decisions while limiting options to those that best serve systems' efficiency and robustness.

An  Architecture Project project consists in a set of modeling tasks entrusted to a Team Committee in order develop or update architecture artifacts (Asset Blocks) so as to achieve a specific objective.

 Architecture Projects are often sub-initiatives of larger enterprise transformation endeavors.

A  Business Capability is a conceptual Capability that benefits to Customers (internal or external) of the enterprise. It expresses an ability to produce Conceptual Outcome Events.

A  Business Capability is defined by its intended Enterprise Outcome Events and the conditions (Condition Property) under which the production of the Enterprise Outcome Events shall be proceeded.

The actual Condition Scale Values for a given Business Capability at different stages of Enterprise Initiatives is given by their exhibition (Exhibited Capability).

A  Business Dictionary is a cluster of Business Dictionary Blocks whose existence and meaning are defined by the  Business Dictionary.

It comprises the Concepts,  Event Concepts along with the terminology (Terms) used to describe this branch of knowledge or discipline.

A   Business Dictionary is both:

1. A lexical scope (Dictionary Lexical Scope): the meaning of a Dictionary Block can only be determined by the  Business Dictionary where it was created.

2. A universe of discourse: the complete range of Conceptual Objects that are expressed, assumed, or implied in a branch of knowledge, a discipline or a field of study.

Example:

- The Harward Medical Dictionary of Health Terms :

A  Business Function is a Mezzo unit within the enterprise's functional division of labor. It is used to shape the enterprise management structure in regard to how it produces, consumes or processes Business Outcome Events: information, energy, materiel.

A  Business Function specifies Skills and  Functionality(ies) required to perform their activities effectively.

A  Business Interaction Process is a story describing how the components of a Business-Entity (Department Types) interact to produce Business Outcome Events.

This includes:

- A course of events represented by information flows depicting the steps towards the delivery of expected Outcomes.

- Components of an Department Type (Sub-Department Types or Organizational Position) that participate to the story.

A  Business Line is a high level classification of the main activities of the enterprise. It corresponds for example to major product segments or to distribution channels.

It can be used to classify Business Processes, Organizational Units or Applications that serve a specific product and/or a specific market.

 Regulatory Frameworks in some industries impose their own list of  Business Lines.

A  Business Object Assurance Case is a Data Assurance Case related to a critial Domain Asset.

Its purpose is to defined the quality and integrity rules that apply to a Domain Asset in each business contexts such as activity domains on the enterprise.

A  Business Partner is a state of a Resource Agent, who acts as a party interacting with the enterprise in the context its operating eco-system (the Resource Operating Ecosystem).

Example : Private Sector Customer, Regulation Authority, Public health Authority.

A  Business Rule is a rule that is under business jurisdiction.

A rule’s being under "business jurisdiction" means that it is under the jurisdiction of the community that it governs or guides - that the community can opt to change or discard the rule. Laws of physics may be relevant to an Enterprise; legislation and regulations may be imposed on it; external standards. These things are not  Business Rules from the company’s perspective, since it does not have the authority to change them.

The company will decide how to react to laws and regulations, and will create  Business Rules to ensure compliance with them. Similarly, it will create  Business Rules to ensure that standards or best practices are implemented as intended.

A  Business Scenario is a story describing how Business-Entity (Department Type) interact wtiht its partners (Partner Department) to achieve Business Outcome Events in a specific Eco-System (Business Environment).

This includes:

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

2) Interacting  Business Entities (Department Types)  who participate to the story in the considered Eco-System.

A  Compliance Case is an Assurance Case (a claim) that a particular set of Resource Operating Assets (Systems or Processes) adequately mitigates certain identified Compliance Risk Types by means of appropriated controls.

A  Compliance Case shall provide confidence that the concerned assets will function as intended in their environment of use.

A  Computer Device is a Computing Device which provides services directly to the end-user.

 Computer Devices can host data stores and run Application code.

Examples: workstation, laptop computer, smartphone.

A  Computer Network is an assembly of Network Devices (e.g. routers, switches, firewalls) that enables communications between Computing Systems (e.g. Computer Servers).

A  Computer Network may breakdown into sub-networks.

A  Computer Server is a Computing Device which provides processing, storage, and network connectivity services to other Computing Devices on a Computer Network.

As a Computing System, it can host data and run Application code..

A  Concept is the representation of any tangible or intanglible entity that is of interest to understand the enterprise, its data, resources and activities.

A  Concept is defined through its essential characteristics which can be:

1) A  Concept Property that represents some an immutable factual characteristic such as "name", "amount".

2) A Concept Relationship that represents relationships to other  Concepts.

A  Concept Domain is a subset of the Concepts of a  Business Dictionary that are relevant to an Operating Domain.

For instance, a "Sales Concept Domain" comprises at least the Concepts of "Customer" and "Order" while a standard "Marketing Concept Domain" comprises at least the Concepts of "Market Segment", "Product" and "Value Proposition".

 Concept Lineage is about tracking the flow of information.

It is necessary to guarantee the quality, usability and security of business data.

For large organizations, it is also a key conformity legal requirement: BCBS 239, Solvency II.

Business Data Lineage is defined as a business data life cycle that describes the source of business data and where it moves over time.

A  Concept Property is an immutable factual characteristic of a Conceptual Entity.

Example: names, amounts, etc.

A  Conceptual Business Rule is a rule that is under business jurisdiction.

A rule’s being 'under business jurisdiction' means that it is under the jurisdiction of the semantic community that it governs or guides - that the semantic community can opt to change or discard the rule. Laws of physics may be relevant to a company (or other semantic community); legislation and regulations may be imposed on it; external standards and best Semantics of Business Vocabulary and Business Rules, v1.0 161 practices may be adopted. These things are not business rules from the company’s perspective, since it does not have the authority to change them. The company will decide how to react to laws and regulations, and will create business rules to ensure compliance with them. Similarly, it will create business rules to ensure that standards or best practices are implemented as intended.

As part of the enterprise Conceptual Operating Model, a  Conceptual Environment Scenario is a story that describes how an Operating Domain interacts with its partners (Business Partner) to achieve Business Outcome Events in a specific Conceptual Environment..

This includes:

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

2) Interacting partners who participate to the story in the considered Conceptual Environment.

An  Conceptual Event is a Temporal Bounding Type that establishes a temporal connection between Conceptual Behaviors.

An  Conceptual Event connects a Previous Behavioral Event, to a Next Behavioral Event.

As part of the Conceptual Operating Model, a  Conceptual Interaction Scenario is a story that frames how the components of a Conceptual Agent interacts to achieve Conceptual Outcome Events.

This includes:

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

2) Conceptual Agents who participate to the story.

A  Control Directive is a kind of Policy that provides recommendations on how to comply with Regulation Articles.

Once implemented,  Control Directives enforces any  Regulatory Framework your enterprise has to comply with.

A  Customer is a Business Partner who orders and/or uses Products (goods or services) produced by enterprises.

A  Customer is part of an ecosystem and has the ability to choose between different Products.

A  Data Catalog is an Assurance System of  Data Assets, ensuring understanding,  trust, compliance and confidence of enterprise data. This includes:

1. Relationship with Enterprise Glossary to provide business context to metadata.

2. Data policy definition and enforcement to ensure data quality.

3. Data Lineage to master data provenance: where data comes from, how data is transformed, and where it is used.

A  Data Center is a Facility composed of networked computers, storage systems and computing infrastructure that enterprises use to organize, process, store and disseminate large amounts of data.

Business Operations rely heavily upon the applications, services and data contained within a  Data Center, making it a focal point and critical asset for everyday operations.

A  Data Field Snapshot is status of a NoSQL Field a the time of data discovery. it provides factual information such as , Minimum Value, Maximum Value, etc.

 Data Field Snapshots are used for quality assessments in data governance.

A  Data Set Snapshot is status of a NoSQL Dataset a the time of data discovery. It provides factual information on the NoSQL Dataset such as Number of Unique Values, Number of Entities, Number of Completed Records, etc.

 Data Set Snapshots are used for quality assessments in data governance.

A  Department is a Mezzo Organization. It is a an administrative unit in government or business.

Examples:

- Sales department of "Aircraft corporation" in France;

- Finance department of "Oakland digital hospital";

- Logistics Department of "APPCo retail inc".

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..

A  Deployable Application Package  is a split of application code according to deployment criteria at runtime. For example, it may be Front End/Back End or GUI/Business Logic etc..

Each  Deployable Application Package is associated to required Software Technology(ies) (for running) and can host code of several Application Component.

Architects can also prescribe a kind of hosting artefact (IaaS/PaaS cloud service or IT server model).

A  Deployable Data Package  represents a data part of an Application that must be hosted and accessed by application services (code) to run.

Each  Deployable Data Package is associated to Required Software Technologys (for data hosting and access) and can host several data structures.

Architect can also prescribes a kind of hosting artefact (IaaS/PaaS cloud service or IT server model).

A  Deployed Data Store is a repository for storing, managing and distributing data sets on an enterprise level. It is a broad term that incorporates all types of data that is produced, stored and used by an organization.

 Deployed Data Stores exist wihin a Data Center. They can be hosted on Deployed Server.

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.

An  Enterprise Stage is a past, current or future state of the Enterprise.

Each stage represents an initiative comprising a purposeful set of activities whose primary purpose is focused on achieving a set of clearly defined objectives that may transcend organisational boundaries and consequently require integrated team working under the direction of an Architecture Governance Committee.

 An  Event Concept is a Domain Asset that represents a type of change used to draw the temporal boundaries of Conceptual Entitys.

Examples:

- order placing

- order delivery

- birth

- death

A  Facility is a class of System of Resources that represents the physical infrastructure (e.g., buildings, plants, warehouses, offices, or laboratories) that houses personnel, equipment, and processes, enabling enterprise's activities.

Examples:

- Data Center

- Factory

- Outlet

- Outdoors construction

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  Hardware Configuration is a Mezzo Concrete Hardware System that is an assembly of Hardware Equipments.

Examples:

- Connected Drone with Online Payment App.

- 3D printer.

- Automated Guided Vehicles (AGVs)

- Connected fridge providing an ordering Functionality and of course a freezing Hardware Capability.

- Production equipment in an assembly line (metal forging machine)

- Car

A  Hardware Equipments are tangible assets (e.g., machinery, tools, IT hardware, vehicles, or production systems) used to execute enterprise operations, deliver services, or produce goods.

a Micro Concrete Hardware System.

Examples:

- Fridge compressor

- Car Engine

A  Hardware Portolio is an Asset Portfolio aimed at developing and maintaining in operational conditions a set of Concrete Hardware Systems delivering  Hardware Capabilitys required by Business Operations.

The purpose of   Hardware Portolios is efficiency of Managed Hardwares, which must provide expected  Hardware Capabilitys in the best cost / performance ratio.

A  Hardware Technology is an elementary Technology System  used as an enabler by Concrete Hardware Systems (as Required Hardware Technology).

 Hardware Technologys fulfill  Hardware Technology Capabilitys.

Examples:

- Oxford Anor Spectrographs (NMR).

- Spectral Data Services (NMR).

- Valeo Powertrain Systems.

- Joyson Electronics Powertrain Systems.

An  Individual Concept is an instance of a Concept.

For example, "John Doe" is an instance of the "Person" Concept.

An  Individual Facility is an Individual System of Resources used to model factories, buildings, or outdoor constructions that provides a particular  Business Capability or is used for a particular industry.

Examples:

- London Data Center

- Frankfurt Factory

- Milan Outlet

An  Individual Resource Configuration is a generic Individual System of Resources that represents Individual System of Resources that are not Individual Facilitys.(Data centers, Factories, Outlets).

Examples:

- The configured nuclear power plant of (with operating teams), 

- The configured aircraft carrier number 3424 (with crew#1) on flight 2501 to LA.

When specific characteristics need to be considered for a given type of  Individual Resource Configuration, it is recommended to create a new sub-type of Individual System of Resources to capture these characteristics.

An  Individual State Concept is an instance of a  State Concept.

Example:

- "John Doe employe at Concoso Corporation in 2010" is a state of the "John Doe" Individual Concept.

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  Job-to-be-done is a set of Customer Tasks that contribute to the achievement of the Customer duty(ies).
The granularity of  Job-to-be-done is determined by Business Outcome Events experienced at  Touch Points.

The  Job-to-be-done concept was forged by Clayton Christensen who provided the following definitions in an article written for the Harward Business Review (see references).
1. “Job” is shorthand for what an individual really seeks to accomplish in a given circumstance.

2.. The circumstances are more important than customer characteristics, product attributes, new technologies, or trends.

3. Jobs are never simply about function-they have powerful social and emotional dimensions.

A  Logical Data Entity is a logical structure of a Data Entity. As any Data Entity, it has an independent existence and can be uniquely identified.

A  Logical Data Entity is characterized by Logical Relationships it has with other  Logical Data Entity(ies) and by its Attributes.

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.

A  NoSQL Dataset is a Physical Data Entity that represents the structure of a collection of related data held in a data source. The represented data structure can be relational (Table) or NoSQL (triple store, document store, flat files, etc.).

A  NoSQL Dataset consists of three types of NoSQL Field:

1) An Identification MetaField, sometimes called "primary key".

2) Relationship MetaFields used to represent relationships with other  NoSQL Datasets.

3) Value MetaFields used to store values in the  NoSQL Dataset.

 NoSQL Datasets can be defined at design time in the context of data architecture activities. They can also be imported automatically through data discovery.

An  Operating Domain is a Macro functional division of labor within an enterprise, acting as a Conceptual Agent.

It embodies a collection of interrelated  Business Functions which collaboratively provide one or more  Business Capability(ies).
Operating Domains serve as the highest hierarchical grouping of Business Functions within the enterprise's Conceptual Environment.

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

Examples:

- Sales representative

- Developer

- Storekeeper

- Architect

A  Period that is an arbitrary period of time.

Examples:

- 20 Minutes - the set of all 20 minute periods

- 3.345 Nanoseconds- the set of all 3.345 Nanosecond periods.

- Quater - the set all all quaters : 1 quater of 1492, 3rd quater of 2056, ....

- 7000 Years- the set of all 7000 Year period.

A  Period Type that is an arbitrary period of time.

 Period Type is used to define the period on which Time Events or Event Concepts can occur.

Examples:

- Year - the set of all years (..., -5000, ... 50, ..., 800, ..., 1000, ..., 1789, ..., 1946, ..., 2050, ...)

- 3.345 Nanoseconds- the set of all 3.345 Nanosecond periods.

- Quater - the set all all quaters : 1 quater of 1492, 3rd quater of 2056, ....

- 7000 Years- the set of all 7000 Year period.

A  Physical Capability is a Business Resource Capability provided by Physical Business Agents representing their ability to produce Physical Outcome Events.

A  Physical Capability defines WHAT a Physical Business Agent can provide.

 Physical Capabilitys are used to express the need of obtaining Physical Outcome Event that will be utilized by Physical Business Agents (people or some Business Systems ) when performing their job.

For internal users, these jobs correspond to Activitys described in Business Processes (see Instrument).

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

Examples:

- 3D Printing.

-  Automated Parcel Delivery.

- Metal Shaping.

Business Data lineage is about tracking the flow of information.

It is necessary to guarantee the quality, usability and security of business data.

For large organizations, it is also a key conformity legal requirement: BCBS 239, Solvency II.

Business Data Lineage is defined as a business data life cycle that describes the source of business data and where it moves over time.

An  Physical Software Interface is a physical specification of an Application Interface to which it adds the following physical characteristics:

1) The software communication protocol which defines the format of the data, the procedures for error handling, and the protocols for data transfer. Examples of software communication protocols include HTTP, SOAP, gRPC,

2) Potential specific target port number.

3) Optional restrictions on source port number to use .

4) Transport protocol (TCP/UDP).

 Physical Software Interfaces can also represent lower lever APIs supported by Software Technology Systems such as DHCP, SMTP, IMAP, LDAP.

A National Representative is a representative of the legal entity in one of the Member States where the data subjects, whose personal data are processed, are located.

A   Process Family is a category of Action Process.

Example: support processes, development processes, operational processes,

A  Product is a state of  a Resource Asset that represents merchandises offered for sale, either goods (produced as the result of manufacturing) or services (some work done by a Business Agent  which produces Business Outcome Events that benefits another Business Agent).

 Products are defined by their unique Value Propositions.

A Project Milestone defines an intermediate delivery gate in the project lifecycle.

Project Deliverables can be associated with a  Project Milesone in case they are delivered during the project and not at the end of the project.

Note: the association of deliverables to milestone do not affect their object life initialization; the object life should be manually updated accordingly if this is relevant.

A Project Portfolio gathers all the projects of a given Project Domain in the defined project state (Demands, Candidate Projects, Ongoing Projects).

In a Portfolio, Projects can be assessed and compared against several criteria:

- Projects Criteria: these are derived from projects information (e.g. costs) or from project qualitative assessment (e.g. strategic alignment level, business value level)

- Portfolio criteria: these are additional criteria which can be defined at portfolio level on top of the projects criteria (ex : score, priority, rank)

The project workflow can be actioned from the project portfolio lines.

Compulsory Policy, define by law, that is not directly enforceable whose purpose is guide enterprise activities.

 Regulation Articles are classified by Regulation section in the context of a Regulatory Framework.

A  Regulation section is a classification of  Regulation Articles.

 Regulation sections can be themselves organized as a classification hierarchy.

A  Regulatory Driver is an Exogenous Driver which includes acts of parliament and associated regulations, international and national standards, local government by-laws, and mechanisms to monitor and ensure compliance with these.

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  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  Resource Configuration is a generic class of System of Resources that represents System of Resources that are not Facilitys.(Data centers, Factories, Outlets).

Examples:

- Configured Nuclear power plant (with operating teams), 

- Configured aircraft carrier (with crew), Configured rescue ship (with rescue team).

When specific characteristics need to be considered for a given type of  Resource Configuration, it is recommended to create a new sub-type of System of Resources to host these characteristics.

A  Resource Operating Environment Scenario is a story that describes how a Resource Agent interacts with its partners (Partner Resource Agent) to achieve Business Outcome Events in a specific Resource Operating Environment.

This includes:

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

2) Interacting partners who participate to the story in the considered Resource Operating Environment.

A  Simple Field is a NoSQL Field that represent a single piece of data. A  Simple Field cannot be decomposed.

 Simple Fields are often described by their name, primitive type and length.

For instance, "customer name", "customer id" and "stree number" are usually considered as  Simple Fields.

A  Skill is an ability of a human resource to produce Business Outcome Events.

 Skills are acquired and refined through training and practice.

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  Software Technology Capability is a Technology Capability offered by Software Technology Systems and aimed at producing Software Technology Outcome Events.

 Software Technology Capabilitys define WHAT Software Technology Systems can do, They are used to understand whether two types of Software Technology Systems are fundamentally doing the same thing.

They are also used in Software Technology ArcOps to identify where there are redundancies in Technology Portfolios.

A  State Concept is Conceptual Entity which is a state of another Conceptual Entity.

Example:

- Employee is a state of Person. Its temporal boundaries are "hiring" and "departure" (see Event Concept).

A  State Concept Type is Class of Conceptual Entity which is a state type of another Class of Conceptual Entity.

Example:

- Employee is a state of Person. Its temporal boundaries are "hiring" and "departure" (see Event Concept).

A  Stored Procedure is a is a subroutine available to applications that access a relational database management system (RDBMS).

It is a kind of  Resource Process handled by RDBMS.

A  Structured Field is a NoSQL Field which is a combination of other NoSQL Fields.

For instance, an address in composed of a street field, a city field and a country field.

A  Switch is a Network Device used to connect multiple devices within a Computer Network, enabling them to communicate with each other.

A  Switch operates at the data link layer (Layer 2) of the OSI model, and it uses MAC (Media Access Control) addresses to forward data between Networking Systems.

A  System of Systems is a Macro Capability Configuration that combine several System of Resources to deliver a common high level  Business Capability.

Examples:

- Air traffic control system

- Smart city system

- Health Care System

- Search and Resue system (SAR)

- Naval squadron consisting of an aircraft carrier, its escort ships and its C5ISR capabilities.

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 Table is a relational data structure, used as the reference for the switch to production. The  Table is the central element of the relational databases.

A table is accessible by means of a primary key, and if necessary foreign keys; it is described by an ordered sequence of Columns. A  Table is generally derived from a Logical Data Entity or asssociation.

 Technology Portfolios are Asset Portfolios aimed at managing a set of Software Technologys delivering functionalities required by enterprise operations.

The purpose of  Technology Portfolios is efficiency: managed Managed Software Technologys must provide expected Software Technology Capabilitys in the best cost / performance ratio.

A  Technology Process is a  Action Process that describes a typical course of action intended to produce Technology Outcome Events, through the involvement of Technology Systems (System Participant).

During its course of action, a  Technology Process consumes or produces  Technology Objects:

1) It may memorize or access  Technology Objects from and to its Process Stores.

2) It may receive  Technology Objects at its boundary: Triggering Technology Outcome Events.

3) It may signal the production of  Technology Objects at its boundary: Produced Technology Outcome Events.

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

A  Transformation Program is an Initiative that is a temporary, flexible organisation created to co-ordinate, direct and oversee the implementation of a set of related Projects and Tasks in order to deliver outcomes and benefits related to the organisation’s strategic objectives.

A programme is likely to have a lifespan of several years. During a programme lifecycle, projects are initiated, executed, and closed.  Programmes provide an umbrella under which these projects can be co-ordinated. The programme integrates the projects so that it can deliver an outcome greater than the sum of its parts.

Programs are defined upon a given domain (e.g. Business, Information Technology)

A program domain gathers all the projects managed from the same perspective in terms of portfolio management decisions. Project Portfolios are therefore also attached to programs; by default, one portfolio of each portfolio type is created when creating a new program.

A  Value Proposition is a distinctive Asset Property that outlines a set of specific benefits a Product (whether goods or services) delivers to its Customers, emphasizing how it satisfies their needs and offers value. It is essentially a promise made by the Enterprise to its target Customers that its Product will fit their need when performing their Job-to-be-done.

A  Value Proposition is a characteristic of a Products (a  Product Characteristic) and is defined by:

1) its Functional Value expressed as qualified and quantified  Business Capabilitys and their Business Outcome Events,

2) its Non Functional Value expressed by Condition Propertys.

 Value Streams are used to frame the Conceptual Operating Model of the enterprise: they describe how the enterprise shall operate, at the conceptual level, and helps chunking responsibilities between Conceptual Agents (Operating Domain or Business Function) .

In the EA context, a  Value Stream is a conceptual Action Process that represents an overarching perspective of the organization's processes aiming at producing Conceptual Outcome Events. The focus is on shaping and understanding the functional relationships and roles within the enterprise : its functional division of labor.

This is not to be confused with Value Stream Mapping (VSM) which is focused on Lean optimization and is addressed with the concept of  Business Process (see the Organization & Processes domain).

A  Value Stream is performed by Conceptual Agents who produce Conceptual Outcome Events. It is depicted as a sequence of Value Stream Stages, controlled by events and conditions.

 Value Stream Activitys are carried out by the involvment of Conceptual Agents as participants in the  Value Stream.

During its course of action, a  Value Stream consumes, produces or stores  Business Objects.

1) It may read or write Domain Assets in its Business Object Store.

2) It may receive Domain Assets at its boundary:  reacted to Business Outcome Events.

3) It may produce Domain Assets at its boundary:  produced Business Outcome Events.

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

There are traditionnaly two kinds of  Value Streams:

1) Development development  Value Streams define all of the actions, both value-creating and nonvalue-creating, required to bring a Product from concept to launch.
2)  Operational  Value Streams define define all of the actions, both value-creating and nonvalue-creating, required from order to delivery. These include actions to process information from the  Customer and actions to transform the product on its way to the Customer.

A Vision describes the future state of the enterprise, without regard to how it is to be achieved.

A Vision is the ultimate, possibly unattainable, state the enterprise would like to achieve.