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

Please visit the LexEVS 5.1 Scope document found at:  https://wiki.nci.nih.gov/display/EVS/LexEVS+5.1+Scope+document^{Image Added}

Use cases

Please visit the LexEVS Gforge site to view applicable Gforge bugs/enhancements for LexEVS 5.1:  https://gforge.nci.nih.gov/projects/lexevs/^{Image Added}

Related requirements

Please visit the LexEVS Gforge site to view applicable Gforge bugs/enhancements for LexEVS 5.1:  https://gforge.nci.nih.gov/projects/lexevs/^{Image Added}One heading for each item.

Solution Architecture

Proposed technical solution to satisfy the requirements.

Performance Enhancements

 RRF Data

Value Set/Domain Support

Loading Framework

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.

Performance Enhancements

 RRF Data

Value Set/Domain Support

Loading Framework

Implementation Requirements

Training and documentation requirements

One heading for each item.

Download center changes

List the needed changes.