 |
Page History
| Wiki Markup |
|---|
{scrollbar:icons=false}
h1. { |
| Page info |
|---|
...
|
Pre Interview:
Item | Information/Response |
|---|---|
Date: | 12/23/2009 |
...
Requirement # unique id <SemCon Ops Initiative>.<analysts |
...
initials><requirement |
...
number> |
...
|
...
Init1dbw1 |
...
| Init1bes10 |
Originator/Customer's |
...
Name |
...
: | Konrad Rockiki |
Originator/Customer's |
...
Company |
...
: |
...
NCI | |
Summary of requirement pre-interview, |
...
by |
...
Reviewer: |
...
Business |
...
Goal: |
...
Provide |
...
session-less, |
...
intitutive |
...
and |
...
direct |
...
links |
...
(URLs) |
...
to CDEs or modeling components. |
...
Metadata |
...
Specialist |
...
|
...
knowlegbase |
...
or |
...
model |
...
repository |
...
browser |
...
web |
...
pages |
...
provide |
...
a |
...
"Link" |
...
link |
...
that |
...
you |
...
can |
...
click |
...
on |
...
to |
...
easily |
...
get |
...
the |
...
link |
...
to |
...
the |
...
current |
...
page |
...
(see |
...
...
Maps |
...
for |
...
an |
...
example). |
...
This |
...
will |
...
allow |
...
easy |
...
sharing |
...
of |
...
the |
...
CDE/Model |
...
centric |
...
information |
...
and |
...
enhance |
...
access |
...
to |
...
CDEs/modeling |
...
components |
...
as |
...
they |
...
are |
...
registered |
...
in |
...
knowledgbase |
...
and/or |
...
model |
...
repositories. |
...
Recommended Next Step Enter one: Follow-up |
...
interview, |
...
Observe, |
...
Use |
...
Case |
...
Template |
...
(text), |
...
Use |
...
Case |
...
Model |
...
(formalized/UML |
...
diagram), |
...
Group |
...
Discussion, |
...
Prototype, |
...
Waiting |
...
Room |
...
Use |
...
Case |
...
Template |
...
(text) |
...
in |
...
Round |
...
2 |
...
with |
...
other |
...
Metadata |
...
Repository |
...
UI |
...
related |
...
functional |
...
requirements |
...
submitted. |
...
|
...
it has been to verify that linking mechanisms described at caDSR API with REST Examples Example 1 meets his requirements. So this functionality needs to be carried over to new knowlegbase or model repository browser. On the top of it he restated a " This functionality should be carried over to new knowlegbase or model repository browser(s). |
Post Interview - ongoing throughout development of use cases:
Item | Description | Information/Response |
|---|---|---|
Stakeholder Community: | Enter appropriate category of stakeholder from Primary Stakeholders:
|
|
Requirement Type (required) | Analyst's assessement of the most appropriate category/type of requirement (no need to ask interviewee):
| Functional |
ConOp Initiative(s) |
| Initiative 1 |
High Level Use Case Summary) | Please write a short descriptive narrative use case; the steps or activities in this use case are usually the things the user wants to accomplish with the system (user/actor's goals). | --- |
Use Case Linkage (required) | Which use case(s) is this requirement linked to? (should follow Use Case numbering scheme <SemCon Ops Initiative>.<analysts initials><requirement number>.<use case number>, for example Init1dbw1.1, Init1dbw1.2, Init2dbw2.1, 2.2, etc. | Use case Number(s): |
Conflicts / Dependencies(required) | Are there any conflicts with other requirements / use cases? | Yes OR No - If yes, what and why? |
Next Step (required) | After reviewing the results of the interview, the forum, and all other materials related to this requirement, the analyst should recommend the next step, then attach the Tiny Link (on the Info tab) for this page to the Master List table. | Enter one: Follow-up interview, Observe, Use Case Template (text), Use Case Model (formalized/UML diagram), Group Discussion, Prototype, Waiting Room |
| Wiki Markup |
|---|
has been to verify that linking mechanisms described at [caDSR:caDSR API with REST Examples] Example 1 meets his requirements. So this functionality needs to be carried over to new knowlegbase or model repository browser. On the top of it he restated a " This functionality should be carried over to new knowlegbase or model repository browser(s). \\
On the top Mr. Rockiki, restated the importance of "Link" link to get the link to the current page as described in "Summary of the requirement". |
h2. Post Interview - ongoing throughout development of use cases:
|| *Item* || *Description* || *Information*/Response ||
| *Stakeholder Community*: | Enter appropriate category of stakeholder from Primary Stakeholders:
* Software and Application designers and architects
* Software and Application engineers and developers
* Scientific and medical researchers
* Medical research protocol designers
* Clinical and scientific research data and metadata managers
* Clinicians
* Patients
* Medical research study participants
* Broader Stakeholders: caBIG® Community WS NIH projects and related commercial COTS vendors (caEHR, SDO's (HL7, CDISC); International Collaborators (e.g NCRI, cancerGrid, China), Government and regulatory bodies (FDA, CDC, ONC) \\
_[_(link to view SemConOps Stakeholders description_|Semantic Infrastructure Concept of Operations Stakeholders]__)._ \\ | \\
\\
Software and Application designers and architects \\
Software and Application engineers and developers \\
Clinical and scientific research data and metadata managers \\
\\
Actors: Primarily Information Technologist and Metadata Specialist but in fact any user that has access to knowledge or model repository browsers. |
| {color:#000000}{*}Requirement Type (required)*{color} | Analyst's assessement of the most appropriate category/type of requirement (_no need to ask interviewee)_: \\
* *Functional:* Fundamental or essential to the product - describes what the product has to do or what processing is needed \\
* *Nonfunctional:* properties the functions must have such as performance, usability, training or documentation \\
** *Project constraint:* schedule or budget constraints \\
** *Design constraint:* impose restrictions on how the product must be designed, such as conformant to ISO 11179, utilizes 21090 or is able to work on a particular type of device \\
** *Project driver:* business-related forces such as descriptions of stakeholders or purpose of the product/project \\
** *Project issue:* conditions that will contribute to the success or failure of the project | Functional |
| ConOp Initiative(s) \\
_Requirements Analyst/Business Analyst_ | * {color:#000000}Select most appropriate initiative: (click for descriptions) {color}
* [Initiative 1 - Distributed, federated metadata repositories and model repositories and operations|Semantic Infrastructure Concept of Operations Initiative 1 Repositories]
* [Initiative 2 - Automated generation of metadata from line-of-business artifacts|Semantic Infrastructure Concept of Operations Initiative 2 Automation]
* [Initiative 3 - Rules management and contracts support (behavioral semantics)|Semantic Infrastructure Concept of Operations Initiative 3 Rules]
* [Initiative 4 - Semantics support for W3C service oriented architecture resources|Semantic Infrastructure Concept of Operations Initiative 4 W3C]
* [Initiative 5 - HL7 CTS II/ OMG MIF compliant federated terminology services|Semantic Infrastructure Concept of Operations Initiative 5 Compliance]
* [Initiative 6 - Controlled biomedical terminology, ontology and metadata content|Semantic Infrastructure Concept of Operations Initiative 6 Controlled]
* [Initiative 7 - Assessment of semantic unification of compositional and derivational models|Semantic Infrastructure Concept of Operations Initiative 7 Assessment]
* [Initiative 8 - Other|Semantic Infrastructure Concept of Operations Initiative 8 Other] |Initiative 1 |
| {color:#000000}{*}High Level Use Case Summary)*{color} \\
_Requirements Analyst/Business Analyst_ \\ | {color:#000000}Please write a short descriptive narrative use case; the steps or activities in this use case are usually the things the user wants to accomplish with the system (user/actor's goals). {color} | \--\- |
| {color:#000000}{*}Use Case Linkage (required)*{color} \\
_Business Analyst_ \\ | {color:#000000}Which use case(s) is this requirement linked to? {color} (should follow Use Case numbering scheme _<SemCon Ops Initiative>.<analysts initials><requirement number>.<use case number>_, for example Init1dbw1.1, Init1dbw1.2, Init2dbw2.1, 2.2, etc. | Use case Number(s): |
| {color:#000000}{*}Conflicts / Dependencies(required)*{color} \\
_Requirements Analyst/ Business Analyst_ | {color:#000000}Are there any conflicts with other requirements / use cases? {color} \\ | Yes OR No - If yes, what and why? |
| {color:#000000}{*}Next Step (required)*{color} \\
_(Requirement Analyst / Business Analyst)_ \\ | After reviewing the results of the interview, the forum, and all other materials related to this requirement, the analyst should recommend the next step, then attach the Tiny Link (on the Info tab) for this page to the [Master List|Semantic Infrastructure Concept of Operations Initiatives - Requirements Master List] table. | Enter one: Follow-up interview, Observe, Use Case Template (text), Use Case Model (formalized/UML diagram), Group Discussion, Prototype, Waiting Room |
\\
{scrollbar:icons=false} |
