Complexity

Research Article

Interface Data Modeling to Detect and Diagnose Intersystem Faults for Designing and Integrating System of Systems

Table 8

Overall test results: fault-diagnosis results.


Test number	Fault case	Interface type	Message type	Interface data	Fault diagnosis	Fault category

Test₁	Fault₁	Sensor_F	Msg_F-1	02-30-31-30-30-39-33-37-…-35-31-20-20-20-…-20-20-20-30-30-33-35-…-03	The modeling should be revised that all the fields regarding a specific section are full of “0x20” if no targets are detected in the section.	Logical fault
	Fault₂	Control_G	Msg_G-2	0D-0A-48-32-35-31-31-…-20-2B-30-38-35-33-…-53-2B-…	The modeling should be revised that the interpreted value of the sign field can be “+” although the precondition field is unavailable.	Logical fault
	Fault₃	Control_G	Msg_G-2	0D-0A-48-32-35-31-31-…-20-2B-30-38-35-33-…-53-2B-…	The modeling should be revised that the speed field has meaningful information although the precondition field is unavailable.	Logical fault
	Fault₄	Control_G	Msg_G-2	0D-0A-48-32-35-31-31-…-20-2B-30-38-35-33-…-53-2B-4F-53-2B-…	The modeling should be revised that the interpreted value of the headline sonar field is “O” instead of “0” if sonar systems are available.	Logical fault
	Fault₅	Control_G	Msg_G-2	0D-0A-48-32-35-31-31-…-00-00-00-00-20-00-00-00-…	The modeling should be revised that every byte of the range field can be 0x00 as well as [0x30, 0x39].	Logical fault

Test₂	Fault₆	Sensor_E	Msg_E-1	2A-30-30-30-31-32-30-31-36-0D-0A	The delimiters should be changed from header and length to header and footer for variable lengths.	Structural fault
	Fault₇	Sensor_E	Msg_E-1	2A-30-30-30-31-2D-36-34-34-35-33-39-0D-0A	The pressure field should be revised to have 4 to 7 bytes including sign characters optionally.	Logical fault
	Fault₈	Control_G	Msg_G-2	0D-0A-48-32-35-31-31-…-00-00-00-…-30-30-35-40	The modeling should be revised that the target field is full of “0x00” if the relevant target is not identified.	Logical fault

Test₄	Fault₉	Control_G	Msg_G-1	05-0A-41-43-4B-20-40	The modeling should be revised that multiple headers, that is, “0D-0A” and “05-0A” are allowed.	Structural fault

Test₅	Fault₁₀	Sensor_C	Msg_C-12	3A-32-30-30-53-43-53-31-31-30-…30-30-53-0D-0A	The modeling should be revised that the interpreted value of the status field contains “STS.”	Logical fault

Test₆	Fault₁₁	Sensor_C	Msg_C-12	3A-32-30-30-49-41-43-31-31-30-…30-30-53-0D-0A	The modeling should be revised that the interpreted value of the status field contains “IAC.”	Logical fault
Test₆	Fault₁₂	Sensor_C	Msg_C-12	3A-32-30-30-54-52-4B-31-31-30-…30-30-53-0D-0A	The modeling should be revised that the interpreted value of the status field contains “TRK.”	Logical fault

Test₉	Fault₁₃	Sensor_B	Msg_B-1	03-01-01-00-00-00-00-…-1B-C3-79-58-84-8A-00-00-00-3F	Sensor_B needs to be refined to send “0x00” or “0x54” for the test field although the corresponding system is initialized.	Logical fault
Test₉	Fault₁₄	Sensor_H	Msg_H-1	0D-0A-20-20-20-…-38-43-35-03	Sensor_H should be refined to send the message with an accurate header.	Structural fault

Data in italics in interface data mean parts for fault diagnosis. Square brackets in fault diagnosis are used for regression expression. These results are extended from our previous study [12].