Using diagrams of Scenario of Flows
Creating a Scenario of Application Flows diagram
To create a scenario of application flows from the Applications navigation menu:
1. Right-click the application that interests you and click Create Diagram.
2. In the Create a diagram window, select Structured diagram > Internal Architecture.
The Scenario of Application Flows Diagram appears.
Adding an IT service to the scenario of application flows
An IT service is a software component of an application, that can't be deployed alone and that realizes a sub-set of the functionalities of this application either for end users of this application or inside the application (or another application). This includes batch programs.To add an IT service:
1. In the objects toolbar of the scenario of application flows, click IT Service.
2. Click in the described application frame.
An addition window box prompts you to choose the IT Service implemented (for example "Customer management").
3. Select the application service required and click OK.
The application service appears in the diagram.
You can add a micoservice in the same way.
A microservice is a software component that can be deployed autonomously, but which does not directly provide an end user service. It can interact with other application services, applications or application systems. This is a deployable software component that uses software technologies. For example: an authentication service, a PDF file printing service.Managing application flows in a scenario of application flows
Creating an application flow with content
An application flow represents the use of a flow between two agents (e.g., 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.The application flows exchanged between the IT services, the microservices or the Application ports of a scenario of application flows are associated with a content.
The content designates the content of a message or an event, independent of its structure. This structure is represented by an XML schema linked to the content. A content may be used by several messages, since it is not associated with a sender and a destination. There can be only one content per message or event, but the same content can be used by several messages or events.You must directly specify the content of an application flow directly on flow creation.
To create the application flow:
1. In the objects toolbar of the scenario of application flows, click Application flow and select the Type of application flow that interests you.
• Result/Provision associated to a service result,
• Call/Request associated to a service request,
• Signal associated to an information exchange.
For more details, see Associating a service interface used to an application flow.2. Click the first object representing the sender of the flow and, holding the mouse button pressed, draw a link to the object receiving the flow.
The Application Flow Creation dialog box opens.
3. In the Content drop-down list, select the content you wish to associate with the flow.
A tree of the Flow Measures used by other application flows with the same content is displayed.
4. Select the flow measures that interests you and click Add.
The application flow is displayed with its content in the diagram.
Application Flow qualification
Application flow categories provide a way to define parameters of the application flows that are used described in the scenario of flows.
To qualify an application flow from flow measures:
1. Open the Qualification property page of the application flow that interests you.
2. In the Flow Qualification section, click the Connect button.
A selection dialog box opens displaying the tree of existing Flow Categories.
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 used to an application flow
A service interface use is associated to a service interface. It enables representation of complex exchanges.Associating a service interface to an application flow enables to establish a correspondence between a Scenario of Flows diagram and a Structure diagram of an application or an application system.
It identifies the service interface/operation called (if the application flow type is Call/Request) or the supplying service interface/operation (if the application flow type is Result/Provision).
To associate a service interface to an application 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.
Creating an application flow channel
An application flow channel is used to graphically group a number of application flows into a single flow.To create an application flow channel, you must first create the channel and then link the application flows that it groups.
To create an application flow channel:
1. In the objects toolbar of the scenario of application flows, click Application Flow Channel.
2. Click the first object in communication and, holding the mouse button pressed, draw a link to the other object.
The application flow channel appears in the diagram.
To connect the application flows to the application flow channel:
1. Open the Characteristicsproperties page of the application flow channel.
2. In the Grouped Flow section, click Connect.
A selection dialog box opens and presents the list of the application flows of the scenario of application system flows.
3. Select the flows that you want to group and click OK.
The content of the selected flows is displayed in the Grouped Flow list.
4. Click the Refresh Channels button.
The application flows grouped in the channel disappears and the corresponding content is displayed around the channel.
If you remove the channel, only the application flows created from the Grouped Flows are removed. The connected application flows are displayed if you click the Refresh Channels button.Creating a System Triggering Event
The creation process for a Creating a System Triggering Event and a Creating a System Triggered Event is the same.
To create a System Triggering Event:
1. In the diagram insert toolbar, click the System Triggering Event button.
2. Position the object at the edge of the frame of the described object.
A creation dialog box opens.
3. Click the arrow at the right of the Referenced Content field and select the content that interests you.
4. Click Add.
The System Triggering Event appears in the diagram.
Any application flow whose origin is the System Triggering Event is connected to the same content.
To create an application flow from a System Triggering Event:
1. In the diagram insert toolbar, click Event Participation.
2. Click the event and, holding the mouse button pressed, draw a link to the object receiving the flow.
The application flow is displayed with its content associated to the event.
Reinitializing components in a scenario of flows
If you insert in a scenario of flows diagram a component that is already described by a scenario of flows, you can note that a new section is created in the Characteristics property page of the component you have added. This section allows you to specify which scenario of flows of the component corresponds to the context of the current application system scenario of flow.
In the component scenario of flows diagram, the Reinitialize components button allows you to insert components coming from the upper level scenario of flow.
Adding an application data store to the scenario of application flows
An application data store materializes the usage of data in the context of a software component (for instance an application). An application data store provides a mechanism to retrieve or update information stored outside of the current software component.A data store can be local or external to the application.
To add, for example, a local application data store to an scenario of application flows
1. In the scenario objects toolbar, click Local Application Data Store.
2. Click in the described application frame.
An addition window prompts you to choose the Object Type that represents the physical structure that will concretely support the application data store.
For more information on managing data stores, see Managing Data.3. Depending on the Object type, select then the object that interests you.
4. Click OK.
The local application data store appears in the diagram with the name of the physical data domain selected.
Creating an application data channel
The applications, the application systems and the microservices can have read or write access to a local or external application data store.
To create an application data channel that represents a reading access:
1. In the diagram objects toolbar, click Application Data Channel.
2. Draw a link between the application data store and the object that reads the data.
An application data channel appears in the Diagram.
To create a link with write access, you must draw a link between the object that reads and the application data store.