Author: |
Charles Griffin |
Email: |
griffinch@mail.nih.gov |
Team: |
EVS |
Contract: |
|
Client: |
National Cancer Institute Center for Biomedical Informatics and Information Technology |
The purpose of this document is to collect, analyze, and define high-level needs and features of the NCI CBIIT Protege Release 1.3. This document focuses on the functionalities proposed by the product stakeholders and target users in order to make it a better product.
Vision and Needs
The objective of this release of the Protege 1.3 is to introduce the database inclusion enhancements that will allow editors to utilize Protege to edit multiple namespaces.
This release will also incorporate defects fixes and other minor feature requests that were high priority items identified by the NCI editing team that were not able to be addressed in the Protege 1.2.3 release.
Functional Requirements
Each enhancement, modification or new feature is described in detail below.
GForge number |
Brief description of functional requirement |
Iteration |
|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
Functional Bug Fixes
Each bug fix included in this release is described in detail below.
GForge number |
Brief description of bug |
Iteration |
|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
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 |
|---|---|---|
|
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." |
|
|
|
|
|
|
|
|
|
|
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 |
|---|---|---|
|
Example, "Level 2 Support, integration of help and training to the user community." |
|
|
|
|
|
|
|
|
|
|
Stakeholder Summary
Customer Name |
Role |
Interest/Need |
|---|---|---|
[Name] |
[Title or role] |
|
|
|
|
|
|
|
CBIIT Staff/Contractor Name |
Role |
Responsibilities |
|---|---|---|
<!-- /* Font Definitions */ @font-face Unknown macro: {font-family}
/* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal Unknown macro: {mso-style-unhide}
p.MsoBodyText, li.MsoBodyText, div.MsoBodyText Unknown macro: {mso-style-noshow}
p.InfoBlue, li.InfoBlue, div.InfoBlue Unknown macro: {mso-style-name}
span.BodyTextChar Unknown macro: {mso-style-name}
.MsoChpDefault Unknown macro: {mso-style-type}
@page Section1 Unknown macro: {size}
div.Section1 Unknown macro: {page}
--> |
|
|
Avinash Shanbhag |
|
|
|
|
|
Technical Environment
This product uses the following technical components which have been derived from the current NCICB Technology Stack
.
Client Interface |
|
Application Server |
[Example, Apache Tomcat 5.5.9] |
Database Server |
[Example, Oracle 9i] |
Operating System |
|
[Other] |
|
Product Dependencies
This release is dependent on the caCORE components or products documented in the [CORE Product Dependency Matrix].
[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 |
Iteration during which the item |
|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
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 |
Related documents: |
[Name and URL of each related document] |
Project Information
CBIIT Management |
Role |
Responsibilities |
|---|---|---|
[Name] |
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. |
Document Signoffs
CBIIT Management |
Role |
Stakeholder Management |
Role |
Sign off |
Date |
|---|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|