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> |
|
Originator/Customer's Name: |
Init1pm4 |
Originator/Customer's Company: |
Tejas Dave (mailto: davet@mail.nih.gov): forum posting |
Stakeholder Community:
|
|
Summary of requirement pre-interview, by Reviewer: |
Using Natural Language Processing and integrating both EVS and caDSR APIs or similar future services, create a discovery service/tool which exposes data elements not based on the Names stored in caDSR but by using query in a concept search and pulling associated Administered Components from caDSR to match. This would enable construction of better search algorithms and serve as a potentially better discovery entry point for the user not familiar with the ISO 11179 nomenclature. The primary users that this would serve include both Cancer Researchers and Information Technologists. |
Recommended Next Step Enter one: Follow-up interview, Observe, Use Case Template (text), Use Case Model (formalized/UML diagram), Group Discussion, Prototype, Waiting Room |
Follow-up interview |
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 |