Instructions
Follow the script instructions and record the information in the designated table cells. You may wish to make notes below the questions.
Pre Interview:
Item |
Information/Response |
---|---|
Date: |
12/18/2009 |
Requirement # unique id <SemCon Ops Initiative>.<analysts initials><requirement number> |
Init5pm22 |
Originator/Customer's Name: |
|
Originator/Customer's Company: |
San Diego Supercomputer Center |
Summary of requirement pre-interview, by Reviewer: |
Currently the NCI standard source for terminology is exclusively NCI Thesaurus. However, EVS has other terminologies available and will be accessing even more in the future. A mechanism needs to be developed to deal with overlap of terms from multiple sources. The caveat being that the same term in different sources may or may not be identical in meaning. This will aid Information Modelers, Metadata Curators, and Terminologists. |
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 Caste Diagram |
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):
|
|
ConOp Initiative(s) |
|
|
High Level Use Case Summary) |
Please write a short descriptive narrative use case. |
|
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 |