DESCRIPTION:
Shares the functionality of verifying that several solutions can interoperate at one or more layers of the interoperability stack, while conforming to one or more specifications. This type of testing is executed by operating SUTs (System Under Test) and capturing their exchanges.
The logistics of interoperability testing is usually more costly (time, coordination, interoperability), and interoperability testing is no substitute for a conformance test suite. Experience shows that interoperability testing is more successful and less costly when conformance of implementations has been tested first.
Based on CEN/CENELC GITB
https://www.cen.eu/work/areas/ict/ebusiness/pages/ws-gitb.aspx
INTEROPERABILITY SALIENCY:
The Conformance Testing Services ABB is salient for technical interoperability because it enables the validation and verification that several solutions at one or more layers of the interoperability stack and they satisfy certain interoperability requirements.
EXAMPLES:
The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB):
Interoperability Testbed
The Test Bed allows users to execute predefined test cases on their systems. Test results are provided in a standardised, machine-readable format. The Test Bed also offers a test registry and repository (TRR) to store test artefacts (assertions, test cases, validation schemas, etc.) and compile test services (validation services, simulator services, etc.).
https://ec.europa.eu/isa2/solutions/interoperability-test-bed_en
|
|
| ID | ABB128 |
| dct:type | eira:TestService |
| dct:publisher | |
| dct:modified | |
| eira:status | [ Exists | Development planned ] |
| eira:reusability | [ Excellent (90-100%) | Very good (70-89,9%) | Fair (50-74,9%) | Poor (0-49,9%) ] |
| eira:actual_use | [ Currently used | Used planned | No ] |
| difi:namespace | eira |
| difi:name_no | Conformance Testing Service [ns:eira] |
| difi:description_no | DESCRIPTION:
Shares the functionality of verifying that several solutions can interoperate at one or more layers of the interoperability stack, while conforming to one or more specifications. This type of testing is executed by operating SUTs (System Under Test) and capturing their exchanges.
The logistics of interoperability testing is usually more costly (time, coordination, interoperability), and interoperability testing is no substitute for a conformance test suite. Experience shows that interoperability testing is more successful and less costly when conformance of implementations has been tested first.
Based on CEN/CENELC GITB
https://www.cen.eu/work/areas/ict/ebusiness/pages/ws-gitb.aspx
INTEROPERABILITY SALIENCY:
The Conformance Testing Services ABB is salient for technical interoperability because it enables the validation and verification that several solutions at one or more layers of the interoperability stack and they satisfy certain interoperability requirements.
EXAMPLES:
The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB):
Interoperability Testbed
The Test Bed allows users to execute predefined test cases on their systems. Test results are provided in a standardised, machine-readable format. The Test Bed also offers a test registry and repository (TRR) to store test artefacts (assertions, test cases, validation schemas, etc.) and compile test services (validation services, simulator services, etc.).
https://ec.europa.eu/isa2/solutions/interoperability-test-bed_en
|
| difi:name_en | |
| difi:description_en | |
| difi:language | no |
| label | ${name} [ns:${property:difi:namespace}] |