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/17/2009 |
Requirement # unique id <SemCon Ops Initiative>.<analysts initials><requirement number> |
Init1pm8 |
Originator/Customer's Name: |
|
Originator/Customer's Company: |
NCI |
Stakeholder Community:
|
|
Summary of requirement pre-interview, by Reviewer: |
The creation of metadata is currently a manual iterative process that involves many discussions, emails, and decisions between the Metadata Modeler and Metadata Curator. This process can occur in the timespan of days or weeks, and complex metadata can involve many modifications and loadings during that time. It is highly desirable that there is a mechanism to track these discussions, decisions, and changes over time. This will provide traceability, as well as a controlled way to review the history of changes for all artifacts involved in compatibility review. |
|
|
Post Interview - ongoing throughout development of use cases:
Item |
Description |
Information/Response |
---|---|---|
Requirement Type (required) |
Analyst's assessement of the most appropriate category/type of requirement (no need to ask interviewee):
|
|
ConOp Initiative(s) |
|
|
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 |