NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin
Scrollbar
iconsfalse

Page info
title
title

25%
Panel
titleContents
Table of Contents
minLevel2
Section
Column
width
Panel
titleDocument Information

Wiki Markup
*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

Panel
titleContents
Table of Contents
maxLevel1
column

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

Sign off

Date

Role

CBIIT or Stakeholder Organization

...

 

...

 

...

 

...

 

...

 

...

 

Wiki Markup
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 \[product\] Release \[x.x.x.x\]. 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

Wiki Markup
The *objective of this release* of the \[product/component\] is to \[brief statement of the release theme, for example, improve usability for creating and maintaining value meanings\].

Wiki Markup
This release will address \[detailed description of the problem statements to be resolved by the release, such as fixes, usability improvements, functional improvement, and performance improvements for an incremental release\].

Current Solution

Wiki Markup
\[Optional, briefly describe the existing solution and shortcomings.\]

Proposed Solutions

...

Hartel

7/2/09

PM

NCI EVS

Raghu

7/2/09

PM

caDSR and EVS Project Manager

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 support the Metathesaurus Browser project by enhancing search and sorting performance as well as RRF loader changes to more accurately reflect the data. In addition we will explore enhancements to the loader framework and provide a recommendation/implementation for value set/domain support.

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

...

 

...

 

...

 

...

 

...

 

...

 

...

 

...

 

...

 

...

 

...

 

...

 

21182

Value Set Support recommendation/implementation

21976

Improved loading framework

21979

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

21978

BDA support for 5.1

---

Update RRF loader to support Metathesaurus (Please see GForge items below)

---

Improve the API to efficiently support expanded search options and large concept relationships sets (Please see Gforge items below)

...

 

...

 

...

 

...

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

...

 

...

 

...

 

...

 

...

 

...

 

...

 

...

 

...

 

...

 

...

 

...

 

15975

The NCI_Thesaurus association Has_Salt_Form and Has_Free_Acid_Or_Base needs reverse name

20875

Unescaping XML character data in complex properties

20896

User question about Metathesaurus Term-group

21278

Displaying multiple concept status.

21287

SNOMED Full Name instead of Full form.

21336

Lucene Max Clause Count exceeded on broad NCI MetaThesaurus RegExp Restrictions

21567

ResourceManager cache not Thread-safe

21716

Add data from MRSAT file to NCI Meta data

21717

MRSAB conifgured to load for NCI Meta data

21718

MRREL data for NCi Meta - needs more data loaded

21719

Load MRRANK data for NCI Meta

21720

Load all MRMAP data

21721

Add some additional data from MRHIER

21722

Make sure MRDOC data for NCI Meta is loaded

21723

Add more data from MRDEF file for NCI Meta

21724

Add data from MRCONSO file to NCI Meta data

21739

CodedNodeGraph resolveAsList distributed method encountered Jaa heap space error

21740

Heap space error on Double Metaphone MetaThesaurus query

21849

Add an algorithm for supporting case-insensitive substring search.

21850

Add a search algorithm for supporting case-insensitive substring search with an additional spelling-error tolerant feature.

21851

Add a sort option for ranking matched concepts by similarity score.

21879

Improve error messages (e.g., CNS.resolve, CNS.resolveToList, CNG.resolveToList)

21880

Make sample programs (in the examples folder) runnable under both local and distributed modes.

21881

Improve ResolvedConceptReferencesIterator performance by reducing client-server network traffic in distributed mode.

21923

Connection Leak on SQLImplementedMethods 'mapToCodingSchemeName'

21935

OWL loader processing associations incorrectly

21980

Optimize Lucene code to improve search performance

21982

Implement a server side sort to improve performance

...

 

...

 

...

 

...

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

...

 

...

Example, "Although there are no functional changes to the product for this requirement, the team must migrate the existing software to Hibernate 4.1 to be compatible with the caCORE technology stack."

...

 

...

 

...

 

...

 

...

 

...

 

...

 

...

 

...

 

...

 

21981

Project plan for 5.1

21988

Test plan & test results

21990

Design and Implementation plan

21991

Release notes for 5.1

21992

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

21993

5.1 Deployment to Dev Tier

21994

5.1 Deployment to QA Tier

21995

5.1 Deployment to Stage Tier

21996

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

...

 

...

Example, "Level 2 Support, integration of help and training to the user community."

...

 

...

 

...

 

...

 

...

 

...

 

...

 

...

 

...

 

...

 

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="224fcf4d-2d28-4c11-8c75-df22e585e6a4"><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="4e40fd26-ba29-495f-a803-9ebc228f5830"><ac:plain-text-body><![CDATA[

...

[Name]

...

[Role in this project]

...

 

...

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

...

 

...

 

...

 

George Komatsoulis

NCICB Application Infrastructure

Oversees NCICB Application Infrastructure

Avinash Shanbhag

NCICB Application Infrastructure

Oversees NCICB caCORE Software Engineering

Frank Hartel

EVS Product Manager

Directs EVS Projects

Denise Warzel

CORE Product Line Manager

Trans-CORE requirement coordination

Gilberto Fragoso

Associate Director EVS Infrastructure

Technical Direction

Jason Lucas

NCI Metathesaurus Browser Project Manager

Project schedule and task management for browser team

Raghu Chintalapati

EVS Project Manager

Project schedule and task management

Craig Stancl

Mayo Clinic Technical Lead

Technical Direction and Implementation

Traci St.Martin

Mayo Clinic Project Manager

Project schedule and task management

Larry Brem

SAIC caBIG ARCH and VCDE Technical Program Manager

Contract governance

...

 

...

 

...

Technical Environment

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

...

Client Interface

...

  • Wiki Markup
    \[Example, Internet Explorer 6.0 and above\]]]></ac:plain-text-body></ac:structured-macro>
    <ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="7327f7c3-3e90-4b27-a883-899b14b190ca"><ac:plain-text-body><![CDATA[* \[Example, Mozilla v. 1.5.0.3 and above\] 

...

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

  • NCI browsers
  • Programs accessing through caCORE/EVS APIs

Application Server

Jboss application server

Database Server

MySQL

Operating System

  • Windows 2000, XP
  • Unix (Sun Solaris)

...

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="97dcb08e-0a3c-486e-95c8-c5a377ffee1e"><ac:plain-text-body><![CDATA[

...

Application Server

...

[Example, Apache Tomcat 5.5.9]

...

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

...

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="074ee1af-fa7d-4602-8e53-5cd4b5b8b55e"><ac:plain-text-body><![CDATA[

...

Database Server

...

[Example, Oracle 9i]

...

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

...

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="308f22e6-0737-41dc-9fdf-9f2b2583d758"><ac:plain-text-body><![CDATA[

...

Operating System

...

  • Wiki Markup
    \[Example, Windows 2000. XP, Vista\]]]></ac:plain-text-body></ac:structured-macro>
    <ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="3f6cd190-8401-4f3f-8169-6ec43637e785"><ac:plain-text-body><![CDATA[* \[Example, Unix (Sun Solaris)\] 

...

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

...

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="e35064ef-5435-4a7d-bf92-2d5b376ff92d"><ac:plain-text-body><![CDATA[

...

[Other]

...

 

...

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

Product Dependencies

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

Wiki Markup
\[Provide additional explanation as applicable. For example, "The EVS vocabulary systems are used by the Java client to retrieve and validate concept information for naming and defining meanings."\]

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

...

 

...

 

...

 

...

 

...

 

...

 

...

 

...

 

...

 

15667

gov.nih.nci.evs.domain.Atom.getLUI does not return value. Per the tracker, Consensus says to deprecate. Lexbig does not load LUI and no user has noticed. Therefore this bug is deferred.

Inception

16678

Serializer Exception on org.apache.lucene.search.regex.JavaUtilRegexCapabilities. Per the tracker, I've replicated what this method does and and called it outside the DLBAdapter and things work fine. Therefore this bug is deferred due to low priority.

Inception

19406

Results not Deserializing Properly when using QueryModifiers on CQL Queries. This bug was discussed in our technical meeting and is deferred due to low priority

Inception

20590

Not all concept status property values are accessible through the API. This item has been discussed and is deferred due to low priority

Inception

20653

Anonymous class hierarchy with unions not showing up correctly. This item has been discussed and is not an issue for 5.0. Deferred due to low priority

Inception

20661

Ontology for Genetic Interval hierarchy does not match up Protege. This item has been discussed and is not an issue for 5.0. Deferred due to low priority

Inception

20665

ECG Ontology missing Description, Date, Source and Creator fields. This item has been discussed and is not an issue for 5.0. Deferred due to low priority

Inception

20684

Cannot compute root node for OBI version v1.0.1423. This item has been discussed and is not an issue for 5.0. Deferred due to low priority

Inception

20797

Strict Owl Processing. This item has been discussed and is not an issue for 5.0. Deferred due to low priority

Inception

...

 

...

 

...

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.

...

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="fc2d62e3-9975-4cb9-b4e9-8ab125e46f33"><ac:plain-text-body><![CDATA[

Project GForge site:

...

[Project GForge site link]

...

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

LexEVS GForge project Docs archive, Files archive

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.

...

Related documents:

[EVS:Name and URL of each related document]

...

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

Project Information

CBIIT Management

Role

Responsibilities

...

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="e2d3e0f0-9b3c-4fa1-8d5a-4bdfb7094f59"><ac:plain-text-body><![CDATA[

...

[Name]

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.

Scrollbar
iconsfalse