Author: Steve Alred
Email: alreds@mail.nih.gov
Team: caDSR
Contract: 27SX001
Client: NCI CBIIT
National Institutes of Heath
US Department of Health and Human Services
|
| Sign off |
Date |
Role
|
CBIIT or Stakeholder Organization
|
| Denise Warzel - pending LOE |
10/24/2008
|
Product Manager |
CORE Infrastructure Program 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 caDSR Semantic Integration Tools Release 4.0.0.2. 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 SIW and UML Model Loader is to support complex (e.g.ISO 21090) datatypes and to fix high priority bugs.
Functional Requirements
Each enhancement, modification or new feature is described in detail below.
GForge number
(hyperlinked) |
Component(s) |
Brief description of functional requirement
(enhancement or new feature)
|
Iteration
(Approved or Proposed)
|
| 9163 |
SIW, UML Loader
|
Provide support for complex datatypes (ISO 21090, HL7, COPPA). Both the Semantic Integration Workbench (GF17106) and the UML Model Loader (GF17107) will be enhanced. This will require allowing users to enter a datatype that is another registered caDSR class. |
Approved |
| 526 |
SIW |
Enhance the Semantic Connector to query existing caDSR elements in addition to EVS. This may include inserting the partially matching components, such as the DEC, when the Class and Attribute match, but the datatype does not, or inserting the concepts or components that match at the Class (Object Class) and Attribute (Property) level.
|
Future |
| |
|
Allow users to match to a Backbone model in which they only difference between their model and the backbone for a given attribute is the constraints/enumerations on the value domain. |
Future |
| 14489 |
UML Loader
|
Allow all primary Value Domain Administered Item attributes to be specified via tagged values |
Approved
|
| TBD |
UML Loader
|
Work with Form Builder team to identify and develop Loader enhancements needed for bulk loading metadata from Excel files
|
Approved
|
| 17786 |
UML Loader
|
Use USER Account table to identify Loader Account
|
Not Approved but completed
|
| 17543 |
UML Loader
|
Create UMLLoader password Swing UI |
Not Approved but completed
|
Functional Bug Fixes
Each bug fix included in this release is described in detail below.
GForge number
(hyperlinked) |
Component |
Brief description of bug
|
Iteration
(Approved or Proposed)
|
| 16024 |
SIW |
SIW Child class inherited attribute and child class NON-inherited attribute can be mapped to same CDE |
Approved |
| 13594 |
UML Loader
|
UML Loader doesn't load model Alt.definition when attribute is mapped to CDE
|
Approved
|
6757
|
UML Loader
|
Redesign UML Loader not to use 'name' for examining concept derivation rules
|
Approved
|
| 16649 |
SIW |
Fix NullPointerException for problem model; improve exception handling/reporting for this problem
|
Approved
|
| 16975 |
SIW |
EVS queries should be case insensitive
|
Approved |
| 18222 |
SIW |
DEV: NullPointerEx. when expanding tree. |
Fixed but not approved for scope yet
|
| 17462 |
SIW |
Cannot save Model Owner Verified checkmark for Value Domain |
Fixed but not approved for scope yet
|
| 13116 |
SIW
|
The Map to CDE box containing CDE info is too big in SIW 3.2.1.3 |
Fixed but not approved for scope yet
|
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)
|
17250
|
Implement automated deployment process for SIW
|
Approved
|
| |
|
|
| |
|
|
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) |
| |
Example, "Level 2 Support, integration of help and training to the user community." |
|
| |
|
|
| |
|
|
| |
|
|
Stakeholder Summary
Customer Name
|
Role
|
Interest/Need
|
Christo Andonyadis
|
COPPA Architect
|
|
| |
|
|
| |
|
|
CBIIT Staff/Contractor Name
|
Role
|
Responsibilities
|
Denise Warzel
|
[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
|
- [caCORE:Example, Internet Explorer 6.0 and above]
- [caCORE:Example, Mozilla v. 1.5.0.3 and above]
|
| Application Server |
[caCORE:Example, Apache Tomcat 5.5.9] |
| Database Server |
[caCORE:Example, Oracle 9i] |
Operating System
|
- [caCORE:Example, Windows 2000. XP, Vista]
- [caCORE:Example, 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:
|
[caCORE: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:
|
[caCORE: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
|
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.
|
|
