Page History
Scrollbar | ||
---|---|---|
|
...
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 1. Examples for Data Elements 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 |
Scrollbar | ||
---|---|---|
|