Interoperability Requirements
This system module was built to perform the automated extraction of System of Systems (SoS) interoperability requirements, considering the Mission Detailed Model of a PoP as the source of information. Therefore, after correctly modeling or linking this model to a desired PoP mission, you can perform the automated extraction of these requirements. To do this, follow the instructions below:
- Step 1: Access the PoP Management module in the PoP Modeler tool, and go to the Show PoP session.
- Step 2: In the PoP listing tab, locate the desired PoP and click on the action button corresponding to the mission from which you want to extract the interoperability requirements.
- Step 3: Select the "Extract Interoperability Requirements" option.
- Step 4: On the extraction screen, choose the desired language (Portuguese or English) and the extraction type (compact or detailed).
- Step 5: Click the button to generate the extraction of interoperability requirements.
- Step 6: After the extraction is complete, you will have the option to download the result in CSV file format.
As a result, an interoperability requirement will be instantiated for each message flow identified in the Detailed Mission Model. The requirement can have both detailed and compact formats, as shown below:
Detailed Format
| Field | Description |
|---|---|
| ID | Unique Indentifier |
| Class | Interoperability |
| Subject | Subject of the requirement; in this case, it is the SoS itself. |
| Action | Interoperability between two constituents to carry out communication |
| Interoperability-related message information | Existence of description in the message flow attribute |
| Interoperability condition | Existence of agreements between the organizations of the constituent systems (CONTRACT) |
| Number of messages sent | Obtained by observing multiple instances of the element that sends the message |
| Time restrictions for sending the message | Obtained by observing time edge events that interrupt the flow |
| Origin of the data when sending the message | Obtained from observing the association of a repository with the sending element |
| Error while sending the message | Obtained by observing error edge events |
| Send Message Flow in Private Mode | Condition only exists when the sending constituent has a pool with private viewing mode |
| Number of messages received by the same constituent | Obtained by observing multiple instances of the element that receives the message |
| Time restrictions for receive the message | Obtained by observing time edge events that interrupt the flow |
| Data destination during message reception | Obtained from observing the association of a repository with the receiving element |
| Error while message receive | Obtained by observing error edge events (DESTINATION) |
| Receive Message Flow in Private Mode | Condition only exists when the receiving constituent has a pool with private viewing mode |
| Traceability | Description for quick identification of BPMN elements that were observed for requirement elicitation and specification |
Compact Format
| Field | Description |
|---|---|
| ID | Unique Indentifier |
| Class | Interoperability |
| Subject | Subject of the requirement; in this case, it is the SoS itself. |
| Action | Interoperability between two constituents to carry out communication |
| Interoperability-related message information | Existence of description in the message flow attribute |
| Interoperability condition | Existence of agreements between the organizations of the constituent systems (CONTRACT) |
| Detailed textual description | All interoperability information observed for sending and receiving |
| Traceability | Description for quick identification of BPMN elements that were observed for requirement elicitation and specification |
In the CSV file, each row corresponds to an interoperability requirement, containing relevant information such as the ID, action, source and destination constituents, source and destination elements, types, repositories, and message details.