Init1hm2 - Reuse or create new data elements at runtime

Date: 

12/09/2009

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

Init1hm2

Originator/Customer's Name:

Juli Klemm                                                                                         

Originator/Customer's Company:

NCI

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
• Scientific and medical researchers

Summary of requirement pre-interview, by Reviewer:

Dynamic extensions are used to dynamically add additional data elements to an information model that is already underlying an application.  It is highly desirable that these new data elements are publishable to the metadata repository in a dynamic way that does not require much manual information (e.g. UML modeling) from the application owner.

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)

The possible solutions for the dynamic extension are as follows:

• Create the federated metadata repository (e.g., allow user to create new data elements, attributes
• Create the federated terminology services (e.g., allow user to create new terms or add its own definitions)
• Browsers to query the federated metadata repository and terminology on the Grid
• Tools to semantic annotate data using concepts, attributes, CDEs created through dynamic extension
  

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) 

Focusing more to developing browsers for reusing and creating metadata elements

• better support metadata search across federated metadata repositories on the grid (e.g., find data elements created by others)
• better support concepts search across federated terminology services on the grid

4

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

Federated metadata repository browsers

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)

No.

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)

Currently, we can not share data that are created through the dynamic extension on the Grid. If this requirement in met, users can query and retrieve real time data on the Grid.

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)

No.

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

Create federated metadata/terminology repository.
Browsers that interact with federated metadata/terminology 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)

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)

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)

(If yes, take notes to use in on a new page with this template; if time not available now, try to make appointment for another call.)

12

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

No

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

Create federated metadata repository: create new data elements through dynamic extension. The federated CDE browser will allow users to query these CDEs on the grid
Create federated terminology services: create new concepts or add definitions to existing concepts in a local terminology. Register the local terminology in the LexEVS. Tools to allow users to annotate their information model using concepts from the local terminologies. 

14

Forum Link:

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

15

URLs (optional):

related to the ICRi use cases 1,2,3,4,5,6,7,8,10,12,13, and 15.
caB2B Overview ppt

16

References (optional):

Links to articles, papers or presentations related to this requirement