Page History
Wiki Markup |
---|
{scrollbar:icons=false}
h1. { |
Scrollbar | ||
---|---|---|
|
page-info |
...
Pre Interview:
...
Item
...
Information/Response
...
Date:Â
:title} h2. Pre Interview: || Item || Information/Response || | {color:#000000}{*}Date{*}{color}{color:#000000}: {color} | 01/07/2010 |
...
| | {color:#000000}{*}Requirement # unique id{*}{color} _<SemCon Ops Initiative>.<analysts initials><requirement number> |
...
_ \\ e.g. Init1dbw1 |
...
Init6SD12
\\ (eventually linked to Use Cases) | Init6SD12 | | *Originator/Customer's Name*: |
...
| Brian |
...
Davis | | *Originator/Customer's Company*: |
...
| 3rd |
...
Millenium \\ | | *Summary of requirement pre-interview, by Reviewer: |
...
* | Actor: The actor is a cancer researcher who is looking for data of his interest and not sure how that entity is modeled as, in the realm of the Grid. |
...
\\ Business goal: To make data search more |
...
Recommended Next Step Enter one: Follow-up interview, Observe, Use Case Template (text), Use Case Model (formalized/UML diagram), Group Discussion, Prototype, Waiting Room
...
Use case development
...
inclusive \\
\\
To achieve seamless interoperability between various tools, the tools need to understand an entity irrespective of whether that entity is modeled as object class, property or value domain. \\ |
| *Recommended Next Step* Enter one: Follow-up interview, Observe, Use Case Template (text), Use Case Model (formalized/UML diagram), Group Discussion, Prototype, Waiting Room | Use case development \\ |
\\
{scrollbar:icons=false} |