 |
Page History
| Wiki Markup |
|---|
{scrollbar:icons=false}
h1. {page-info:title}
h2. Pre Interview:
|| Item || Information/Response ||
| {color:#000000}{*}Date{*}{color}{color:#000000}: {color} | 12/24/2009 |
| {color:#000000}{*}Requirement # unique id{*}{color} _<SemCon Ops Initiative>.<analysts initials><requirement number>_ \\
e.g. Init1dbw1 \\
(eventually linked to Use Cases) | Init1bes12 |
| *Originator/Customer's Name*: | Baris E. Suzek / SAEAF impact of compatibilty WG |
| *Originator/Customer's Company*: | Georgetown University |
| *Summary of requirement pre-interview, by Reviewer:* | Business Goal: Provide support to current caBIG services for them to be able to exchange data with services who consume/produce ISO21090 data type containing messages/XML documents(serialized objects), \\
Actor: Information Specialist \\
ISO21090 data types will start to be used by several services. Existing services have been using programming language specific data types (e.g . Java). To be able to exchange data with services who consume/produce ISO21090 data type containing messages/XML documents(serialized objects), existing projects would either be redeveloped to use/implement ISO21090 data type libraries for their programming language of choice \[VCDE:Alternative Solution\] OR are provided a mapping tool (and/or transformation service) that will transform native content with language specific data types to messages/XML documents containing ISO21090 data types. Possibly the mapping tool can produce a document as an input to a transformation service (describing how mapping should be done) or generate the code for service itself. \\
The libraries in first solution or mapping tool in the second solution are going to be used by Information Specialists (e.g. software developers). |
| *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 Template (text) |
\\
{scrollbar:icons=false} |
