Page History

...

• Artifact Management
• Service Lifecycle Management and Governance
• CRF Modeling
• Conformance Testing
• P/S/T & Terminology Integration

Functional requirements defines the key requirements for  provides in support of creation and composition of higher-level services utilized in the use case. Data requirements define the non-functional characteristics of data (including metadata) and service contract definition and management. These requirements are found in nearly all clinical and translational biomedical informatics systems, including the use case above. Security requirements are found throughout the use case, both during service invocation and data accessThe requirements listed above address one or more use cases in each domain. In addition to the domain specific use-cases, the requirements also address CBIIT's internal development and architecture requirements. Specifically, CBIIT has stardardized on Services Oriented Architecture as the foundational principle for applications architecture and interoperability. CBIIT has also adopted a formal approach to defining service specifications, supporting both interoperability, and the need to publish formal specifications that can be adopted by external organizations and vendors.

The following sections provide detail on these three categories of requirements, defining the requirement as well as describing the relevance to our use case for our primary and secondary users. Recall that the primary and secondary users include service developers, application developers, and platform developers along with service and application users as well as non-developer users from the cancer research community.

This section enumerates requirements elicited from the use case, organized by category.

use-cases. 

Artifact Management

This is a foundational requirements group that allows a service developer to build higher-level services (for example, a service in the NCI Enterprise Service Inventory) that are utilized in the use case. This group of requirements allows a primary user (service or application developer) to provide business logic as a service to the broader enterprise. This group of requirements focuses on specification-driven configuration of policies, security requirements, and metadata of the service, and a development process that allows service developers to focus on business logic.

Link to use case: service based capabilities for image databasing, image annotation creation capabilities, search and query, patient electronic medical record markup, glioblastoma recommended treatment analysis, and other capabilities in the use case.

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.

...

CRF Modeling

Discovery includes service discovery, data discovery, and policy discovery. Service discovery allows primary users as well as secondary users to locate a service specification and instances based on attributes in the service metadata (for example, via a search for specific micro-array analysis services). Data discovery enables secondary users to find the types of data available in the ecosystem as well as summary-level information about available data sets. Policy discovery allows application developers to find and retrieve policies on services.

Link to use case: As institutions share de-identified glioblastoma data sets, they are available to others via data discovery. The treatment recommendation service used by the oncologist is able to discover these new data sets and their corresponding information models, and include that data for subsequent use in recommendation of treatment.

...

Conformance Testing

Human semantics include metadata about a service that is meant to be displayed via a user interface, for example, a description of the operations defined on a service. Computable semantics are metadata that are added to a service primarily in order to facilitate service orchestration and choreography, and to specify precisely the semantic meaning of data in order to allow interpretation and reasoning. Services in the ecosystem must have both types of metadata in order to facilitate tools for the platform and enable working interoperability.

...