NIH | National Cancer Institute | NCI Wiki  

Document Information

Author: Craig Stancl, Scott Bauer, Cory Endle
Email:craig.stancl2@nih.gov, scott.bauer@nih.gov, cory.endle@nih.gov
Team: LexEVS
Contract: 20X048F
Client: NCI CBIIT
National Institutes of Heath
US Department of Health and Human Services

Contents of this Page

Project Scope

The purpose of this document is to collect, analyze, and define high-level needs and features of the National Cancer Institute Center for the duration of this contract (8/31/2019- 8/30/20). This document focuses on the functions proposed by the product stakeholders and target users in order to make it a better product.

Vision and Needs

The objective of this release of the LexEVS is to provide a bug fixes and a set of new features as captured in the document.

High-Level Scope and Priorities


Functional Requirements

Each enhancement, modification or new feature is described in detail in the following documents.

LexEVS 6.5.3

Functional requirements for 6.5.3 can be found here: LexEVS 6.5.3 Release Notes

LexEVS 6.5.4

Functional requirements for 6.5.4 can be found here: LexEVS 6.5.4 Release Notes

Functional Bug Fixes

Each bug fix included in this release is described in detail in the following documents.  

LexEVS 6.5.3

Non-Functional Requirements and Functional Bug Fixes for 6.5.3 can be found here: LexEVS 6.5.3 Release Notes

LexEVS 6.5.4

Non-Functional Requirements and Functional Bug Fixes for 6.5.4 can be found here:LexEVS 6.5.4 Release Notes

Non-Functional Requirements

This section describes in detail all the related requirements which must be met for this release but do not add functionality. These requirements are included in the scope and project plan due to level of effort or relative importance to the overall success of delivery of the release.

Project

JIRA number (hyperlinked)

Project

Brief description of non-functional requirement

Status
(Approved or Proposed)

Iteration






General Support Activities

This section describes in detail all the related activities which must be performed for this release but do not add functionality. These activities are included in the scope and project plan due to level of effort or relative importance to the overall success of delivery of the release.

JIRA number (hyperlinked)

Brief description of general support activity

Status
(Approved or Proposed)

Iteration






Out of Scope Items

Items that are out of scope were evaluated as part of the initial scoping activities for this release, and subsequently not included in the final approved scope. These items are also documented in the cumulative backlog of requirements found on the product JIRA site. They include out-of-scope functional requirements (enhancements or new features), bug fixes, non-functional requirements, and general support activities.

JIRA number (hyperlinked)

Project

Brief description of item moved from the in-scope section
with brief explanation added of why it was not included in this release

Iteration during which the item
was removed from in-scope