NIH | National Cancer Institute | NCI Wiki  

Error rendering macro 'rw-search'

null

Versions Compared

Old Version 5

changes.mady.by.user Warzel, Denise (NIH/NCI) [E]

Saved on

compared with

New Version 6

changes.mady.by.user Warzel, Denise (NIH/NCI) [E]

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Panel
titleTable of Contents
Table of Contents
MaxLevel4
MinLevel2

Active Period

The VCDE initial project is active from November 2009 - Feb 14, 2010

Problem Statement

There will be work beginning in 2010 to build infrastructure (software). VCDE WS has resources to spend on "Requirements elicitation in the community" that would help jump start the development early next year. This will be done in concert with the Vocabulary Knowledge Center. This effort should be seen as an ongoing activity by VCDE WS in 2010 and should support the overall "Software development processes" for caBIG in 2010 and beyond.

Objectives

This exercise would do at least three things:

• Access whether initiatives are addressing community needs
• Provide traceability from grass roots community needs to more top level initiatives in ConOps
• Provide input into ConOps to address further community needs

Deliverables

This group should produce:

Deliverable

Description

Date

Master List of Requirements mapped to Semantic Concept of Operations

An electronic resource that has requirements from community organized via the ConOps

Dec 2010

VKC Wiki with 150 newly fleshed out requirements

Review existing forum entries and translate them into requirements, will involve interviewing stakeholders

Jan 2010

Prioritized use cases with story boards

Requirements decomposed into Use Cases in a common format for a subset of the overall requirements (actor, success scenario, pre-post conditions)

Feb 2010

An electronic resource that can be expanded to support software development

Electronically recorded requirements and Use cases that can serve as a starting point for architects and business analysts to complete and translate into information models and more formal software artifacts. The documentation for each requirement should include:

a. Stakeholders
b. Formal requirements statement
c. Analyzing requirements to recommend next step

i. Use cases
ii. Prototyping

e. Specifications (via ECCF guidelines)
f. Etc, including Enabling a traceability matrix from completed software back to requirements

Feb 2010

Group Organization, Roles, and Responsibilities

Link to VKC Semantic Infrastructure Wiki - Requirements Elicitation Team

Process

The process the analysts are following is: 

...