Notice: This application will enforce Multi-factor authentication (MFA) for NIH users beginning the evening of Wed Aug 3rd.
NIH | National Cancer Institute | NCI Wiki  

Contents of this Page

Author:

Charles Griffin, Denis Avdic

Email:

griffinch@mail.nih.gov

Team:

MDR

Contract:

27XS083

Client: | National Cancer Institute Center for Biomedical Informatics and Information Technology
National Institutes of Heath
US Department of Health and Human Services
|

The purpose of this document is to collect, analyze, and define high-level needs and features of the NCI CBIIT MDR Data Warehouse iteration 3 of the 1.0 release. This document focuses on the functionality 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 is to take the prototype warehouse schema that was created during iteration 1 and iteration 2 of this 1.0 release and utilize it as back end database in a production environment for a new browser within the caDSR suite.  The new browser will provide a flattened view of caDSR content to users in the general public who do not understand ISO 11179. To support the open systems initiative at NCI CBIIT, the MySQL version of the MDR Data Warehouse will be utilized in lieu of the Oracle version. Since the MDR Data Warehouse schema and ETL scripts have been created during the first two iterations, it is expected that only minor tweaks to the warehouse will be need to support the new caDSR flattened view browser.

In addition to the changes to support the new caDSR flattened view browser, work will be done to specify the requirements and design for the MDR Warehouse to support the following four views:

1) A domain model (11179) view for all Administered Items

2) A Data Element View (flattened view)

3) A UML Browser view

4) A Forms View
Finally, as part of this iteration, an API will be provided that will enable users and applications to search the MDR Data Warehouse. It's expected that this API would resemble a caCORE SDK generated system.

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)

Create a design and implement changes to the MDR Data Warehouse schema necessary to support the new caDSR flattened view browser if any.

Create a design for and implement an API that will allow remote and local users and applications to query the the MDR Data Warehouse. he design should utilize caCORE components that are available i.e. caCORE SDK if possible.

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)

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)

Create a design that details any changes that would need to be made to the MDR Data Warehouse to support a domain model (11179) view for all Administered Items

---

Create a design that details any changes that would need to be made to the MDR Data Warehouse to support a Data Element view (flattened view)

---

Create a design that details any changes that would need to be made to the MDR Data Warehouse to support a UML Browser view

---

Create a design that details any changes that would need to be made to the MDR Data Warehouse to support a Forms view

---

Specify the process that the systems team will need to follow to periodically run the ETL scripts to populate the MDR Data Warehouse schema with the latest data in the caDSR transactional system. The deliverable for this requirement is a document providing step by step instructions that the systems team can follow.

---

Define a process that would make the contents and the schema of the MDR Data Warehouse available for download for adopters. How often the data for the download is updated will be decided by MDR product management.

---

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)

N/A

Stakeholder Summary

Customer Name

Role

Interest/Need

Denise Warzel

caCORE Product Line Manager

---

Dave Hau

caCORE Assistant Director of Core Engineering

---

caDSR Users and modelers

Users that search caDSR content for various meta data

---

CBIIT Staff/Contractor Name

Role

Responsibilities

Charles Griffin

Project Manager

Denis Avdic

Architect/Developer

Nadine Azie

Data Architect

Technical Environment

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

Client Interface

Internet Explorer 6.0, Mozilla v. 1.5.0.3 and above

Application Server

JBoss 4.0.5

Database Server

mySQL 5.0

Operating System

Windows 2000. XP, Vista, Linux

Product Dependencies

This release is dependent on the caCORE components or products documented in the Legacy caDSR Technology 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:

[:Project GForge site link]

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:

[Name and URL of each related document]

Project Information

CBIIT Management

Role

Responsibilities

Denise Warzel

Product Manager

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

Dave Hau

Engineering Manager

Oversees NCICB caCORE software engineering practices, conducts design reviews, guides technical development for MDR, caDSR, CSM, CLM, and SDK

Denise Warzel

Product Line Manager

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

Document Signoffs

CBIIT Management

Role

Stakeholder Management

Role

Sign off

Date

---

---

---