 |
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} | 12/18/2009 |
...
| | {color:#000000}{*}Requirement # unique id{*}{color} _<SemCon Ops Initiative>.<analysts initials><requirement number> |
...
_ \\ e.g. Init1dbw1 |
...
Init5pm21
\\ (eventually linked to Use Cases) | Init5pm21 \\ | | *Originator/Customer's Name*: |
...
| [Jyoti Pathak|mailto:Pathak.Jyotishman@mayo.edu] \- [forum |
...
post|https://cabig-kc.nci.nih.gov/Vocab/forums/viewtopic.php?f=43&t=117]\\ | | *Originator/Customer's Company*: |
...
| Mayo |
...
Clinic \\ | | *Summary of requirement pre-interview, by Reviewer: |
...
* | In another requirement, it is expressed that providing terminology mappings is needed. |
...
However, once a mapping is in place, there needs to be a way to validate that the mapping is correct. |
...
There should be a way for users to detect mappings that will cause semantic and logical inconsistencies. |
...
This functionality will be most useful for Information Modelers and Metadata Curators. |
...
\\ | | *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} |
