New Account Helpful Tips
  CORE - EVS
  LexEVS 4.2.1 Scope Document
Added by Traci StMartin, last edited by Traci StMartin on Jan 23, 2009  (view change)

Labels

 
Document Information

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

Sign off Date Role
CBIIT or Stakeholder Organization
Hartel 10/21
Product Manager NCI EVS
Fragoso     NCI EVS
Beasley 10/30
Overall EVS Technical Lead NCI EVS
Griffin
Overall EVS Project Manager NCI EVS
Lucas 10/30 Project Manager NCI EVS

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 EVS Release 4.3. 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 4.2.1 is to deliver any critical bux fixes and be used to deprecate EVS 4.0 support and give notice to users of the pending deprecation of the 3.2 API and EVS 4.1.  We will also look into piloting the BDA process.

Current Solution

LexEVS 4.2 

Proposed Solutions

Maintain 4.2 code base but deprecate EVS 4.0.

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)
Iteration
(Approved or Proposed)
17198 Pilot BDA process  
17199 Tag the API classes as deprecated  
17670 DAO is throwing a ClassCastException when attempting access MedDRA  
     

Functional Bug Fixes

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

GForge number
(hyperlinked)
Brief description of bug
Iteration
(Approved or Proposed)
  TBD - critical fixes only  
     
     
     

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
Iteration
(Approved or Proposed)
17072 Project plan for 4.3  
17073 Release notes for 4.3  
17074 Update Tech and Admin Guides for 4.3  
17087 Deploy to NCI Dev tier  
17088 Deploy to QA tier  
17089 Deploy to Stage tier  
17090 Deploy 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 Iteration
(Approved or Proposed)
17939 MySQL 5.0.45 upgrade  
     
     
     

Stakeholder Summary

Customer Name
Role
Interest/Need
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
Johnita Beasley Project Manager Technical Direction and Implementation
Gilberto Fragoso Associate Director EVS Infrastructure Technical Direction
Denise Warzel CORE Product Line Manager Trans-CORE requirement coordination
Thomas Johnson Mayo Clinic Software Engineering Manager Technical Direction and Implementation
Jason Lucas Project Manager Project schedule and task management
Traci St.Martin Mayo Clinic Project Manager Project Schedule and task Management
CBIIT Staff/Contractor Name
Role
Responsibilities
[caCORE:Name]
[caCORE:Role in this project]
 
     
     

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)
[caCORE:Other]  

Product Dependencies

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

[caCORE: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
     
     
     
     

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.
Related documents:
[caCORE:Name and URL of each related document]

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.


CONTACT US PRIVACY NOTICE DISCLAIMER ACCESSIBILITY APPLICATION SUPPORT
National Cancer Institute Department of Health and Human Services National Institutes of Health USA.gov