Author: Traci St.Martin/Craig Stancl
Email: stmartin.traci@mayo.edu
Team: LexEVS/EVS
Contract: SAIC Subcontract#28XS112
Client: NCI CBIIT
National Institutes of Heath
US Department of Health and Human Services
Sign off |
Date |
Role |
CBIIT or Stakeholder Organization |
Reviewer's Comments (If disapproved indicate specific areas for improvement.) |
|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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.
Note
Use the sub-headings that you need for details of your Design Scope, Solution Architecture, and Implementation Requirements. Delete the ones you do not need, along with this note.
Design Scope
GForge items
Please visit the LexEVS 5.1 Scope document found at: https://wiki.nci.nih.gov/display/EVS/LexEVS+5.1+Scope+document
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/
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/
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 Plan
This will include the technical environment (HW,OS, Middleware), external dependencies, teams/locations performing development and procedures for development (e.g. lifecycle model,CM), and a detailed schedule.
Technical environment
External dependencies
Team/Location performing development
Procedures for Development
Detailed schedule
The LexEVS 5.1 project plan is located in Gforge at:
Training and documentation requirements
One heading for each item.
Download center changes
List the needed changes.
