Defining a data flow and its usages
A flow represents the circulation of information between two agents of an information System (for example, two applications, an application and an Org-Unit).
The flow is defined by:
• a sender
• a receiver
• exchanged content, symbolizing the data being transported
The flow is defined in absolute terms.
In Hopex, flows can be defined between some object types only:
• Application system / Application system
• Application system / Org-Unit or Application system / Position
• Application system / Application
• IT service / Microservice
• IT service / IT service
• Application / Microservice
• Application / Org-Unit or Application / Position
• Application / Application
• Application System / Microservice
Application flow
An application flow represents the use of the flow between two agents (for example, applications) in a usage context (represented by a scenario of flows).
An application flow is based on a flow, which represents the reference flow in context.
Scenario of flows
A scenario of flows represents a context in which an agent is used: an application or an IT system, for example. An application flow describes the exchange of data in a unique usage context. However, the same exchange of data can be described in another usage context by another application flow.
An application flow is owned by a single flow scenario and refers to a single flow.
A flow enables the representation of data exchanges common to several contexts, i.e., several flow scenarios. A flow can be connected to several application flows.
Flow qualification
Measure Schemes Categorization enable the definition of parameters that characterize the flows.
To qualify a flow from a Flow measure:
1. Open the Qualification page of the flow that interests you.
2. In the Flow Qualification section, click the Connect button.
A selection dialog box opens displaying the tree of existing Measure Schemes Categorizations.
3. Select the flow measures that interests you and click Add.
To access the list of Application Flow Categories: using the
Administration navigation menu, select
Categorization and unfold the
Measure schemes Categorization. The list of Application Flow Categories appears.
Associating a service interface use to a flow
A Service Interface is a template of a contract between entities (organizational, IT …). The contract is described by available operations which can be triggered trough messages exchanged by roles (vendor, buyer..).
A service interface use is associated to a service interface. It enables representation of complex exchanges.
A service interface can be connected to a flow. This enables the identification of the API used in a flow context, for example.
There are two ways to use a service interface within a flow:
• The flow triggers the service interface (API). It is then of Call/Request type.
• The flow is the result of the service interface (API). It is then of Result/Provision type.
To associate a service interface to a flow:
1. Open the Service Interface Used page of the application flow that interests you.
2. Click New.
A dialog box opens proposing a list of service interfaces used whose content is a request point or a result.