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/16/2009 |
Requirement # unique id <SemCon Ops Initiative>.<analysts initials><requirement number> |
Init1pm1 |
Originator/Customer's Name: |
|
Originator/Customer's Company: |
Mayo Clinic, ICR Interoperability Working Group |
Stakeholder Community:
|
|
Summary of requirement pre-interview, by Reviewer: |
The ICR Interoperability working group has summarized a set of tooling/development requirements that they believe will help developers meet their interoperability development goals. This set of requirements can (and should) be represented by a variety of use cases. It is also likely that these requirements significantly overlap many of the other requirements that are being gathered by other stakeholders. The following is a bulleted list summary of their requirements. Please refer back to the original post by Bob for a full list when modeling.
|
Recommended Next Step Enter one: Follow-up interview, Observe, Use Case Template (text), Use Case Model (formalized/UML diagram), Group Discussion, Prototype, Waiting Room |
|
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 |