NIH | National Cancer Institute | NCI Wiki  

Error rendering macro 'rw-search'

null

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Document Information

Author: Traci St.Martin/Craig Stancl
Email: stmartin.traci@mayo.edu
Team: LexEVS
Contract: 28XS112
Client: NCI CBIIT
National Institutes of Heath
US Department of Health and Human Services

Contents

Sign off

Date

Role

CBIIT or Stakeholder Organization

 


 


 


 


 


 


The purpose of this document is to collect, analyze, and define high-level needs and features of the National Cancer Institute Center for Biomedical Informatics and Information Technology (NCI CBIIT) caCORE LexEVS Release 5.1. This document focuses on the functionalities proposed by the product stakeholders and target users in order to make it a better product. The use-case and supplementary specifications document will detail how the framework will fulfill these needs.

Vision and Needs

The objective of this release of the LexEVS 5.1 is to explore enhancements to the loader framework and recommendations for value set support.  

This release will address performance improvements in loading, support for value sets, and functional bug fixes identified from LexEVS 5.0.

Current Solution

LexEVS 5.0

Proposed Solutions

LexEVS 5.1

Functional Requirements

Each enhancement, modification or new feature is described in detail below.

GForge number
(hyperlinked)

Brief description of functional requirement
(enhancement or new feature)

Status
(Approved or Proposed)

Iteration

 

Value Set Support recommendation/implementation

 

 

 

Improved loading Framework

 

 

 

Improved ability to load RRF data

 

 

 

Improved ability to load OWL data

 

 

 

Improved performance of LexEVS loading

 

 

 

Ability to load custom data - custom loading feasibility/recommendation report

 

 

 

BDA support for 5.1

 

 

 

Search and retrieval functionality (Metathesarus) - sort functions, substring matching, etc.

 

 

 

 

 

 

Functional Bug Fixes

Each bug fix included in this release is described in detail below.

GForge number
(hyperlinked)

Brief description of bug

Status
(Approved or Proposed)

Iteration

20896/21287

User question about Metathesaurus Term-group / SNOMED Full Name instead of Full form

 

 

21278

Displaying multiple concept status.

 

 

21336

Lucene Max Clause Count exceeded on broad NCI MetaThesaurus RegExp Restrictions

 

 

20354

Root concepts found by ListHierarchyMetaBySource when running against NCI MetaThesaurus with source set to NCI are different from root concepts in NCI Thesaurus.

 

 

20043

Creation of XSL stylesheets for transformation of LexBig data to n-1 LexBig versions

 

 

15975

The NCI_Thesaurus association Has_Salt_Form and Has_Free_Acid_Or_Base needs reverse name.

 

 

14971

Make use of logging consistant. Eliminate System.out

 

 

 

Modification to loader for Metadata/RRF issues

 

 

21197

 

 

 

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.

GForge number (hyperlinked)

Brief description of non-functional requirement

Status
(Approved or Proposed)

Iteration

 

Project plan for 5.1

 

 

 

Test plan & test results

 

 

 

Design and Implementation plan

 

 

 

Design Review

 

 

 

Monthly Status Report

 

 

 

Deliverable readiness review

 

 

 

Project summary report

 

 

 

Release notes for 5.1

 

 

 

Updated programmer's guide and users guide documentation on VKC Wiki for 5.1

 

 

 

Participation/SME for caBIG Boot Camp

 

 

 

5.1 Deployment to Dev Tier

 

 

 

5.1 Deployment to QA Tier

 

 

 

5.1 Deployment to Stage Tier

 

 

 

5.1 Deployment to Production Tier

 

 

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.

GForge number (hyperlinked)

Brief description of general support activity

Status
(Approved or Proposed)

Iteration

 

Global Concept ID support for caGrid team

 

 

 

Support migration of other caCORE projects to LexEVS

 

 

 

Identify any 5.x/6.x requirements from caCORE teams as they migrate from EVS 3.x to LexEVS

 

 

 

 

 

 

Stakeholder Summary

Customer Name

Role

Interest/Need

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="322a732e-41ea-4c5f-b513-c1748ae4de24"><ac:plain-text-body><![CDATA[

[Name]

[Title or role]

 

]]></ac:plain-text-body></ac:structured-macro>

 

 

 

 

 

 

CBIIT Staff/Contractor Name

Role

Responsibilities

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="77725eee-82cc-41e5-b7c2-e4fd3d948cdf"><ac:plain-text-body><![CDATA[

[Name]

[Role in this project]

 

]]></ac:plain-text-body></ac:structured-macro>

 

 

 

 

 

 

Technical Environment

This product uses the following technical components which have been derived from the current NCICB Technology Stack.

Client Interface

  • NCI browsers
  • Programs accessing through caCORE/EVS APIs

Application Server

Jboss application server 

Database Server

MySQL

Operating System

  • Windows 2000, XP
  • Unix (Sun Solaris)

 

 

Product Dependencies

This release is dependent on the caCORE components or products documented in the CORE Product Dependency Matrix.

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 GForge site. They include out-of-scope functional requirements (enhancements or new features), bug fixes, non-functional requirements, and general support activities.

GForge number (hyperlinked)

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

 

 

 

 

 

 

 

 

 

 

 

 

Document History

Document Version:

Click the Info tab. View the Recent Changes or click the link to view the page history.

Last Modified:

Refer to the first line displayed in the document window.

Project GForge site:

https://gforge.nci.nih.gov/projects/lexevs/

Most current version:

Unless the display includes a notice that you are viewing a previous version, you are viewing the most current version of this Scope Document for the release indicated in the title.

Revision history:

Click the Info tab. In the Recent Changes area, click the link to view the page history.

Review history:

Click the Info tab. In the Recent Changes area, note the developer who made each change and the date and time. Refer to the Key People Directory for their roles. Click the link to view any page or to view the page history, and then click the link for a page. When the page opens, view the comments and changes made in that version.

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="8f350a78-2e6d-440f-b8f2-936668ca70be"><ac:plain-text-body><![CDATA[

Related documents:

[Name and URL of each related document]

]]></ac:plain-text-body></ac:structured-macro>

Project Information

CBIIT Management

Role

Responsibilities

Frank Hartel

Product Manager

Oversees development of the product: features, functions, definition of stakeholders, priorities within the scope, timeframe for release

Avinash Shanbhag

Engineering Manager

Oversees NCICB caCORE software engineering practices, conducts design reviews, guides technical development

Denise Warzel

Product Line Manager

Oversees NCICB caCORE product line. Responsible for overall product integration, major and minor release cycles. Supports Product Manager.

  • No labels