Author: Jason Lucas |
Sign off | Date | Role | CBIIT or Stakeholder Organization |
|---|---|---|---|
--- | --- | --- | --- |
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) Protégé Release 1.3.0.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.
The objective of this release of Protégé 1.4.1.1 is to provide critical bug fixes that are necessary to maintain acceptable performance levels given the increased level of batch jobs observed in Protege 1.4.1.0.
This release will address the bugs described below found in UAT testing.
Each enhancement, modification or new feature is described in detail below.
GForge number | Brief description of functional requirement | Iteration |
|---|---|---|
— | — | — |
Each bug fix included in this release is described in detail below.
GForge number | Brief description of bug | Status |
|---|---|---|
ChAO is slow working with over 57000 changes | Approved | |
Performance does not seem to be as robust as it was in UAT | Approved | |
NIH user name is displayed in <Definition_Reviewer_Name> slot of DEFINITION | Approved |
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." | — |
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." | — |
Customer Name | Role | Interest/Need |
|---|---|---|
EVS Content Editors | Edit NCI Thesaurus and BiomedGT Content | Primary Users of Protege |
CBIIT Staff/Contractor Name | Role | Responsibilities |
|---|---|---|
Frank Hartel | EVS Product Manager | --- |
Gilberto Fragoso | Government Lead | --- |
Sherri De Coronado | Contract Project Officer | --- |
This product uses the following technical components which have been derived from the current NCICB Technology Stack.
Component | Description |
|---|---|
Client Interface |
|
Application Server | Example, Apache Tomcat 5.5.9 |
Database Server | Example, Oracle 9i |
Operating System |
|
[EVS:Other] | — |
This release is dependent on the caCORE components or products documented in the CORE Product Dependency Matrix.
[EVS: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."]
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 |
|---|---|---|
— | — | — |
Item | Information |
|---|---|
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: | EVS Collaborative Development Tools Docs archive, Files archive; Trackers |
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 |
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. |