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> |
Init1pm12 |
Originator/Customer's Name: |
|
Originator/Customer's Company: |
San Diego Supercomputer Center |
Summary of requirement pre-interview, by Reviewer: |
It appears that the current construct of the CDE carries too many dependencies that make it hard to adopt (by parties other than the author). For this, and other reasons, there is a proliferation of difficult to reuse CDEs. One possible solution could be by expressing the ValueDomain as either XSD, RDF or OWL, then it would be much easier to reuse existing CDEs since one apply "runtime semantics" controlled by the adopters. Another option is to distribute the metadata repositories across organizations, allowing Information Technologists to create and annotate their own metadata. This issue has been discussed at length, and attached are some supporting documents. |
Recommended Next Step Enter one: Follow-up interview, Observe, Use Case Template (text), Use Case Model (formalized/UML diagram), Group Discussion, Prototype, Waiting Room |
Followup interview |
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 |