 |
Page History
...
Service Lifecycle Management and Governance
Service deployment requirements include instance-specific configuration of service policies, business logic configuration, security configuration, and local or remote (for example, cloud) deployment. The requirements also include configuration of instance-specific service metadata, advertisement, and publication of a service to the broader ecosystem for re-use.Link to use case: the services may be located at an institution or hosted externally by service providers.lifecycle management and governance allows service developers to specify rich metadata about services. This enables better discovery, and governance of services.
Service lifecyle management requirements include
The manage capability enables management of service metadata, as well as service interactions, dependencies, and redundancies. You can classify services based on business objectives, manage policies for service usage, and monitor how services are changed and versioned. Also, you can link related documents (such as PDF files) to service metadata. This capability helps you optimize the use of services in an SOA by exchanging rich service metadata with runtime service registry.
Promote Service Reuse:
Establish Service policies:
Lifecycle Management:
Better Discovery:
The requirements listed above are derived from the following use cases in the previous section:
caEHR: The caEHR project is developing service specifications and lacks the infrastructure to govern services.
CBIIT Projects: CBIIT has adopted SOA. Service lifecycle management and governance are industry best practices for organizations adopting SOA. Better service discovery
Forms Definition & Modeling
...
Services specifications developed by NCI and the community have to be testable to ensure that the implementation is conformant with the specification.
Conformance Testing 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 during in the specification (design time) and validate that this response time is valid for an implementation of the service, additional test points include binding to specific terminologies, domain models, etc.
Conformance testing ensures interoperability by ensuring thatallows both CBIIT and other HL7 SAIF adopters to validate specifications.
The requirements listed above are derived from the following use cases in the previous section:
- CBIIT's adoption of ECCF: ECCF requires all specification developers to make conformance statements, this also provides a mechanism for external validators to the conformance testing framework leverages these conformance statements to generate validation tests
- ..
Service Generation
Service Discovery & Utilization
...
