Application data channels represent the interactions between application data stores.

An application data store materializes the usage of data in the context of a software component (for instance a system). It provides a mechanism to retrieve or update information stored inside or outside the current software component. It can be local or external.

A system flow represents a piece of information flowing between systems or inside a system.

A system flow can carry a content.

An application flow channel allows grouping graphically several system flows into a single flow.

An application input gate represents the entry point which allows to receive a piece of information inside a system.

An application input gate is associated to a content.

An application output gate represents the exit point which allows to send a piece of information outside a system.

An application output gate is associated to content.

An application system is an assembly of other application systems, systems and end users, in order to realize one or more functionalities (e.g.Payroll System).

An application system environment presents an application system use context. It describes the interactions, between the application system and its external partners, which enables it to fulfill its mission and ensure the expected functionalities.

An application system flow environment presents globally the flows exchanged between this application system and other application systems, systems, micro-services or organizations.

A technical architecture of an application system describes one possible configuration of the deployment of the system of this application system. It describes which technical architecture is chosen for each of the systems involved and the communication protocol they use to communicate with each other.

A technical Architecture describes one possible configuration of the deployment of a system. It describes how the different system technical areas are connected to each other and the technologies and communication protocols they use. A system can have multiple possible technical architectures (Ex: stand-alone installation, horizontal or vertical deployment, etc.).

An application technical area represents an organizational element of a system according to technical criteria. For example, this can be the user interface or a process. Each application technical area is associated with one or more technologies. The deployment of several application technical areas is necessary for the system to be operational.

An artifact is any element in the physical domain that is not a system or an organizational element (where organizational includes people).

An Artifact can represent a physical system, sub-system, platform, component or simply a physical item that has specific attributes.

A Business Capability is a set of features that can be made available by an enterprise.

A Business Capability Composition is the involvement of a business capability in the context of a business capability map (one and only one) linked to an enterprise.

A Business Capability Dependency is a relationship which asserts that a dependent Capability depends upon a needed capability in the context of a capability dependency owner, with respect to its needed effect (business outcome).

A Business Capability Map is an assembly of Business Capabilities and their Dependencies that, together, provide a capability scope for an Enterprise Stage.

A business information area is a sub-set of elements of a subject area that reduces the scope of a field.

A business information map enables to define the scope of Business Information Areas for a studied concern.

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

A business service catalog provides a centralized information source for the business services offered by the service provider organization. It contains a customer-oriented view of the business services used, how they are supposed to be used, the processes that they support as well as the expected service quality level. The business service catalog presents a list of functionalities mentioned as well as implementation recommendations.

A Business Skill is a Capability of an Organization (human resource) that has been acquired by training.

A business transformation stage is a type of enterprise transformation stage aiming at the alignment of the enterprise operating model to its strategy and corresponding exhibited business capabilities.

A component is an intermediary object which represents the usage of an object in a specific context.

A Composite KPI Dimension defines the grouping of elementary KPIs that should be examined together in order to appreciate the actual performance of a KPIed item. E.g. a delivery should be achieved in a defined target timeframe AND at a target cost.

 

A concept is a statement expressing the essential nature of a being, an object, a word through its essential properties and characteristics or its specific qualities.

A concept type enables classification of concepts. Relationships between concept types are represented by concept type components.

A concept view enables representation of the semantic scope covered by a business object. A concept view is based on the selection of several concepts specific to the view.

A condition indicates the state in which an object should be in order to perform an action.

Content designates the content of a message or a message flow, independently of its structure. Content may be used by several messages or message flows, since it is not associated with an sender and a destination.

A data area is subset of the enterprise data that is meant to be manipulated together in the context of business operations.

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

Data Areas define functional data boundaries used both for Data Allocation to systems (see Data Stores) and Data Governance for data stewardship.

 

A data object is used to explain how documents, data, and other objects are used and updated during the process. A data object can represent an electronic document, or any other type of object, electronic or physical.

A data store provides a mechanism to update or consult data that will persist beyond the scope of the current process. It enables storage of input message flows, and their retransmission via one or several output message flows.

A data view enables representation of the scope covered by a package element. A data view is based on the selection of several classes connected in the specific context of the view.

A database stores data physically or logically.

A desired application effect is the effect (or applicative outcome) desired by a functionality.

It can be required by another functionality through a functionality dependency.

The effect (or outcome) is the content delivered through an Exchange Contract or an Exchange.

Ends are about what an enterprise wants to be. Ends can be about changing what the enterprise is (e.g., developing new lines of business, moving into new markets) or about maintaining its current position relative its market and competition. The definition of an end does not say how it will be achieved. Ends are categorized as Vision, Goals and Objectives.

An enterprise event is something that happens at a given place and time and that marks the end of one enterprise stage and possibly the beginning of another.

An Enterprise is a purposeful undertaking, conducted by one or more organizations, aiming at delivering goods and services, in accordance with the enterprise mission in its changing environment. During its development over time, an enterprise has to adapt to its environment and sets up transformation goals and objectives along with course of action to achieve these objectives. The design and realization of the resulting transformation stages may transcend organizational boundaries and consequently require an integrated team working under the direction of a governing body to involve stakeholders in transformation initiatives.

En enterprise stage is a past, current or future stage of an enterprise.

An enterprise undertaking is a supertype of Enterprise and Enterprise Stage, defining that subtypes may have components (sub-Enterprise Stages), an ability map and logical environment, as well as physical implementations.

An exchange contract is a model of a contract between organizational entities. This contract is described by exchanges between an initiator role and one or several contributor roles.

An exchange use represents the usage of an exchange in another exchange contract.

An exchange contract use represents the usage of an exchange contract in another exchange contract.

An exhibited business capability is a business Capability that is exhibited by an Enterprise Stage with quantified measure (KPI) and potential geopolitical scope (Site) for a defined market segment (Business Partner).

An external application data store materializes data usage in the context of a software component (for instance an application). It provides a mechanism to retrieve or update information stored outside the current software component.

A facility is a model of location of interest for the enterprise. Examples: Data Center, Factory, Outlet.

Fulfillment refers to the provision of services or functionalities. Example: a system fulfills project management functionalities.

A functionality is a service required by an organization in order to perform its work. This functionality is generally necessary within an activity in order to execute a specific operation. If it is a software functionality, it can be provided by a system.

A functionality component represents a sub-functionality in a functionality map or a functionality.

A functionality dependency is a relationship which asserts that a functionality is dependent on another (required functionality), in the context of a Functionality Building Block (owner), with respect to its desired effect.

A functionality map is an assembly of functionalities and their dependencies that, together, define the scope of a hardware or software architecture.

A gate is a connection point between a message outside an interaction fragment with a message inside the interaction fragment.

Gateways are modeling elements that are used to control how sequence flows interact as they converge and diverge within a system function.

A Goal tends to be longer term, and defined qualitatively rather than quantitatively. It should be sufficiently narrow-focused that Objectives can be defined for it.

Hardware consists of non-IT equipment.

Non-IT Hardware can embed Computers. Together with their embedded computers, they provide information and IS services. Examples: Connected Truck with Delivery Calendar App, Connected Drone with Online Payment App.

Hardware device can also provide hardware functionalities. Example:- Connected fridge providing ordering functionalities and of course a freezing hardware functionality, connected drones fly and provide Online Payment.

A hardware functionality is the ability to deliver a physical outcome which is required by an organizational resource in order to perform its work. This hardware functionality is generally necessary within an operational activity in order to execute a specific operation.

The Hardware Service Catalog provides a central source of information on the Hardware services delivered by the service provider organization. It contains a customer-facing view of the Hardware services in use, how they are intended to be used, the process they enable, and the levels and quality of service the customer can expect from each service. The Hardware Service Catalog provides the list of reference Hardware functionalities and their recommended implementation.

An Hardware Service Catalog Item defines which hardware functionality is part of the catalog and which hardware artifacts are fulfilling the hardware functionality.

The Information Service Catalog provides a central source of information on the Information services delivered by the service provider organization. It provides the list of reference functionalities and their recommended implementation.

An Information Service Catalog Item defines which functionality is part of the catalog and which application artifacts are fulfilling the functionality.

An interacting element endpoint is a connection point between an exchange channel and an interacting component.

An Interaction represents a contract between entities in a specific context inside or outside a company. These entities can be organizations, activities, or processes. The content of this contract is described in a protocol.

An interaction scenario is used to describe an operational, system or a service use case. It presents the sequence of message instances exchanged between organizations, systems or service instances during the execution of the scenario.

An IoT Device is both a hardware device and a computing device which provides combined hardware and information services to the users using it directly. As a hardware device, it embeds sensors - e.g. accelerometer - which provide data to the embedded computing device. As a computing device, it can host data stores or run systems.

An IT Device is a computing device which provides end-users with a service. This computing device can host data stores or run systems. Examples: workstation, laptop computer, smart phone.

An IT Infrastructure consists of several connected IT Devices (IT Technical Devices or Computing Devices) and IT Networks.

An IT Network is an assembly of IT Technical Devices (e.g. routers, switches, firewalls) enabling remote communications between IT Devices (e.g. IT Servers). An IT Network may breakdown into sub-networks.

An IT Peripheral Device can host and run Software Technology. Together with its hosted Software Technologies, it provides Technical Services. Examples:- Wifi Access Point, Firewall, Router, Switch, Printer, Hard Drive, etc.

An IT Server is a computing device which provides a service to the users connected to it via an IT network. This computing device can host data stores or run systems (applications).

An IT service is a software component of a system. It cannot be deployed alone.

An IT Service realizes a sub-set of the functionalities of this system either for end users of this system or inside the system (or another system).

It includes batch programs.

An IT Transformation Stage is a type of Enterprise Transformation Stage aiming at the alignment of its IT System to expected functionalities required for the business to operate effectively at the right cost.

A KPI (key indicator) defines how much of something that can be quantified, either as a singular value or as range of values, according to a KPI Dimension. KPI are valued KPIs. Example: Time to deliver [10-20] minutes.

A composite KPI defines the grouping of elementary KPIs that should be examined together in order to appreciate the performance of an item with KPI. E.g.: a delivery must take place in less than 20 minutes and cost less than 5 euros.

KPI dimensions express the nature of KPIs (Time, Mass, Cost, ..) and define the units used for KPI (minutes, kg, euros, etc.). Example: Time to deliver in minutes, Delivery cost in kilo Euros.

KPI dimensions are KPI definitions. They can be elementary or composite. Elementary dimensions are described by KPI units: kg, Liter, Gallon, Hour, Minute.

A composite KPI dimension consolidates a set of KPI dimensions that must be considered jointly to assess the performance of a tracked element. E.g: a delivery must take place within a target timeframe AND at target cost.

Libraries are collections of objects used to split HOPEX repository content into several independent parts. They allows virtual partition of the repository. In particular, objects owned by different libraries can have the same name.

A lifeline represents the participation of a software or organizational component in a scenario of another software component (application, IT Service, …).It represents an individual participant in the Interaction.

A logical data area is used to define a logical data structure made up of classes and data views.

A Means is some capability, regime, technique, restriction, agency, instrument, device or method that may be called upon, activated, or enforced to achieve Ends. It does not include either the tasks (business processes and workflow) necessary to exploit it, nor responsibility for such tasks.

A measure is an indicator of the achievement of an objective, the impact of a risk factor, the likelihood or the severity of a risk, the efficiency of a control, etc..

A micro-service is a software component that can be deployed autonomously, but it does not directly provide a service to the end user.

It can interact with other IT Services, Systems or Application systems. It uses software technologies.

Examples: Authentication service, PDF Printing service

A Mission indicates the ongoing operational activity of the enterprise. The Mission describes what the business is or will be doing on a day-to-day basis.

A Mission makes a Vision operative; that is, it indicates the ongoing activity that makes the Vision a reality. A Mission is planned by means of Strategies.

Needlines group together internal operational flows.

An object life is the set of time periods representing the current schedule of states for an object.

An objective is a goal that a company/organization wants to achieve, or the target set for a business process or an operation. An objective allows you to highlight the features in a business process or operation that require improvement.

An operation is an elementary step in an operational activity executed by an organization. It cannot be broken down.

An operational activity is a set of operations performed by organizations within a company or organization, to produce a result. It is depicted as a sequence of operations, controlled by events and conditions.

 

Operational Rules are explicit constraints on operational activities and/or provide support for conducting them. Operational Rules are derived from Business Policies.

An operational scenario presents flows exchanged between organizations. A scenario can represent a specific use case or, globally, the set of all flow exchanges at the operational level.

An organization represents a person or a group of persons that intervenes in the enterprise business processes or information system. An organization can be internal or external to the enterprise.

- An internal organization is an organizational element of the enterprise structure such as a department, a service, or a workstation. An internal organization is defined based on how detailed you require your view of the enterprise to be (cf org-unit-type). Example: financial management, sales management, marketing department, account manager.

- An external organization is an organization that exchanges flows with the enterprise. Example: Customer, Supplier, Government Office.

An organization environment defines the organizational context, roles and relationships among organizations.

An organizational element is an organizational resource configured to achieve different capabilities within a resource architecture.

A package partitions the domain studied and the associated work. It enables grouping of various elements, in particular use cases and classes. A package can also contain other packages. Packages are interconnected through contractual reports defining their interface.

A logical data area is used to define a logical data structure made up of classes and data views..

A position type is a type of status assigned to an individual or group of individuals which defines a job in an organization or hierarchy. It helps define human roles.

A Project is a temporary endeavor undertaken by a specific team, to create a unique product, service or result It serves a purpose which can be expressed in terms of capability that is acquired (new), extended (improvement) or decommissioned (rationalization). It generates Project deliverables. It can be attached to one or several Project Categories.

A Project may fit into one or several categories, depending on its purpose and breadth or depth of coverage regarding the architectural landscape (e.g. Strategic Business Initiatives, Maintenance-driven activities, Technology initiatives, IT management initiatives, etc.).

A Project Deliverable defines the outcome of a project and its impact or contribution to the solutions architectural landscape.

It is defined as a Solution Building Block (e.g. an Organization, an Application, a Resource Architecture, or IT Infrastructure) delivered by the project to the Architectural Landscape. As part of a Project Deliverable, a block can be:

- New: the project is delivering a new block in the to be architecture landscape;

- Updated: the project modifies a block from the ‘as is' landscape, for instance to extend its lifecycle, and delivers it to the ‘to be' landscape;

- Decommissioned: the project removes a block from the as-is landscape.

A project is defined upon a given domain (e.g. Business, Information Technology). A domain gathers all the projects managed from the same perspective in terms of portfolio management decisions. Project Portfolios are therefore also attached to Project Domains; by default, one portfolio of each portfolio type is created when creating a new domain.

A Project Portfolio gathers all the projects of a given Project Domain.

A project risk is a potential issue faced by the project team when carrying out the project or concerning the project outcomes. It may face risks of various kinds (e.g. delays, budgeted costs increase, inadequate deliverables quality); the kinds of risk can be defined through project risk types. The Project Risks are not to be confused with operational risks, and concern only the project endeavor itself, not the operation of its deliverables after the end of project.

Realization refers to compliance to an operating model.

A resource architecture is a combination of used material and organizations configured to provide a capability.

A Resource architecture environment is an environment context for a Resource Architecture or Facility and its interacting partners.

A Resource Configuration is a set of physical and human resources configured to provide a Business Capability.

A rule is a constraint represented by a control or a business rule that must be applied during processing.

A scenario of application system flows presents the flow exchanged between the other application systems, systems or the micro-services used by this application system. A scenario can represent a specific use case of this application system or, globally, the set of all flows exchanged inside this application system.

A scenario of system flows presents the flow exchanged between the IT services or the micro-services used by this system.

A sequence flow is used to show the order in which the steps of a function will be performed. It has only one source and one target.

A Service Catalog is a list of key service offerings for which a set of recommended solutions are proposed.

A service catalog item defines which functionality is part of the catalog and which artifacts are fulfilling the functionality.

A service point is a point from which a system receives a request from another system and provides the requested service.

A site is the geographical location of an organization. Examples: Boston subsidiary, Seattle plant, and more generally the headquarters, subsidiaries, plants, warehouses, etc.

An enterprise stage is a past, current or future stage of an enterprise plan.

A standard is a definition or format that has been approved by a recognized standards organization or is accepted as a de facto standard by the industry.

A standard component represents the use of a standard within another one.

A state concept is a situation in a concept life cycle during which it satisfies certain conditions, executes a certain activity or waits for a concept event. A state concept represents a time interval of which limits are two concept events. A state concept is a phase through which the concept passes during its life cycle.

A state machine is a set of states and transitions governing the state changes that can match any time-dependent object.

A Strategy is one component of the plan for the Mission. A Strategy represents the essential Course of Action to achieve Ends (Goals in particular). A Strategy usually channels efforts towards those Goals.

A Strategy is accepted by the enterprise as the right approach to achieve its Goals, given the environmental constraints and risks.

A subject area is a branch of knowledge, a discipline or a field of study. It is used to describe all the elements defining your information architecture.

A system is a software component that can be deployed and provides users with a set of functionalities.

A system environment allows presenting the other application systems, applications or micro-services with which this system can interact.

A system flow represents an information flow between systems or inside a system. It can carry content.

 

 

A system flow environment presents globally the flows exchanged between this system and other application systems, systems or micro-services.

A system flow environment subject represents the system whose environment is illustrated by the system flow environment.

A system function is the executable representation of an operational activity.

The elements that formalizes a system function are as follows: the events of the workflow, the tasks to be carried out during the processing, the algorithmic elements used to specify the way in which the tasks follow on each other, the information flows exchanged with the participants.

An system of system is the configuration of a resource architecture within another architecture.

An system of system is an assembly of other systems of systems, systems and end users, in order to realize one or more functionalities.

A system technical area is a split of a system according to technical criteria. For example, it may be GUI, process and data. Each technical area is associated with one or several technologies. Several system technical areas need to be deployed to get the system operational.

A system used during the execution of a step of an operational activity represents what is necessary to realize this step. It can be a service or any other non IT resource, or more generally a functionality.

A Tactic is a Course of Action that implements part of a Strategy. Tactics generally channel efforts towards Objectives.

A tag is a classifying description which permits characterization of objects.

A task is an elementary step that is included within a system function. A task is used when the work in the system function is not broken down to a finer level. Generally, an end-user and/or an IT service are used to perform the task when it is executed.

A technical Architecture describes one possible configuration of the deployment of a system. It describes how the different application technical areas are connected to each other and the technologies and communication protocols they use.

A system can have multiple possible technical architectures (Ex: stand-alone installation, horizontal or vertical deployment, etc.).

A data technical area represents an organizational element of a system used to access the data necessary for the operation of this system. Each application technical area is associated with one or more technologies (E.g.: Oracle 12, SQL Server 2012, etc.). A data technical area can allow access to one or more data stores.

An application technical area is a split of a system according to technical criteria. For example, it may be GUI, process and data. Each technical area is associated to one or several technologies. Several system technical areas need to be deployed to get the system operational.

A technical communication line represents a technical connection between application technical architectures or areas through input to output communication ports. The output technical port of a technical area or architecture asks the input technical port of the other technical architecture or area to open the communication line.

A technical data area is a split of a system allowing access to the data required for the operation of this system. Each technical data area is associated to one or several technologies (Ex: Oracle 12, SQL Server 2012, Windows file system, etc.). A technical data area can allow access to one of several data stores.

A technical functionality is the ability to deliver a technical information which is required by a technical artifact in order to function properly. This technical functionality is generally required within a technical process handled by the technical artifact.

An input technical port is a point used to open communications with a technical architecture or an application technical area in compliance with a particular communication protocol (SMTP, HTTP, etc.).

The Technical Service Catalog provides a central source of information on the technical services delivered by the service provider organization. It contains a customer-facing view of the Technical services in use, how they are intended to be used, the process they enable, and the levels and quality of service the customer can expect from each service. The Technical Service Catalog provides the list of reference IT functionalities and their recommended implementation.

A Technical Service Catalog Item defines which technical functionality is part of the catalog and which technical artifacts are fulfilling the technical functionality.

A term is a word or group of words that is used for a specific meaning in a specific context.

A used material is a resource that can host systems. It is configured to achieve different capabilities.

A Vision is the ultimate, possibly unattainable, state the enterprise would like to achieve. A Vision is often compound, rather than focused toward one particular aspect of the business problem. A Vision is supported or made operative by Missions. It is amplified by Goals.