Fault Tolerance Requirements
This system module was built to perform automated extraction of System-of-Systems (SoS) fault tolerance requirements, considering the Detailed Mission Model of a PoP as a 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 navigate to the Show PoP section.
.
-
Step 2: In the PoP listing tab, locate the desired PoP and click on the corresponding action button for the mission from which you want to extract fault tolerance requirements.
-
Step 3: Select the option "Extract Fault Tolerance Requirements".
-
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 fault tolerance requirements.
- Step 6: After the extraction is complete, you will have the option to download the result in CSV file format.
As a result, a fault tolerance requirement will be instantiated for each message flow associated with a send-and-receive task with a failure attached to its edge identified in the Detailed Mission Model of the PoP. The requirement can have detailed and compact formats, as shown below:
Detailed Format
| Content | Field |
|---|---|
| ID | [Unique requirement identifier] |
| Class | Fault tolerance |
| Subject | [Subject of the requirement, in this case it is the SoS itself] |
| Constituent of origin | Constituent that sends messages |
| Target constituent | Constituent that receives messages |
| Time when the failure occurred during sending and receiving a message | Obtained by observing the task of sending and receiving a message associated with an error event |
| What errors occur when sending and receiving messages | Obtained by observing each label associated with each subprocess gateway output flow that represents exception handling during message sending and receiving |
| How to resolve errors when sending and receiving messages | Obtained from the observation of temporal intermediate events, intermediate message reception events (not attached to tasks) and tasks that must be executed after the occurrence of each failure during sending and receiving a message |
| Action | Handling failure to send and receive messages during interoperability between two constituents |
| Traceability | Obtained by observing the name of the source constituent among the destination constituent when sending and receiving a message during the time of failure |
In the CSV file, each line corresponds to a fault tolerance requirement containing relevant information such as ID, class, subject, originating constituent, destination constituent, time of failure occurrence during message transmission and reception, types of failures occurring during message transmission and reception, how to resolve failures during message transmission and reception, action, and traceability.
Compact Format
| Field | Content |
|---|---|
| ID | [Unique requirement identifier] |
| Class | Fault tolerance |
| Subject | [Subject of the requirement, in this case it is the SoS itself] |
| Action | Handling failures in sending and receiving messages during interoperability between two constituents |
| Traceability | Obtained by observing the name of the source constituent among the destination constituent when sending and receiving a message during the time of failure |
In the CSV file, each line corresponds to a fault tolerance requirement containing relevant information such as ID, class, subject, action, and traceability.