Services specifications developed by NCI and the community have to be testable to ensure that the implementation conforms to the specification.
Conformance testing leverages the artifact and service metadata to validate that an implementation adequately addresses the requirements stated in the service specification. An example of service requirement is the ability to specify a response time in the specification (design time) and validate that this response time is valid for an implementation of the service. Additional test points include but are not limited to binding to specific terminologies and domain models.
Capabilities related to Conformance Testing within the Semantic Infrastructure are summarized as:
- Testing for Conformance, including a Service-Oriented Architecture (SOA) Testing Environment and semantic validation of interoperability
Conformance testing allows both CBIIT and other HL7 SAIF adopters to validate specifications.
Functional Profile Group
- 5.2.4.1 - Create Conformance Statements Sept. 6, 2010
- 5.2.4.2 - Search and Access Conformance Statements Sept. 6, 2010 Conformance testing leverages the artifact and service metadata to validate that an implementation adequately addresses the requirements stated in the service specification. An example of service requirement is the ability to specify a response time in the specification (design time) and validate that this response time is valid for an implementation of the service. Aadditional test points include but are not limited to binding to specific terminologies and domain models.
- 5.2.4.2.1 - Conformance Analysis Sept. 6, 2010 Provides search and access for conformance statements associated with design models and run-time artifacts
- 5.2.4.3 - Test for Conformance Sept. 6, 2010 Testing for SOA combines the typical challenges of software testing and certification with the additional needs of accommodating the distributed nature of the resources, the greater access of a more unbounded consumer population, and the desired flexibility to create new solutions from existing components over which the solution developer has little if any control. The purpose of testing is to demonstrate a required level of reliability, correctness, and effectiveness that enable prospective consumers to have adequate confidence in using a service.
- 5.2.4.3.1 - SOA Testing Sept. 6, 2010 Testing for SOA combines the typical challenges of software testing and certification with the additional needs of accommodating the distributed nature of the resources, the greater access of a more unbounded consumer population, and the desired flexibility to create new solutions from existing components over which the solution developer has little if any control. The purpose of testing is to demonstrate a required level of reliability, correctness, and effectiveness that enable prospective consumers to have adequate confidence in using a service. Adequacy is defined by the consumer based on the consumer's needs and context of use. Absolute correctness and completeness cannot be proven by testing; however, for SOA, it is critical for the prospective consumer to know what testing has been performed, how it has been performed, and what were the results.
- 5.2.4.3.2 - Validate Sept. 6, 2010 Conformance testing leverages the artifact and service metadata to validate that an implementation adequately addresses the requirements stated in the service specification. An example of service requirement is the ability to specify a response time in the specification (design time) and validate that this response time is valid for an implementation of the service. Additional test points include but are not limited to binding to specific terminologies and domain models.
