Init1bes2 - Downloading all CDEs

Date: 

12/08/2009

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

Init1bes2

Originator/Customer's Name:

Tejas Dave and Sal Mungal

Originator/Customer's Company:

EkagraSoft and Duke University

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 engineers and developers

Summary of requirement pre-interview, by Reviewer:

Business Goal: To improve/streamline metadata reuse
Actor: Information Specialist (Modeler) 

Modelers need browsers that download selected (or all) search results (can be model components or DEs) in an XML format compliant with ISO 11179 schema. In a federated metadata repository structure this will involve communicating multiple instances of repositories.

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 with Tejas Dave to create Use Case Model

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 need browsers that interact with and search Knowledge and Model Repositories and support:

• Selection/configuration of repository instances to use: In a federated environment, user should be able to choose/configure which model and/or knowledge repository instances s/he wants to use.
  
• Search and discovery:  The browsers should allow developers/modeler to be able to discover/search the model or metadata components. The searches can be against:
     -Project names
     -Model package names
     -Description of model components (classes/attributes)
     -Semantic annotation (concepts)
     -Value domains/permissible values
     -Any text field that is provided for the model or associated metadata (free text search)
  
• Presentation of search results: The search results should: 
      -Allow selection of the search results (partial or complete) added in a shopping cart (basket) that can be exported in XMI (if needed transformed to classes for modeling tool consumption) and  XML compliant with ISO 11179 XSD.

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) 

No.

4

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

Knowledge/model repository and browser (or browsers) to support easy discovery/visulization and download of semantic metadata and/or model components.  The tools should support export formats that are widely used by modelers/developers.

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)

CDE Browser, UML Model Browser
Rigid /static in terms of view (not dynamic). So textual hard to understand. Performance. Comparison is primitive. Color coding is not user friendly. Discovering and reusing model components is not easy.

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)

Modelers/developers will be able to use browsers for modeling purposes; improving their models by identifying right components to use. Furthermore they will be able to use browser exports directly in modeling tools.

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)

One alternative solution, other then those involve more manual work for developers/modelers, will be facilitating direct interaction of modeling tools with model or knowledge repository and allowing all metadata to be pulled to modeling tool. One downside of this solution is the number of modeling tools and challenges around the selection of which one(s) to support. 

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.)

Provide functionality to download of selected or all CDEs in an XML format compliant with ISO 11179 schema. In a federated metadata repository structure this will involve communicating multiple instances of repositories.

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)

1. Must 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)

 2. Mostly 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)

See https://wiki.nci.nih.gov/x/NhBlAQ

12

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

N/A

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 I search for metadata, I should be able to find the correct model components in the first page of the returned results (good ranking) 

• In the results view, I should be able to select components from the search results (no upper boundaries) and  export selected components (classes or translated versions if they are CDE) in XMI format. This XMI format should be importable to a modeling tool.  Alternatively the export operation should generate an XML document compliant with ISO 11179 schema
  

14

Forum Link:

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

15

URLs (optional):

Links to pages or applications related to this requirement

16

References (optional):

Links to articles, papers or presentations related to this requirement