Page History
Scrollbar | ||
---|---|---|
|
...
Page info |
---|
...
|
Pre Interview:
Item | Information/Response |
---|---|
Date: | 12/16/2009 |
...
Requirement # unique id <SemCon Ops Initiative>.<analysts |
...
initials><requirement |
...
number> |
...
|
...
Init1dbw1 |
...
| 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 |
|
Scrollbar | ||
---|---|---|
|