| Description | Dictionary of abstractions and patterns at the foundation of the SysFEAT Framework. |
|---|---|
| Parent Dictionary | Systemic Framework for Enterprise Architecture & Transformation |
| Top Level Map |
SysFEAT Foundation Ontology Map |
| Name | Description |
|---|---|
Appraisal Pattern | The Appraisal Pattern domain defines constructs used by stakeholders to assess and qualify Asset Blocks. |
Architecture Assets | The Architecture Assets domain defines top level constructs used in enterprise architecting: Asset Types, Asset Category(ies), Asset Property(ies). |
Architecture Packages | The Architecture Packages domain defines how Asset Blocks are grouped and packaged. |
Architecture Packaging | |
Compositionality | The purpose of the Compositionality family of concepts is to provide syntactic mechanisms that support the construction of composite Building Blocks. The Compositionality pattern handles situations where Building Blocks have an internal structure. Such Building Blocks are called Aggregate Blocks. They are made of internal nested Entity Elements called Aggregate Members. Aggregate Members contextualizes Building Blocks living outside the Aggregate Block structure (specialization in OMG - Kernel Modeling Language (KerML) is such an Aggregate Member). Advanced Aggregate Block features are provided by Bounded Aggregates which hide their internal structure to the outside world by means of a formal boundary (see Connection Relationship). |
Directed E/R Graph | The Directed E/R Graph domain defines the top level constructs of entity (Entity Element) and their relationships (Relationship Element). It is the second layer of SysFEAT's graph architecture. SysFEAT is based on a node-centric definition of graphs, aligned with practical implementations like adjacency lists in programming To leverage graph defintions, SysFEAT has adopted a layered approach of relationship formalization: 1) It starts by explicitly encoding directed edges as set-based constructs: Adjacency List. 2) Adjacency Lists are then reified to create direct relationships between Relationship Elements: Relationship Elements. 3) Further structuring of Entity Elements and their Relationship Elements is provided by the Compositionality pattern that layouts the concepts of locality and connections. |
Elementary Graph | The Elementary Graph domain defines the basic constructs for relating and classifying Elements in a directed graph. SysFEAT is based on a node-centric definition of graph that follows the principal of lexical locality. It defines the concepts of entity (Entity Element) and relationship (Relationship Element) as specific kinds of nodes. To implement the principle of locality in graph definitions, SysFEAT has adopted a layered approach of relationship formalization: 1) It starts by explicitly encoding directed edges as Kuratowski pair , <a,b> = { {a}, {a,b} }, represented as: Adjacency List. 2) Adjacency Lists are then reified to create direct relationships between Entity Elements: Relationship Elements. 3) Further structuring of Entity Elements and their Relationship Elements is provided by the Compositionality pattern that layouts the concepts of locality and connections. |
Governance Pattern | The Governance Pattern domain defines organizations and instrurments required to govern Enduring Initiatives. |
Information Assets | The Information Assets domain describes top level concepts used to describe information. |
Information Packaging | |
Initiative and Transformation Pattern | The Initiative and Transformation Pattern domain defines management concepts required for transformation initiatives. It provides principles for the coordination of large scale initiatives evolving over time (Enduring Initiative and their Initiative Stages). |
Legend | |
Measurement | |
Model Block Packaging | Model Block Packaging family of concepts defines the different kind of Building Blocks used in system and enterprise modeling: |
Packaging | The Packaging domain defines the core elements of Building Block and Container which provide the basis for building modules. Building Blocks are reusable units They have an independent existence. Thereby, they cannot be nested in other structures which would hide their existence (lexical scope). Because of their independent existence, they must be owned by an independent artifact which sole purpose is model management Containers . Containers are dedicated to model management: . They own blocks to which they provide existence. . They can provide namespace to blocks. . They have dependencies on other Containers which blocks have relationships to blocks they packaged. |
Policies | The Policies domain defines Directives and Behavioral Rules that constrain enterprise structures (Agents structure) and Behaviors. |
Resolution & Decision | The Resolution & Decision domain defines constructs used by stakeholders to assess and qualify Functional Assets. |
Risk & Threat | |
Semantic | The purpose of the Semantic pattern is to provide meaning through the definition of Ontological Blocks, described by their Typology Relationship (Classification and Specialization), and their Temporal Sequencing. - Composition (Whole/Part) combines Individuals to form whole-part hierarchies. - Classification distributes Ontological Blocks into Ordered Semantic Classes of the same type, through instance->type relationship. It starts with Ontological Blocks that are classifed by Ordered Semantic Classes and allows for multilevel of classification ( higher-order) of Ordered Semantic Classes by Class of Classes. Individuals introduce spatio-temporal concerns in the ontology by representing Ontological Blocks that exist over space and time. Specialization provides a specialization/generalization relationship between Ordered Semantic Classes. |
System Operating Framework - SOF | The System Operating Framework - SOF models how an active system (Agent) operates/functions (Behavior) in its Operating Eco-System to produce Outcome Events that benefit (value) to other Agents or affect (have an effect upon) these Agents. The SOF includes Agents, Action Processes, Interaction Processs, Policy(ies), Capability(ies), Outcome Events. |
Systemic Operating Ontology | The Systemic Operating Ontology domain bundles sub-domains used to model how a system, including an enterprise, operates/functions in its environment. It includes Agents, Action Processes, interactions , Behavioral Rules, Capabilityies, Outcome Events, Information Assets and Directives. |
Teams Pattern | The Teams Pattern domain defines organization structure and behavior as well as instrurments required to govern Enduring Initiatives. Any Initiative, (project, enterprise, asset portfolio, privacy insurance, etc.) shall be governed. This includes: 1. Governance Committees in charge of governance. They comprise persons and the role of these individual in the team (architects, auditors, product owner, etc.). 2. Governance Events describe changes that need to be recorded to monitor transformations (décisions, incidents, etc.). 3. Governance Activity(ies) describe all actions that come in response to change events and may results in other change events (workflow, audits, ...). 4. Measurement Instruments provide KPIs (qualification and quantification) on the status of Undertakings being governed. |
Upper Ontology | The Upper Ontology domain encompasses six fundamental domains that establish the foundation for the modeling syntax and semantic. 1) Elementary Graph defines basic constructs for relating and classifying elements in a directed graph. 2) Directed E/R Graph defines the elementary constructs for entities and relationships. 3) Packaging defines syntactic constructs used to package reusable entities( Building Blocks) in modules called Containers. 4) Compositionality defines the syntactic constructs used to build Entity Elements that have an internal structure and boundaries. 5) Packaging defines syntactic constructs used to organize models in modules called Containers. 6) Semantic defines Bounded Individuals (entities that exists over space and time how they are composed and classified, enabling effective representation of meaning. |
| Name | Description |
|---|---|
| A | |
Adverse Event (Individual) |
|
Advise |
An Advise is time bound Resolution, agreed upon by Stakeholders to recommend what can or cannot be done regarding an Asset Block. |
Appraisal Date |
|
Appraisal Option |
An Appraisal Option is a Property associated with an Appraisal Type representing a potential appraisal value that can be chosen during an appraisal process. For instance, when making decisions about invesment on an enterprise asset, the possible options can be: eliminate, invest, migrate. |
Architecture Block Collection |
An Architecture Block Collection is a collection of Asset Blocks usually created for model management purposes, such as validating or sharing a set of Asset Blocks. |
Architecture Decision |
An Architecture Decision is a Decision that can apply to any kind of Asset Block. |
Architecture Decision Option |
An Architecture Decision Option is a Decision Option that can apply to any kind of Asset Block. |
Architecture Decision Type |
|
Assessment Value |
An Assessment Value is an Appraisal Option associated with an Assessment Type, representing a potential value that can be chosen during an assessment process. |
| b | |
build |
|
| C | |
Category Partition |
|
Class Partition |
|
Concept Type |
|
Contextualized Targeted Threshold |
|
Credit Risk |
|
CRUD |
|
| D | |
Data Category |
A Data Category is a classification or division of Information Assets regarded as having particular shared characteristics. Examples: . Health data, . Financial data, . Contact data. |
Decision Option |
A Decision Option is a possible value of a Decision Type, that will be selected during a decision-making process. For instance, when making decisions about invesment on an enterprise asset, the possible options are: eliminate, invest, migrate, tolerate. |
Description Note |
A Description Note is an Annotation Block whose body in describes its in Annoted Element in natural language.
|
Directive |
A Directive is an authoritative declaration that indicates how Agents and their Behaviors should be (or should not be) in the enterprise. Specifically, a Directive defines, constrains or liberates some aspects of an Agent and its Behaviors. As such, Directives shall be considered as constraning Asset Propertys. Directives are intended to assert agent structures or to control or influence their Behaviors. Directives are stated in declarative form. |
Documentation |
|
| E | |
Environmental Condition Type |
An Environmental Condition Type is a class of Environmental Property Type. Example: PESTEL (political, economic, social, environmental, legal), physical conditions (weather conditions, terrain conditions,) It is used to group Environmental Property Type(ies) by domain of concerns represented by Family of Measurement. |
Environmental Property |
An Environmental Property is a specific value of an Environmental Property Type. Environmental Propertys are used as constraints on Asset Blocks in the context of non-functional requirement analysis and Value Proposition analysis. Examples: - Muddy, frozen ground, deep snow (Terrain Type), - Broad daylight, dusk, moonlit (Light condition). |
Environmental Property Type |
An Environmental Property Type is a characteristic of the environment in which an Enterprise or its sub-systems are required to operate. Examples: . Terrain Type: muddy, frozen ground, deep snow, etc; . Light conditions: broad daylight, dusk, moonlit, etc; . Weather condition: stormy, sunny, cloudy, etc; . Polical conditions: political stability, level of education; . Economical conditions: exchange rates, inflation rate. |
| F | |
Family of Category |
A Family of Category is a Top level group of categories that belong to a common domain. For instance, the GDPR categorization schema groups all categories relevant to GDPR such as data categories, sensitive activities. |
Family of Measurement |
A Family of Measurement is a top level grouping of Condition Property Type(ies) that belong to a common domain. |
| G | |
Governance Activity |
A Governance Activity is an action done by one or several Stakeholders as part of the governance of an Enduring Initiative. Governance Activity(ies) range from assessments, audit, workflows to remediation plans. |
Governance Committee |
A Governance Committee is a group of Stakeholders that contributes to architecting and assurance activities and governs Enduring Initiatives. |
Governance Property Type |
A Governance Property Type is a classification of Governance Propertys. |
| I | |
Individual Stakeholder |
An Individual Stakeholder is a person with a Stakeholder role in architecting & assurance activities. |
Initiative Instrument |
An Initiative Instrument is a resource and course of actions defined by Enduring Initiatives to achieve its objectives. For instance: Data Controls are mechanisms used to ensure data quality and data integrity Privacy Representatives are used to identify national entities in charge on privacy. |
Initiative Milestone |
An Initiative Milestone is a calendar change that marks the end of an Initiative and possibly the beginning of another. |
| L | |
Library |
A Library is a kind of Architecture Container used to split SysFEAT repository content into several independent modules (aka package). They allow virtual partitions of the repository used for model management. In particular, Asset Blocks owned by different Library(ies) can have the same name (namespacing). |
Location |
A Location is a geopolitical location anywhere on the earth. Examples: - France - Paris - Washington DC - Cairo - Buenos-Aires - Asia |
Location Type |
A Location Type is a type of Location that is a geopolitical location. Example: - Continent - Country - City - District - Street |
| M | |
Management Initiative Committee |
A Management Initiative Committee is a Governing Team responsible for overseeing the administration of a Management System. |
Measurable Data Quality |
|
Measure Property |
A Measure Property is a possible value of a Measure Property Type such as a delivery time of 30 minutes, a weight of 20 kg, a high level of confidentiality. It represents how much there is or how many there are of something that you can quantify according to its Constraining Measurable Property. Measure Propertys are used as constraints on Asset Blocks in the context of non-functional requirement analysis and Value Proposition analysis.
|
Measure Unit |
A Measure Unit defines the units used for Measurable Propertys. Examples are minutes (Time Measure Type), kg (Mass Measure Type) , euros (Amount Measure Type) etc. |
Measurement Type |
A Measurement Type is a class of measurement. Example: Performance, Security, Cost. It is used to group Measure Property Type(ies) by domain of concerns represented by Family of Measurements. |
Measurement Value |
A Measurement Value is the value of Measure Property Type that result from a Measurement, at specific point in time in the context of a Key Indicator. A Measurement Value is always nested by its Measurement. |
| O | |
Ordered Class |
Ordered Class is defined as the Meta-Class of all power type based Class of Entity Elements. |
| P | |
Parent Category |
|
Parent Policy Category |
|
Parent Risk |
|
Policy Asset |
A Policy Asset is any topic related to policy definitions. It ranges from the different kinds of Directives (Business Policy, Architecture principle, Behavioral Rule, etc.), to classification of policies (Policy Category) up to an entire set of policies (Policy Framework). |
Policy Conformance |
|
Policy Decision |
A Policy Decision is a Decision that defines the applicability status of a policy to a set of Functional Assets. |
Policy Decision Option |
|
Policy Decision Type |
|
Policy Framework |
A Policy Framework is a set of Policy Assets, defined in laws published by governements or in policy frameworks defined by the enterprise. Both Business Policy Frameworks and Regulatory Frameworks are Policy Framework(ies).
|
Process Family |
A Process Family is a categorization of Business Operating Assets used to assert that a Business Operating Asset belongs to a specific process domain. |
| R | |
Resolution Type |
A Resolution Type is an Appraisal Type that refers to a kind of Resolution used to guide what can or cannot be done regarding a specific Asset Block. Resolution Types define a set of Resolution Options which are the possible values that will result from a resolution process. For instance, when making decisions about invesment on an enterprise asset, the possible options can be: eliminate, invest, migrate. |
Responsibility Assignment |
A Responsibility Assignment is a governing duty assigned to an Individual Stakeholder on a particular asset ( Functional Asset). |
Review Note |
Review Note is a comment used by a Stakeholder to annotate Repository objects. Review Notes are the bases to follow a conversation between Stakeholder on a dedicated object. |
| S | |
Set of Condition Properties |
A Set of Condition Properties is a 'And' combination of Condition Propertys. Example: . Delivery time of 30 minutes, at a cost ranging between $8.50 and $10, in stormy conditions.
|
Set of Environmental Condition Type |
A Set of Environmental Condition Type is an "and" combination of Condition Property Types. Example: . "Delivery time" at "appropriate cost" in "stormy conditions".
|
Specialized Class of Class |
|
Specialized Property Type |
|
Systemic Levels |
|
| T | |
Tag |
A Tag is a general classification description which permits non formal characterization of Entity Elements. All Entity Elements can be tagged. |
Time Event |
A Time Event is a Behavioral Event that signifies the happening of a time change used to coordinate Behaviors. |
| V | |
Vendor Catalog |
A Vendor Catalog is a package of resources offered by a Vendor. |
| W | |
Waiver End |
|
Whole Life Asset |
A Whole Life Asset is a Individual Asset that is not the temporal slice of any other Individual Asset. A Whole Life Asset includes its past and future. Examples: . The Eiffel tower (31st March 1889 - ...). . William Shakespeare (23 April 1564 - 23 April 1616). . Confucius (685-758). . Mount Vesuvius eruption (Aug. 24-25, A.D. 79). . Oackland digital hospital (1994 - ...). . The registration process used at the Oackland digital hospital during the COVID-19 pandemic (17 March 2020 - 1 May 2020). |
| Name | Description |
|---|---|
| A | |
Abstract Entity Element |
Abstract Entity Element is a class of Entity Elements that cannot have direct instances. Example: 1) Aspects of Entity Elements, such as Lexical Scope. 2) Individual Propertys of Individuals. |
Action Process |
An Action Process is a Behavior that describes a typical course of action intended to produce Outcome Events, through the involvement of Agents as Active Participants. During its course of action, a process consumes or produces Functional Assets, including Information Assets. 1) It may memorize or access Information Assets from and to its Process Stores. 2) It may receive Functional Assets at its boundary: Outcome Consumptions. 3) It may signal the production of Functional Assets at its boundary: Outcome Productions. The course of actions of a Action Process is constrained ( Rule Enforcement) by the application of Behavioral Rules that define what is allowed and not allowed to do. Within SysFEAT, we can examine Action Processes from two distinct perspectives: a) A conceptual standpoint is provided by Value Streams. b) A concrete implementation standpoint is provided by Resource Action Processes. |
Adjacency Item |
An Adjacency Item is a member of an Adjacency List, and represents an elementary constituent of a model, used to reference an Element. It is a basic construct to form Adjacency Lists. An Adjacency Item is either a Reference Adjacency or a Nesting Adjacency . |
Agent |
An Agent is an Operating Asset which is able to participate actively to Behaviors, to produce and react to Outcome Events. 1. Agents participate to Action Processes (Active Participant) and/or conduct Action Processes (Performed Process). 2. Agents participate to Interaction Process (Scenario Participant) describing how they interact with other Agents. These actions and interactions define Agents boundaries described by Service Interfaces.
|
Agent Environment |
An Agent Environment is an Operating Eco-System which defines the interactions (Service Channel) of an Agent with its partners (Partner Agent). |
Agent Life Cycle Event |
An Agent Life Cycle Event is a Temporal Bounding Type that defines the boundaries of an Agent's life cycle. |
Agent State |
An Agent State is a temporal slice type of an Agent related to its lifefcyle. Examples: . The lifecycle phases of a person, such as childhood, adulthood, eldery stage. . The lifecyle phases of a hospital such as construction phase, operation and maintenance phase, renovation and expansion phase, decommissioning phase. |
Aggregate Block |
An Aggregate Block is a Building Block which has an internal structure made of Aggregate Members which, through nesting (Membership of <Aggregate Member>), contextualizes/aggregates (Aggregation ) external Building Blocks within the Aggregate Block. |
Aggregate Entity Block |
An Aggregate Entity Block is a self-contained and independant Aggregate Block that is not a Connection Relationship. An Aggregate Entity Block can have both Unbounded Members, which enable aggregation of external Aggregate Entity Blocks, and Bounded Members which can be inter-connected. Examples: - Operating Eco-System; - Directive; - Agent. |
Annotation Block |
An Annotation Block is a Building Block used to provide additional characteristics such as Documentations, Examples: Tags.
|
Appraisal |
An Appraisal is a time bound statement expressed by stakeholders to qualify Asset Blocks with respect to their worth. Assessments and Decisions are two major types of Appraisals provided by SysFEAT. |
Appraisal Type |
An Appraisal Type refers to a kind of Appraisal method and technique used to evaluate the worth, effectiveness, compliance, or quality of enterprise Asset Blocks. Appraisal Types define a set of Appraisal Options which are the possible values that will result from an Appraisal activity. For instance, when making decisions about invesment on an enterprise asset, the possible options can be: eliminate, invest, migrate. Assessment Type and Resolution Type are the two appraisal techniques provided by SysFEAT. |
Architecture Block |
An Architecture Block is any Model Building Block used to describe the architecture of a system (including the enterprise). This includes Asset Blocks (Applications, org-units, Business Functions, Business Processes...) and Individual Architecture Assets (physical persons, software installations, locations, ...). |
Architecture Container |
An Architecture Container is a Model Container that packages Asset Blocks used for enterprise architecture descriptions. This includes Information Asset, Processes, Software Systems, Hardware Systems, Organizations, etc. Model Containers are used to split SysFEAT repository content into several independent modules (aka package). They allow virtual partitions of the repository. In particular, Asset Blocks packaged by different Model Containers can have the same name (namespacing). |
Architecture Lexical Scope |
An Architecture Lexical Scope is a kind of Model Lexical Scope for Architecture Blocks. |
Assessment |
An Assessment is the result of the act of judging or assessing an aspect of the enterprise, based on an enterprise description and on the comparison of this description with the actual state of the enterprise. An Assessment is made by one or several Stakeholder s. |
Assessment Process |
An Assessment Process is an Governance Activity carried out over a determined time period. When an assessment session is published, an assessment questionnaire containing questions is sent to targeted assessors. |
Assessment Type |
An Assessment Type refers to a kind of Assessment method and technique used to evaluate the worth, effectiveness, compliance, or quality of enterprise Asset Blocks. Assessment Types define a set of Assessment Values which are the possible values that will result from an Assessment. |
Asset Block |
An Asset Block is an Architecture Block used to describe the System Operating Framework - SOF of the enterprise and its systems. |
Asset Category |
An Asset Category is a Category used to classify Asset Blocks. There are different kinds of Asset Category that applies only to certain subtypes of Asset Blocks. For instance: . Data Category applies to Information Assets. . Process Family applies to Resource Operating Assets. . Risk Type applies to Functional Assets. |
Asset Property |
Example: . Capabilities (as a functional property). . Environmental conditions. . Directives. |
Asset Property Type |
An Asset Property Type is a classification of Asset Propertys. |
Asset State |
An Asset State is a temporal slice type of an Asset Type. Examples: . The lifecyle phases of buildings such as a skycraper: construction phase, operation and maintenance phase, decommissioning phase. . The lifecycle phases of a person, such as childhood, adulthood, eldery stage. . The phases of a volcanic eruption: magma accumulation, plinian phase, eruptive phase, effusive phase, declining phase. . The lifecyle phases of a hospital such as construction phase, operation and maintenance phase, renovation and expansion phase, decommissioning phase. |
Asset State |
An Asset State is a temporal slice of a Individual Asset. Examples: . The state of the Eiffel tower during the 1900 World Fair, with its improved elevators and electric illuminations (Apr 14, 1900 - Nov 12, 1900). . William Shakespeare in its early theatrical career (1592-1600). . Confucius in its early childhood. . The first Plinian phase of the Mount Vesuvius eruption (18 to 20 hour, Aug. 24 A.D. 79), that projected a column of volcanic debris and hot gases. . Oackland digital hospital after its renovation (2022 - ...). |
Asset Type |
An Asset Type is a Class of Individual which is used in the description of the enterprise and its systems, such as Action Processes, Department Types, Applications, Location Types, Period Types.
|
Assurance Initiative |
An Assurance Initiative is an Initiative designed to uphold operational trustworthiness by mitigating Risks, countering threats, and complying with regulatory requirements. |
Assurance Instrument |
An Assurance Instrument is a resource or course of actions used by an Assurance System to achieve its objectives. For instance: Actions plans are course of actions aimed at solving incidents. Data Controls are mechanisms used to ensure data quality and data integrity Privacy Representatives are used to identify national entities in charge of privacy. |
| B | |
Behavior |
A Behavior is an Operating Asset that describes any action or reaction of an Agent to external or internal Behavioral Events. Behaviors include Action Processes (action), Interaction Processs (stories) or interactions (Service Interface). The course of actions of a Behavior is constrained ( Rule Enforcement) by the application of Behavioral Rules that define what is allowed and not allowed to do. |
Behavioral Event |
A Behavioral Event is a Temporal Bounding Type that establishes a temporal connection between Behaviors. A Behavioral Event connects a Predecessor Behavioral Event, to a Successor Behavioral Event. |
Behavioral Rule |
A Behavioral Rule is a Directive intended to guide the Behavior of Agents, in compliance with enterprise Policy(ies) or regulations. |
Block Collection |
A Block Collection is an Entity Element that is a grouping of Building Blocks. The grouping of Building Blocks can be achieved either by reference (Referencing Relationship) or by nesting (Nesting Relationship), in which case the Block Collection serves as a Lexical Scope. Example: - Container Package as a Block Lexical Scope. - Asset Portfolio as a pure Block Collection. |
Block Lexical Scope |
A Block Lexical Scope is a Block Collection that is also a Lexical Scope for the Building Blocks it groups. A Block Lexical Scope defines the existence of its Building Blocks through nesting.
|
Bounded Aggregate |
A Bounded Aggregate is an Aggregate Entity Block which hides its internal structure to the outside world by means of formal Borders. The only way to access a Bounded Aggregate is through its formal Borders, which ensures the aggregate's internal consistency. The Borders of a Bounded Aggregate is determined by the Connection Relationships it can participate to. Within a Bounded Aggregate structure, Bounded Members can be linked together through Connectors. The nature of Connectors is given by their associated Connection Relationship. Examples: - Action Processes are bounded by their start and end events (see Behavioral Event). |
Building Block |
A Building Block is an autonomous, Entity Element that contributes to the makeup of other Building Blocks. Building Blocks can be either reusable entities (packaged in Containers) or be local to the Aggregate Block that references them (see Block Lexical Scope and Hierarchical Member). Examples: - Functionality(ies), Business Process(es), Data Entity(ies), Tags, ARE Building Blocks. - Process Steps or Attributes of a data entity ARE NOT Building Blocks. They are members on an internal structure (see Aggregate Member). |
| C | |
Capability |
A Capability is a functional Asset Property which refers to the ability to produce an Outcome Event. Capabilitys are fulfilled by Agents performing Processes and interacting with other Agents to produce the desired Outcome Event. |
Capability Map |
Top level assembly of Capabilitys and their dependencies which, together, provide a scope of added value (Outcome Events) pursued by Operational Transformations. |
Category |
A Category is a used to classify Class of Bounded Individual. |
Category of Initiative |
|
Class of Bounded Individual |
A Class of Bounded Individual is a Class of Individual which denotes Bounded Individuals that have a proper life cycle, bounded by Temporal Bounding Types. Class of Bounded Individual is the powertype of Bounded Individual. It means that all sub-types of Bounded Individual are instances of Class of Bounded Individual. Examples: - Car, , Application, - A Process Type (Action Process) such as the registration process used at the Oackland digital hospital during the COVID-19 pandemic. Counterexamples: - Project is not a Class of Bounded Individual because its instances have a spatio-temporal extent. Project is a subtype of Bounded Individual. - Capability is not a Class of Bounded Individual. It is a Property. |
Class of Class of Bounded Individual |
A Class of Class of Bounded Individual is a Class of Class of Individual which is the powertype of Class of Bounded Individual . It means that all sub-types of Class of Bounded Individual are instances of Class of Class of Bounded Individual. |
Class of Class of Individual |
The powertype of Class of Individual.
|
Class of Entity Element |
A Class of Entity Element is a Class of Element that classifies Entity Elements. Being a subtype of Entity Element, it is also an instance of itself. |
Class of Individual |
A Class of Individual is an Ordered Semantic Class of Ontological Blocks that exist in space and time. It is the powertype of Individual. Class of Individuals are represented as dark orange boxes (see the Meta-Model Legend) . Examples: - Red; - 12 kg; - Top Secret (TS) confidentiality. - Birth, - Death, |
Condition Category |
A Condition Category is a class of Condition Property Type. Example: Measurement Types (Performance, Security, Cost), PESTEL (political, economic, social, environmental, legal) It is used to group Condition Property Type(ies) by domain of concerns represented by Family of Measurement. |
Condition Property |
A Condition Property is a possible value of a Condition Property Type such as a delivery time of 30 minutes, a weight of 20 kg, a high level of confidentiality, stormy conditions. A Condition Property is either a single measure (Measure Property: a weight of 20 kg), an Environmental Property (stormy conditions.) or a Set of Condition Propertiess. Condition Propertys are used to constrain Asset Blocks in the context of non-functional requirement analysis and Value Proposition analysis. Examples: . Cost of 100€ . Delivery time of 30 minutes. . Weight of 20 kg. . Temperature of 18 degree Celcius. |
Condition Property Type |
A Condition Property Type expresses a type of constraint that can be applied to Asset Types. These constraints can be either Measure Property Type (Time, Mass, Cost, ..), Environmental Property Types (Terrain Type, Light conditions, Weather conditions) or a grouping of these (Set of Environmental Condition Type). Condition Property Types are used to constrain Asset Blocks in the context of non-functional requirement analysis and Value Proposition analysis. |
Connection Relationship |
A Connection Relationship is an Aggregate Block that defines possible connections between the Borders of two or more Bounded Aggregates. Examples: |
Container |
A Container is a collection of Building Blocks whose existence and meaning are defined by the Container. A Container is both: 1. A Lexical Scope: the meaning and usage of a Building Block is only applicable within the context of the Container to which it belongs. 2. A universe of discourse: the complete range of Building Blocks that are expressed, assumed, or implied in an architecture domain. Examples: - Library - Enterprise |
Container Package |
A Container Package is a Container which sole purpose is model management. Examples: Library, Information Dictionary Conterexamples: Enterprises or Infrastructure Landscapes are Containers but are not Container Packages because they have functional purposes that go beyond model management. |
| D | |
Data Risk Type |
A Data Risk Type is a Risk Type that refers to the accuracy, consistency, and reliability of data during its entire lifecycle. |
Decision |
A Decision is a time bound Resolution, agreed upon by Stakeholders, to state what shall or shall not be done regarding a specific Functional Asset. Architecturally significant decisions that are been made in the organization typically includes: a) Product selections b) Justification for major architectural features of projects c) Standards deviations d) Standards lifecycle changes e) Change Request evaluations and approvals f) Re-use assessments |
Decision Type |
A Decision Type is a Resolution Type that refers to a kind of Decision used to state what shall or shall not be done regarding an enterprise Asset Block. Decision Types define a set of Decision Options which are the possible values that will result from a decision-making process. For instance, when making decisions about invesment on an enterprise asset, the possible options can be: eliminate, invest, migrate. |
| E | |
Element |
An Element is an elementary constituent of a model. It is the top level abstraction of the SysFEAT upper ontology. |
Elementary Block |
An Elementary Block is a Building Block which doesn't have an internal structure. |
Enduring Initiative |
An Enduring Initiative is a long term Initiative which involves roadmapping and governance. Enterprises and their Management Systems are typical Enduring Initiatives. 1. Enduring Initiatives are purpose-oriented. 2. Enduring Initiatives are change management systems: they have objectives regarding the purposes they pursue, maintain and develop. 3. Enduring Initiatives are measured to ensure they meet their Goals. 4. Enduring Initiatives are organized according to subsidiary levels, ensuring autonomy and ownership at each level of delegation while providing responsibility and accountability in achieving common goals. 5. Enduring Initiatives are under the control of an associed Governing Team. 6.Governing Teams have instruments used to carry out governance: responsibility assignment, assessments, workflow, decision records, incident records. |
Entity Element |
An Entity Element is a distinct, identifiable Element that has a proper existence (living or non living). It is accessible by some referencing mechanism and can establish elementary relationships (Relationship Element) to other Entity Elements. |
Environment Interaction Process |
An Environment Interaction Process is a story that describes how an Agent interacts with its partners (Partner Agent) to achieve Outcome Events in a specific Operating Eco-System (Agent Environment). This includes: 1) A course of events represented by Object Flows depicting the succession of intermediate Outcome Events towards the production and consumption of final Outcome Events. 2) Interacting partners who participate to the story in the considered Operating Eco-System. |
| F | |
Family of Class |
|
First Order Class |
First Order Class is defined as the Meta-Class of all subclasses of Particular Entity Element. Each instance of First Order Class is a Class of Entity Element, each of whose instances is necessarily an Particular Entity Element. The class Particular Entity Element is an instance of First Order Class since, by definition, all of its instances are Particular Entity Element |
Functional Asset |
Functional Assets encompasse all Architecture Asset Types used to describe why and how systems operate/function. This includes the Operating Eco-System where system operates to fulfill these purposes (Agents and their Behaviors). Functional Assets include: 1. Blocks defining results of Behaviors of the enterprise or its sub-systems, that benefit to it internal or external customers : Outcome Event, 2. Blocks used to describe information: Information Asset. 3. Blocks used to describe how the enterprise operates: Operating Assets (Agent, Behavior, Service Interface). |
| G | |
Governance Building Block |
A Governance Building Block is a Model Building Block that is participate to the overarching of transformation Initiatives. |
Governance Container |
Container of Model Building Blocks used to measure, assess, monitor transformation Initiatives . |
Governance Event |
A Governance Event is any event that has an impact on the management and governance of an Enduring Initiative. |
Governance Instrument |
Governance Instruments include all instruments used to monitor and steer transformation Initiatives. They include incidents, assessments, indicators and their templates. |
Governance Property |
A Governance Property is a Property used to measure Asset Blocks during governance activities. |
Governing Team |
A Governing Team consists of a collection of individuals and resources, including personnel and committees, assembled to effectively oversee the management of an Enduring Initiative. |
| I | |
Individual |
Individuals are Ontological Blocks which represent things that exist over space and time. Individuals are represented as light orange boxes, while there classes are represented as dark orange boxes (see the Meta-Model Legend) . Examples: . The Eiffel tower completion (31st March 1889) . The Eiffel tower (31st March 1889 - ...). . William Shakespeare birth (1592) . William Shakespeare in its Early Theatrical Career (1592-1600). . Confucius (685-758). . Confucius death (758). . Mount Vesuvius eruption (Aug. 24-25, A.D. 79). . Oackland digital hospital after its renovation (2022 - ...) . The execution of the registration process at the Oackland digital hospital, by John Smith, on 17 March 2020. |
Individual Agent |
An Individual Agent is an Individual Operating Asset that exists in space/time and that is able to participate actively to Action Processes and/or to conduct Action Processes. |
Individual Asset |
An Individual Asset is an Individual which is used in the description of the enterprise and its systems. Individual Assets can be qualified by Condition Scale Values.
|
Individual Behavior |
An Individual Behavior is an actual instance of Behavior that is bounded in time. |
Individual Event |
An Individual Event is a Temporal Bounding that establishes a temporal connection between Individual Behaviors.
|
Individual Macro Operating Asset |
An Individual Macro Operating Asset is an Individual Operating Asset which correspond to a large-scale enterprise assets. This level of analysis is concerned with understanding how large enterprise systems operate and how they interact with each other. Examples of macro-level systems: . Legal entities . The overall enterprise IT System . The internet . System of Systems . The Enterprise itself., |
Individual Mezzo Operating Asset |
A Individual Mezzo Operating Asset at is the intermediate level between the foundational Individual Mezzo Operating Assets and the overarching Individual Micro Operating Assets. At the mezzo level, aggregates or collections of Micro Operating Assets come together to form larger entities or sub-systems. Boundaries and signals at the mezzo level arise from the interactions and emergent behaviors of micro-level components, yet they also have their own distinct properties and rules not strictly reducible to the micro behaviors. Emergence at the mezzo level can be analyzed: 1) Bottom-up: Looking at how interactions and behaviors at the micro level give rise to emergent phenomena, structures, or behaviors at the mezzo level. 2)Top-down: Understanding how meso-level structures influence and constrain the behaviors and interactions of the micro-level components within them. |
Individual Micro Operating Asset |
A Individual Micro Operating Asset represents the foundational level at which a system's structure and interactions can be analyzed without further subdivision into smaller constituent parts. Individual Micro Operating Assets set the stage for how higher-level behaviors emerge. As one moves up to higher hierarchical levels (mezzo, macro, etc.), the signals and boundaries at each of those levels are influenced by the foundational interactions set at the micro level. |
Individual Operating Asset |
An Individual Operating Asset is a Functional Asset that describes the way Outcomes are produced and consumed: how (Individual Processes) and by whom (Individual Agents). |
Individual Process |
Individual Process is the root instance of Action Process.
|
Individual Resource Process |
Individual Resource Process is the root instance of processes performed by Individual Resource Agents. |
Individual State |
An Individual State is a temporal slice of a Bounded Individual. Examples: . The state of the Eiffel tower during the 1900 World Fair, with its improved elevators and electric illuminations (Apr 14, 1900 - Nov 12, 1900). . William Shakespeare in its early theatrical career (1592-1600). . Confucius in its early childhood. . The first Plinian phase of the Mount Vesuvius eruption (18 to 20 hour, Aug. 24 A.D. 79), that projected a column of volcanic debris and hot gases. . Oackland digital hospital after its renovation (2022 - ...).
|
Information Asset |
An Information Asset represents anything that can be communicated or memorized by an Agent to produce and react to Outcome Events. An Information Asset is either an Information Entity or an Information Property. The difference lies in their relationship to change and to time. Information Entity(ies) can change over time and have a lifeycle while Information Propertys are immutable characteristics. |
Information Block |
An Information Block is an Asset Block involved in the description of information. Information Blocks range from Information Assets to Information Domains. They are packaged in Information Dictionary(ies) and managed in Data Catalogs. |
Information Dictionary |
An Information Dictionary is a Model Package of Information Blocks used to describe an information architecture. This includes: 1. Information Domain which groups Information Entitys by unit knowlege required by an Agent to operate during Behavior execution. 2. Information Entity which constitute resusable unit of information that can change over time. 3. Concept Property which constitue immutable characteristics of Information Entitys. Concrete implementations of Model Packages are Business Dictionary, Logical Data Dictionary, etc. |
Information Domain |
An Information Domain is a family of Information Entity(ies) which constitutes a unit a knowlege required by an Agent to operate during Behavior execution. |
Information Element |
An Information Element is an Element that represents some memorized information, either an Information Asset or an Information Asset Relationship, produced and/or consumed by Operating Assets. |
Information Entity |
An Information Entity is an Information Asset that is not fundamentally defined by its attributes, but rather by its continuity. An Information Entity evolves over time and has states. For instance a person is an Information Entity. Employe is a state of a person. An Information Entity has relationships to other Information Entitys and can have Information Propertys.
|
Information Lexical Scope |
An Information Lexical Scope is a kind of Model Lexical Scope for Information Blocks. |
Information Map |
An Information Map is a Operating Property Map that is the top level grouping of Information Domains. Information Maps are used to provide navigationtop level entry points for Information Dictionary(ies) and to scope data management initiatives at the level of portfolio management ( Data Catalog), at the project level or at the Enterprise level (Enterprise Concept Map). |
Information Property |
An Information Property is an Information Asset that represents a characteristic (Property) of an Information Entity. An Information Property is fundamentally defined by its value. It doesn't evolve over time and is thereby immutable. Examples: . Address. . Customer Name. . Amounts, |
Initiative |
An Initiative is any piece of work that is undertaken or attempted under the responsibility of a Steering Authority. Initiatives range from single project to long term initiatives (Enduring Initiative) such as Enterprises. Initiatives are sychronized over time using Initiative Milestones.
|
Initiative Block |
An Initiative Block is a Model Building Block used to describe enterprise transformation and sustainability Initiatives. |
Initiative Resource Type |
An Initiative Resource Type is a type of Initiative Resource defined by Enduring Initiatives to achieve its objectives. For instance: Data Controls are mechanisms used to ensure data quality and data integrity Privacy Representatives are used to identify national entities in charge on privacy. |
Initiative Stage |
An Initiative Stage is a past, current or future state of an Enduring Initiative. The set of all Initiative Stages of an Enduring Initiative defines its Roadmap. |
Interaction Process |
An Interaction Process is a story (Behavior) that describes how the components of an Agent interacts to produce and consume Outcome Events. This includes: 1) A course of events represented by Object Flows depicting the succesion of intermediate Outcome Events towards the production of the final Outcome Events. 2) Interacting Agents who participate to the story.
|
| K | |
Key Indicator |
A Key Indicator is a collection of Measurement of Architecture Property regarding the valuation, over time, of a Measure Property Type that qualifies a specific Asset Block. |
| L | |
Lexical Scope |
A Lexical Scope is a kind of Abstract Entity Element that defines the existence, visibility, and accessibility of the entities nested within it through a Nesting Relationship. Nested Entity Elements have no independent identity or validity outside the lexical or structural scope in which they are defined - they exist only within and for the duration of their parent construct. Every Entity Element belongs to exactly one Lexical Scope. A Lexical Scope carries no intrinsic semantic meaning; it serves purely as a syntactic mechanism for establishing hierarchical containment. Examples: 1) Composite structures nesting their internal constituents. 2) Social structures nesting their roles and functions. 3) Computer functions nesting their local variables or inner functions 4) Packages nesting their building blocks.
|
| M | |
Measure Property Type |
A Measure Property Type is a Condition Property Type that expresses a type of measurement (Time, Mass, Cost, ..) and define the units used for measures (minutes, kg, euros, etc.). Examples: - Time to deliver in minutes. - Delivery cost in kilo Euros. Condition Property Types are described by Measure Unit: kg, Liter, Gallon, Hour, Minute. Condition Property Types are used to constrain Asset Blocks in the context of non-functional requirement analysis and Value Proposition analysis. |
Measurement Instrument |
A Measurement Instrument is a quantified aspect of the assets of the enterprise (Agents, Behaviors, Information Assets) used by organizations to guide its transformation and assurance Initiatives.
|
Meta Family of Class |
A Meta Family of Class is a Class of Classes of Element (its members are themselves Class of Elements), typically used to group or organize collections of Class of Elements that share some structural, relational, or definitional property. In contrast to families of sets, which are sets of sets, a family of classes operates at a higher ontological level-its elements may represent universes, types, or conceptual groupings rather than individual sets. |
Meta-Class |
Meta-Class (also called Class of Classes of Entity Element) is defined as the Class of Entity Element of all Class of Entity Elements each of whose instances is necessarily a Class of Entity Element. In other word, Meta-Class is the powertype of Class of Entity Element: all sub-classes of Class of Entity Elements are instances of Meta-Class. Since Meta-Class is itself a sub-type of Class of Entity Element, Meta-Class is an instance of itself.
|
Meta-Class Partition |
|
Model Building Block |
A Model Building Block is a Building Block used to represent aspects of the reality. It comprises: - Asset Blocks are used to describe the how the enterprise and its systems operate (function) is their eco-systems. - Initiatives are used to manage enterprise and systems functional transformations, as well as assurance objectives and activities. - Governance Instruments are used to ensure that these objectives and activities are understood and fulfilled. |
Model Container |
A Model Container is a Container of Model Building Blocks used to describe both the architecture of the enterprise and Initiatives aimed at designing, developing, running, adapting and maintaining this architecture over time. Model Containers range from Information Dictionary(ies), architecture Library(ies) up to an entire Enterprise .
|
Model Lexical Scope |
A Model Lexical Scope is Block Lexical Scope for Model Building Blocks. It also adds the ability to nest Annotation Blocks. |
Model Package |
|
Model Property Block |
A Model Property Block is a Building Block used to provide classification and qualification ofModel Building Blocks. For instance, Tags are used for classification. Condition Value are used for qualification or quantification. |
| N | |
Nesting Adjacency |
A Nesting Adjacency is an Adjacency Item that references its Element by nesting. Nesting is a fundamental concept in complex systems organization where Entity Elements are contained within other Entity Elements, creating hierarchical or web-like structures. This embedding mechanism intrinsically links the properties, behaviors, and lifecycles of nested Elements to their containing Elements, forming cohesive units at multiple scales. Nesting facilitates the emergence of complex aggregates and properties from simpler Entity Elements, enables efficient design of systems across levels, and supports both autonomy and integration within systems. |
| O | |
Ontological Block |
Ontological Block is the root ontological foundation that defines the capacity to embody meaning through Semantic Relationships - such as Composition (Whole/Part), Classification or Specialization. In contrast, Building Blocks like Aggregate Blocks or Containers act as syntactic constructs, They structure or group Ontological Blocks, but lack inherent semantic properties of their own, serving purely as structural or logistical tools within the framework. |
Operating Asset |
An Operating Asset is a Functional Asset that describes the way Outcome Events are produced and consumed: how (Behaviors) and by whom (Agents). Operating Assets fulfill Capability(ies) (Fulfilled Capability). As any Functional Architecture Asset, Operating Assets are subject to Policy Conformances. In addition, they define Rule Enforcements to indicate how Policy Conformances are met.
|
Operating Connection |
An Operating Connection is an Aggregate Connection that defines a behavioral connection between Operating Assets. |
Operating Eco-System |
An Operating Eco-System is an Operating Context in which an Agent exists or lives for a specific purpose, interacting with partners. For instance, the operating context of an enterprise includes its customers and suppliers. |
Operational Transformation |
An Operational Transformation is an Initiative that creates or transform Operating Assets, based on a Capability Map's functional scope. Its Goal is to deliver new or improved Capabilitys, with measurable qualitative properties, to well identified beneficiary stakholders. |
Ordered Semantic Class |
An Ordered Semantic Class is collection of Ontological Blocks which it classifies according to a chain of powertype relations, with every Ordered Semantic Class specializing the basic type of the same order and instantiating the one of the order above. This make SysFEAT is a higher-order ontology, so Ordered Semantic Classes may have members that are also Ordered Semantic Classes ( Class of Classes). |
Ordereless Class |
An Ordereless Class is a Class of Entity Element which instances can belongs to different order. This includes Class of Entity Elements that are instances of themselves. |
Outcome Event |
An Outcome Event is a Behavioral Event that signals the Output of an Asset Type or state of Asset Type (Outcome) by a producer Behavior, ready to be used as an Input by a consumer Behavior. |
| P | |
Particular Entity Element |
A Particular Entity Element is an Entity Element that is an instance of a Class of Entity Element but that is not itself a Class of Entity Element. |
Physical Data Asset |
A Physical Data Asset represents the physical structure of any kind of data that can be memorized by a Business Software System. A Physical Data Asset is either a Physical Data Entity or a Physical Data Property. Only Physical Data Entitys can have an identity can by be referenced by Physical Relationship. Physical Data Property only handle raw data. |
Physical Data Domain |
A Physical Data Domain is subset of the metadata of an enterprise’s data store. 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). |
Policy |
A Policy is a Directive that is not directly enforceable whose purpose is to govern, guide or constrain the structure and Behavior of Agents in the enterprise.
|
Policy Category |
A Policy Category is a classification of policies. In regulations, it represents sections of the law.
|
Power Class |
A Power Class (often denoted P^* (A)) is a Class of Entity Element of all Sub-Class of Entity Elements of a given Class of Entity Element "A". It generalizes the notion of a power-set (which is the set of all subsets of a set) to the class-theoretic level. |
Property |
A Property is an abstract Class of Individual, which purpose is to qualify Bounded Individuals and their classes (Class of Bounded Individual). Because instances of Property are Individual Propertys, they do not have proper instances: there are no instances of "red", but there are red Bounded Individuals. Example: - 10 degree celcius; - Ability to cook (a capability); - Red; - 12 kg; - Top Secret (TS) confidentiality. - 7/7 availability |
Property Type |
A Property Type is a Class of Class of Individual Object that is used to classify Propertys. Example: - Temperature - Color - Weight - Confidentiality - Availability
|
| R | |
Reference Adjacency |
A Reference Adjacency is an Adjacency Item Item that references its target Element through some identification mechanism kind (for instance, indexing mechanism using IDS and Keys, or physical pointers such as Cylinder.Head.Sector for files on hard-drives). |
Reference Dictionary |
A Reference Dictionary is a kind of Architecture Container that is used as a reference library to hold reference materials used to develop architectures. Example: - Vendor Catalog - Regulatory Framework -
|
Resolution |
A Resolution is time bound Appraisal, agreed upon by Stakeholders to guide what can or cannot be done regarding a specific Functional Asset.
|
Resolution Option |
A Resolution Option is a possible value of a Resolution Type, that will be selected during a resolution process. For instance, when making decisions about invesment on an enterprise asset, the possible options are: eliminate, invest, migrate. tolerate. |
Risk Type |
A Risk Type is a distinct category or classification of risk based on its origin, nature, or potential impact. It helps in organizing and addressing different sources of uncertainty or potential harm that an individual, organization, or system might face. By categorizing risks into different types, entities can develop more targeted mitigation strategies and response plans. Common risk types include Operational Risk Type, Privacy Risk Type, and Compliance Risk Type, among others, |
| S | |
Second Order Class |
Second Order Class is defined as the Meta-Class of all subclasses of First Order Class. Each instance of Second Order Class is a class, each of whose instances is a First Order Class. First Order Class is an instance of Second Order Class since, by definition, all of its instances are First Order Classes. Examples: 1) Car-Brand (with instances such as VolkswagenCar and HondaCar), 2) AnimalSpecies (with instancessuch as GreyWolf and Dodo), Occupation, and USArmyRank. |
Service Interface |
A Service Interface is an interaction Behavior that describes a typical course of Flow Connections, coordinated by Behavioral Events and Outcome Events, and intended to produce Outcomes through the involvement of Agents. |
Software Deployment Environment |
A Software Deployment Environment describes a possible integration context for a Software Deployment Architecture. It contains the subject Business Software System deployment architecture and the partner deployment architectures it must be integrated with, meaning it must communicates with via technical connections (with communication protocols, port numbers...). |
Stakeholder |
A Stakeholder is an individual, team, organization, or classes thereof, having an interest in an Initiative. Stakeholders have concerns with respect to the Initiative considered in relation to its environment. |
State Class |
A State Class is a class of the temporal slices of a Class of Bounded Individual. It is the powertype of Individual State. Examples: . The lifecyle phases of buildings such as a skycraper: construction phase, operation and maintenance phase, decommissioning phase. . The lifecycle phases of a person, such as childhood, adulthood, eldery stage. . The phases of a volcanic eruption: magma accumulation, plinian phase, eruptive phase, effusive phase, declining phase. . The lifecyle phases of a hospital such as construction phase, operation and maintenance phase, renovation and expansion phase, decommissioning phase.
|
| T | |
Team Responsibility |
A Team Responsibility is an assignment of a Functional Asset to a Stakeholder for management or governance purposes. |
Temporal Bounding |
A Temporal Bounding is an Individual whose temporal extent is instantaneous, and whose spatial extent corresponds with the start or end of the Bounded Individuals for which it is the temporal border. Example: . The Eiffel tower completion (31st March 1889) . William Shakespeare birth (1592) . Confucius death (758). . Start of the first Plinian phase of the Mount Vesuvius eruption (18h, Aug. 24 A.D. 79) . Oakland hospital opening in 1994. |
Temporal Bounding Type |
A Temporal Bounding Type is Class of Individual that defines the type of temporal boundaries that delimitate Class of Bounded Individuals. It is a class of Temporal Bounding. Exemples: - Birth, - Death, - Start of the plinian phase of a volcanic eruption. - Hospital opening. |
Time-bound Initiative |
A Time-bound Initiative is an Initiative that has a clearly defined start and end date, with specific objectives to be achieved within that timeframe. These initiatives are characterized by their limited duration, focus on achieving particular outcomes within the set period. Example: project. |
| U | |
Unbounded Aggregate |
An Unbounded Aggregate is an Aggregate Entity Block that does not have boundaries and, thereby, that cannot participate to Connection Relationships. Examples: - Directive. |
| W | |
Waiver |
A Waiver is a temporary Resolution, agreed upon by Stakeholders, that suspends the enforcement of a Policy Decision for a specified duration. |
Whole Life Agent |
Examples: . A type of building such as a skycraper. . A type of person such as a philosopher. . A type of facility such as a Hospital. |
Whole Life Asset |
A Whole Life Asset is an Asset Type that is not the temporal slice type of any other Asset Type. Examples: . A type of building such as a skycraper. . A type of person such as a philosopher. . A type of activity such as a volcanic eruption. . A type of facility such as a Hospital. |
Whole Life Class |
Whole Life Class is the power-type of Whole Life Individual. Examples: . A type of building such as a skycraper. . A type of person such as a philosopher. . A type of activity such as a volcanic eruption. . A type of facility such as a Hospital. . A Process Type (Action Process) such as the registration process used at the Oackland digital hospital during the COVID-19 pandemic. |
Whole Life Individual |
A Whole Life Individual is a Bounded Individual that is not the temporal slice of any other Bounded Individual. A Whole Life Individual includes its past and future. Examples: . The Eiffel tower (31st March 1889 - ...). . William Shakespeare (23 April 1564 - 23 April 1616). . Confucius (685-758). . Mount Vesuvius eruption (Aug. 24-25, A.D. 79). . Oackland digital hospital (1994 - ...). . The execution of the registration process at the Oackland digital hospital, by John Smith, on 17 March 2020.
|