Init1bes4 - SIW Enhancement

Date: 

12/09/2009

Requirement # unique id <SemCon Ops Initiative>.<analysts initials><requirement number>
e.g. Init1dbw1
(eventually linked to Use Cases)

Init1bes4

Originator/Customer's Name:

Sharon Gaheen

Originator/Customer's Company:

SAIC

Stakeholder Community:
Enter appropriate category of stakeholder from Primary Stakeholders:  

• Software and Application designers and architects
• Software and Application engineers and developers
• Scientific and medical researchers
• Medical research protocol designers
• Clinical and scientific research data and metadata managers
• Clinicians
• Patients
• Medical research study participants
• Broader Stakeholders: caBIG® Community WS NIH projects and related commercial COTS vendors (caEHR, SDO's (HL7, CDISC); International Collaborators (e.g NCRI, cancerGrid, China), Government and regulatory bodies (FDA, CDC, ONC)
  (link to view SemConOps Stakeholders description).

Software and Application designers and architects
Software and Application engineers and developers

Summary of requirement pre-interview, by Reviewer:

Enhance the Semantic Integration Workbench to allow application developers to validate their model against an existing standard supported by caBIG (e.g. NPO, CDISC, HL7, etc.). This will assist in determining the models' level of support for the standard and verify touchpoints.  Different types of support for vocabulary, message and data element standards needed.

Recommended Next Step Enter one: Follow-up interview, Observe, Use Case Template (text), Use Case Model (formalized/UML diagram), Group Discussion, Prototype, Waiting Room

Follow-up interview

1

Hello, my name is NAME. I am calling you today because NCI and caBIG are working toward a new and improved version of the semantic infrastructure to better support integration scenarios.
Our first step was to organize requirements collected over the past year. Your organization has expressed a requirement/need for BRIEF STATEMENT OF USER REQUIREMENT.  This has been identified as potentially a critical component to support application/data and service integration, and we need more information in order to enable us to meet this requirement.
Do you have about 30 minutes to talk about this?

Yes.                                                                                                                    

2

Do you have any solution integration needs? If so, what are they? Have you envisioned new ways of interacting with existing or new parts of the semantic  infrastructure?
(prompt to elicit changes/new ways of using the infrastructure)

We would like to have a tool that will to assist in mapping the information model (class, attributes, and permissable values) to specific terminology/ontologies from one or many terminology services.  Unlike current SIW, which allows you to map model components against all NCI-T, works against one instance of EVS and provides only XMI as an output, we would like to be able to:
-  restrict the mapping to certain terminologies and/or different levels of hierarchies in terminology/ontology
-  use one more multiple instances of terminology services available
-  generate a table of the model component-matched concepts (in Excel and/or CSV formats)
This will identify gaps in the information model in terms of concept coverage (e.g. the concepts that are not covered by model but covered by ontology).  

We would like to have the tool (could be the same one with above) to assist in mapping the information model to the domain analysis models (DAMs) or platform independent models and or platform specific models from model repository (or knowledge repository).  This could assist in verifying compliance and/or identifying extensions to the DAM or other models.  Automating compliance/conformance process at information model level and simplying it through tooling  would be great.

3

Are there any business changes you are assuming we will be able to deal with? 
(prompt to elicit changes/new ways of using the infrastructure) 

Per ECCF,  the modelers should be able to verify conformance/compliance of PIMs/PSMs against DAMs (or PSMs against PIMs)

4

Are there any capabilities you are expecting to be available to support your needs? 
(prompt to elicit expectations/dependencies)

See 3.

5

Do you use any of the existing software/services? If so, what do you like or dislike about it?
(if related to existing capability)

SIW. It does not allow to specify certain terminology or level of terminology to map against.

6

If this requirement in met, what would be the benefits? If you do not have it, what would be the negative impact?
(prompt to elicit benefits/value - will help to prioritize)

The process of mapping a model to "right" concepts from "right" terminology/ontology will require cleaning to remove false-positives which is a labor-intensive task. 

Identifying the relationship between different levels of models PIM->DAM for verifying the conformance/compliance will be a mostly manual task.

7

If, for any reason, we were not able to create that solution, do you think there might be another way to solve this issue? Can you think of an alternative solution?
(prompt to elicit alternative solutions/workarounds)
(to be prepared by the Requirement Analyst)

Use current SIW to map a model against NCI-T concepts, do manual clean up of all concepts that does not belong to terminology/ontology of your interest.

8

Would you agree that we can summarize your requirement like this?
(Summarize one requirement in 2-3 lines and read back to interviewee for confirmation.)

Business Goal: To improve semantic annotations/concept mapings
Actor: Information Specialist (Modeler)
We would like to have a tool that will to assist in mapping the information model (class, attributes, and permissable values) to specific terminology/ontologies from one or many terminology services.  We would like to have the tool (could be the same one) to assist in mapping the information model to the domain analysis models (DAMs) or platform independent models and or platform specific models from model repository (or knowledge repository).

9

How important is this requirement to the interviewee? Required: Customer Priority/Annotationrement Analyst
(Provides concrete assessment of the relative importance for the requirements specification)

2. Should have

10

On a scale from 1 to 3 with 1 being "not satisfied" to 3 "completely satisfied", how would you rate your overall satisfaction with the product if this requirement was met?  (Relative rating/ranking of how satisfied or dissatisfied interviewee would be if this requirement were met/not met)

3. Completely satisfied 

11

Are there other requirements that you would like to share with us? I'd be more than happy to call you back another time, or if you have another 10 minutes, please share other issues you can think of.
(prompt to elicit any hidden - potentially higher priority requirements if they exist)

The performance of terminology services should support fast real-time access to reading full/partial subtrees of terminologies/ontologies.

The addition of new concepts to NCI-T could be streamlined by providing a service that allows submission of new concepts for harmonization/creation upon EVS curator review.

12

Who else should we talk to in order to elicit more information about this need?

Konrad Rockiki

For specific service enhancement or requirement from Forum entry:

13

Can you or someone else give me a step-by-step description of how you would describe the expected performance/behavior of the software in order for you to feel that your requirement is met? 
(Required: Fit Criterion - will help us create test cases and user acceptance criteria - to be prepared by the Requirement Analyst)

When an information model is mapped to a certain terminology and/or different levels of hierarchies in a terminology/ontology, all the concepts mapped should be from the target set.
When an information model is mapped to a DAM/PSM, all the common classes (entities) and attributes should be returned/provided.  

14

Forum Link:

https://cabig-kc.nci.nih.gov/Vocab/forums/viewtopic.php?f=40&t=104

15

URLs (optional):

16

References (optional):

VCDE:Meeting notes describing the requirements and motivation behind them as discussed in the interview.