NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin
Wiki Markup
{scrollbar:icons=false}

h1. 

Protégé

...

1.4.1.1

...

(Patch)

...

Scope

...

Document

{:=
Panel
title
Contents
of
this
Page
} {
Table of Contents
:
minLevel
=
2
} {panel} {panel:title=Document Information} *Author:* Jason Lucas *Email:*
Panel
titleDocument Information

Author: Jason Lucas
Email: lucasjr@mail.nih.gov

*


Team:

*

EVS

*


Contract:

* *


Client:

*

NCI

CBIIT


National

Institutes

of

Heath


US

Department

of

Health

and

Human

Services {panel} || 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

Services

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.

...

Vision

...

and

...

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.

...

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)

Functional Bug Fixes

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

GForge number
(hyperlinked)

Brief description of bug

Status
(Approved or Proposed)

23517

ChAO is slow working with over 57000 changes

Approved

26154

Performance does not seem to be as robust as it was in UAT

Approved

26131

NIH user name is displayed in <Definition_Reviewer_Name> slot of DEFINITION

Approved

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)

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
(Approved or Proposed)

Example, "Level 2 Support, integration of help and training to the user community."

Stakeholder Summary

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 Government Lead

---

Sherri De Coronado

Contract Project Officer Contract Project Officer

---

Technical Environment

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

Component

Description

Client Interface

  • [EVS:Example, Internet Explorer 6.0 and above]
  • [EVS:Example, Mozilla v. 1.5.0.3 and above]

Application Server

[EVS:Example, Apache Tomcat 5.5.9]

Database Server

[EVS:Example, Oracle 9i]

Operating System

  • [EVS:Example, Windows 2000. XP, Vista]
  • [EVS:Example, Unix (Sun Solaris)]

[EVS:Other]

Product Dependencies

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."]

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

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

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:

[EVS: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.


Wiki Markup
 Proposed) \\ ||
| --- | --- | --- |


h2. Functional Bug Fixes

Each bug fix included in this release is described in detail below.
|| GForge number \\
(hyperlinked) || Brief description of bug \\ || Status \\
(Approved or Proposed) \\ ||
| [23517|https://gforge.nci.nih.gov/tracker/?group_id=174&atid=822&func=detail&aid=23517] | ChAO is slow working with over 57000 changes | Approved |
| [26154|https://gforge.nci.nih.gov/tracker/?group_id=174&atid=822&func=detail&aid=26154] | Performance does not seem to be as robust as it was in UAT | Approved |
| [26131|https://gforge.nci.nih.gov/tracker/?group_id=174&atid=822&func=detail&aid=26131] | NIH user name is displayed in <Definition_Reviewer_Name> slot of DEFINITION | Approved |


h2. 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) \\ ||
| --- | 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." | --- |


h2. 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." | --- |


h2. Stakeholder Summary

|| 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 Government Lead \\ | --\- |
| Sherri De Coronado \\ | Contract Project Officer Contract Project Officer | --\- |

h2. Technical Environment

This product uses the following technical components which have been derived from the current [NCICB Technology Stack|https://gforge.nci.nih.gov/docman/index.php?group_id=27&selected_doc_group_id=460&language_id=1].

|| Component || Description ||
| Client Interface \\ | * \[EVS:Example, Internet Explorer 6.0 and above\]
* \[EVS:Example, Mozilla v. 1.5.0.3 and above\] |
| Application Server | \[EVS:Example, Apache Tomcat 5.5.9\] |
| Database Server | \[EVS:Example, Oracle 9i\] |
| Operating System \\ | * \[EVS:Example, Windows 2000. XP, Vista\]
* \[EVS:Example, Unix (Sun Solaris)\] |
| \[EVS:Other\] | --- |

h2. Product Dependencies

This release is dependent on the caCORE components or products documented in the [CORE Product Dependency Matrix|https://wiki.nci.nih.gov/x/hIx8].

\[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."\]

h2. 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 \\ ||
| --- | --- | --- |

h2. Document History

|| 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|https://gforge.nci.nih.gov/projects/protegegui/] \\ |
| *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|https://wiki.nci.nih.gov/x/Cg5y] 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:* \\ | \[EVS:Name and URL of each related document\] \\ |

h2. 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. \\ |
\\
{scrollbar:icons=false}