List of results from formal validation.


 



4 results found
Code Name Overall result of the formal validation - Result Overall result of the formal validation - Validation protocol contents Overall result of the formal validation - impact on technical interaction or operation Result of the individual formal validation - Result Result of the individual formal validation - impact on technical interaction or operation
OK OK The formal validation did NOT detect any data constellations that would indicate (a) data incompleteness or incorrectness, e.g. inconsistency, and/or (b) described activities' or objects' lack of compliance with requirements, e.g. legal regulations or official constraints. The validation protocol is empty, i.e. it contains neither INFO, WARNING nor ERROR entries. Successful processing of the technical interaction/operation: The result of formal validation by itself does NOT impair the software's processing of the technical interaction/operation.
INFO Info The formal validation has detected data constellations that indicate (a) data is incomplete or incorrect, e.g. inconsistent, and/or (b) described activities or objects do not comply with the requirements, e.g. legal regulations or official constraints; or (c) the described activity or object has unusual properties which occur rarely in practice. The validation protocol contains at least one INFO entry, but neither WARNING nor ERROR entries. Successful processing of the technical interaction/operation: The result of formal validation by itself does NOT impair the software's processing of the technical interaction/operation. The software has detected a data constellation that indicates (a) data is incomplete or incorrect, e.g. inconsistent, and/or (b) described activities or objects do not comply with the requirements, e.g. legal regulations or official constraints; or (c) the described activity or object has unusual properties which occur rarely in practice. Successful processing of the technical interaction/operation: The data constellation by itself does NOT impair the software's processing of the technical interaction/operation.
WARNING Warning The formal validation has detected data constellations that indicate (a) data is incomplete or incorrect, e.g. inconsistent, and/or (b) described activities or objects do not comply with the requirements, e.g. legal regulations or official constraints. The validation protocol contains at least one WARNING entry, but no ERROR entries. The validation protocol may also contain INFO entries. Successful processing of the technical interaction/operation: The result of formal validation by itself does NOT impair the software's processing of the technical interaction/operation. The software has detected a data constellation that indicates (a) data is incomplete or incorrect, e.g. inconsistent, and/or (b) described activities or objects do not comply with the requirements, e.g. legal regulations or official constraints. Successful processing of the technical interaction/operation: The data constellation by itself does NOT impair the software's processing of the technical interaction/operation.
ERROR Error The formal validation has detected data constellations that indicate (a) data is incomplete or incorrect, e.g. inconsistent, and/or (b) described activities or objects do not comply with the requirements, e.g. legal regulations or official constraints. The validation protocol contains at least one ERROR entry. The validation protocol may also contain WARNING and/or INFO entries. Rejection/abortion of the technical interaction/operation: The result of the formal validation is such that the software does NOT carry out the technical interaction/operation, i.e. it aborts or rejects the technical interaction/operation. In particular, in the case of data transmissions, addressees do NOT have access to the transmitted data. The software has detected a data constellation that indicates (a) data is incomplete or incorrect, e.g. inconsistent, and/or (b) described activities or objects do not comply with the requirements, e.g. legal regulations or official constraints. Rejection/abortion of the technical interaction/operation: The data constellation is such that the software does NOT carry out the technical interaction/operation, i.e. it aborts or rejects the technical interaction/operation. In particular, in the case of data transmissions, addressees do NOT have access to the transmitted data.
4 items found, showing all items.