Page History

page-info

:title}

h2. Pre Interview:

|| Item || Information/Response ||
| {color:#000000}{*}Date{*}{color}{color:#000000}: {color} | 01/05/2010

 |
| {color:#000000}{*}Requirement # unique id{*}{color} _<SemCon Ops Initiative>.<analysts initials><requirement number>

_ \\
e.g. Init1dbw1

 \\
(eventually linked to Use Cases) | Init6SD10 |
| *Originator/Customer's Name*:

 | Hannes

 Neidner |
| *Originator/Customer's Company*:

 | SanDiego Supercomputer Center

 UCSD \\ |
| *Summary of requirement pre-interview, by Reviewer:

* | The Actor is a Cancer researcher purely from a domain side wanting to get acquainted with various caBIG tools models.

 \\
\\
Business goal is to make documentation supporting the model as informative as possible to a layman. \\  \\
\\
Requirement: \\
1)When submitting a new model or modifying an existing one it should be accompanied with a document/s which, in a very easy to understand language explain the purpose, utility, constraints, the relationships, instructions to use, future scope and path and outlook for each of the models; \\
\\
2) There needs to be a crystallized definition of each model type (Domain Model, Domain Object Model, Domain Information Model, Domain Analysis Model, Business Architecture Model) how they are created and how they relate to one another \\
\\
3) There needs to be traceability of individual specifications /requirements throughout the design/specification/modeling process: starting from abstract (implicit or explicit)requirements formulation to the concrete implementation. \\
\\
4) More clarity is needed on the question of UML versus OWL as \\
 choice for the formal model representation \\
\\ |
| *Recommended Next Step* Enter one: Follow-up interview, Observe, Use Case Template (text), Use Case Model (formalized/UML diagram), Group Discussion, Prototype, Waiting Room | Group discussion \\ |
\\
{scrollbar:icons=false}