Page info
title title

*Author:* \[Project Manager/Technical Lead\]
*Email:* \[Email address for Scope Document contact\]
*Team:* \[For example caDSR, EVS, caGRID, and so on.\]
*Contract:* \[Contract number\]
*Client:* NCI CBIIT
National Institutes of Heath
US Department of Health and Human Services

The *purpose of this document* is to collect, analyze, and define high-level needs for and designed features of the \[Product or Component Name x.x\].  The focus is on the functionalities proposed by the stakeholders and target users to make a better product.  The use case documents show in detail how the features meet these needs.

Design Scope

GForge items

One heading for each item, to include functional and non-functional requirements and bug fixes.

Use cases

Links to available documents.

Related requirements

One heading for each item.

Solution Architecture

Proposed technical solution to satisfy the requirements.

Cross product dependencies

Include a link to the Core Product Dependency Matrix.

Changes in technology

Include any new dependencies in the Core Product Dependency Matrix and summarize them here.

Assumptions

List any assumptions.

Risks

List any risks.

Detailed Design

Specify how the solution architecture will satisfy the requirements. This should include high level descriptions of program logic (for example in structured English), identifying container services to be used, and so on.

Implementation Requirements

Training and documentation requirements

One heading for each item.

Download center changes

The purpose of this document is to collect, analyze, and define high-level needs for and designed features of the National Cancer Institute Center for Biomedical Informatics and Information Technology (NCI CBIIT) caCORE LexEVS Release 6.1. The focus is on the functionalities proposed by the stakeholders and target users to make a better product.

Design Scope

Please view the LexEVS 6.1 Scope document (LexEVS 6.1 Scope Document)

JIRA items

Please view the LexEVS 6.1 JIRA items (LexEVS 6.1 JIRA Items)

Use Cases and Requirements Mapping

Please view the LexEVS 6.1 Use Case Document and the LexEVS 6.1 Requirements Mapping Document.

Detailed Design

The following sections specify how the design will satisfy the requirements.

Detailed Design - CTS 2 REST Services

Please view the detailed design: LexEVS 6.1 Design Document - Detailed Design - CTS2 REST Services

Detailed Design - Loader - OWL2

Please view the detailed design:LexEVS 6.1 Design Document - Detailed Design - Loader - OWL2

Detailed Design - Loader - HL7 MIF

Please view the detailed design:LexEVS 6.1 Design Document - Detailed Design - Loader - HL7 MIF

Detailed Design - Loader - MedDRA

Please view the detailed design:LexEVS 6.1 Design Document - Detailed Design - Loader - MedDRA

Detailed Design - Performance - Hierarchy Traversal

Please view the detailed design:LexEVS 6.1 Design Document - Detailed Design - Performance - Hierarchy Traversal

Detailed Design - Performance - Text Search (Contains)

Please view the detailed design:LexEVS 6.1 Design Document - Detailed Design - Performance - Text Search (Contains)

Detailed Design - Performance - Value Set Resolution (Persistence)

Please view the detailed design:LexEVS 6.1 Design Document - Detailed Design - Performance - Value Set Resolution (Persistence)List the needed changes.