Page History

...

• Semantic Infrastructure Users and Roles
• Functional Requirements
  • ECCF Artifact Management
    • Static Models
    • Behavioral Models
    • Forms
    • Specification Content
  • Services Lifecycle Management & Governance
    • Discovery
    • Lifecycle Management
    • Governance
  • Case Report Form Modeling
    • Form template editingauthoring
  • Conformance Testing
  • P/S/T & Terminology Integration
    

Requirements Analysis

This section presents the dervied requirements as a result of the requirements analysis of the use cases presented in section 3 - caGrid 2.0 Use Cases August 30, 2010previous section. The analysis includes tracing of requirements up to the use case and stakeholders and down to service capabilities specified later in this document.

...

Semantic Infrastructure Consumers and Roles

caGrid 2.0 as defined in the introduction, The semantic infrastructure is expected to address the needs of a broad group of stakeholders. The semantic infrastructure as defined in this section provides foundational specifications and capabilities for three groups of primaryusers: service developers, application developers, and platform developers. The platform provides infrastructure and utility capabilities in service and non-service forms to enable service developers and application developers to create and compose higher level functionalities.

Mapping to the CBIIT enterprise service inventory (diagram below), the platform includes the infrastructure and utility services to support core, capability, and business services. The platform developers in vendor and open source communities are enabled by the Platform Specifications and SOA industry standards and principles to provide pluggable implementations of platform components and capabilities. It is important to note that caGrid 2.0 both leverages and informs the enterprise service inventory.

Figure 4.1 CBIIT Enterprise Service Inventory

Security in caGrid 2.0 provides foundational security services via the platform itself, exposing security features through services plugged into the platform. The Tooling component is aimed at providing tools, defined as software components that require user interaction, to our primary and secondary users, both service and application developers as well as bioinformaticians, scientists, and other "non-developers" in the cancer research community.

A separate effort is being undertaken to define and use static and behavioral semantics as part of the Semantics Infrastructure. It is fully anticipated that the caGrid 2.0 and the Semantics Infrastructure will interface to integrate run-time semantics into the platform, providing capabilities such as semantic query, semantic reasoning, and more.

Numerous additional stakeholders, as outlined above, contribute to the scope definition, use cases, and requirements that end up in the platform security and tooling components as outlined throughout the rest of this document.

...

the following key users:

• Clinicians
• Model Developers
• Service Developers
• Service Architects
• Service Analysts
• CBIIT Enterprise Architecture Governance
• Vendors
• Platforms, including caGrid 2.0
• BioInformatics Specialists

Functional Requirements

This section includes:

• Functional requirements
• Data requirements
• Security requirements

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

Functional requirements defines the key requirements for  provides Functional requirements define what the caGrid 2.0 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 access.

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.

Functional Requirements

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

...