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

• 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

Requirement Type (required)

Analyst's assessement of the most appropriate category/type of requirement (no need to ask interviewee):

• Functional: Fundamental or essential to the product - describes what the product has to do or what processing is needed
  
• Nonfunctional: properties the functions must have such as performance, usability, training or documentation
  
  • Project constraint: schedule or budget constraints
    
  • Design constraint: impose restrictions on how the product must be designed, such as conformant to ISO 11179, utilizes 21090 or is able to work on a particular type of device
    
  • Project driver: business-related forces such as descriptions of stakeholders or purpose of the product/project
    
  • Project issue: conditions that will contribute to the success or failure of the project

ConOp Initiative(s)
Requirements Analyst/Business Analyst

• Select most appropriate initiative: (click for descriptions) 
• Initiative 1 - Distributed, federated metadata repositories and model repositories and operations
• Initiative 2 - Automated generation of metadata from line-of-business artifacts
• Initiative 3 - Rules management and contracts support (behavioral semantics)
• Initiative 4 - Semantics support for W3C service oriented architecture resources
• Initiative 5 - HL7 CTS II/ OMG MIF compliant federated terminology services
• Initiative 6 - Controlled biomedical terminology, ontology and metadata content
• Initiative 7 - Assessment of semantic unification of compositional and derivational models
• Initiative 8 - Other

Use Case Linkage (required)
Business Analyst

Which use case(s) is this requirement linked to?  (should follow Use Case numbering scheme <SemCon Ops Initiative>.<analysts initials><requirement number>.<use case number>, for example Init1dbw1.1, Init1dbw1.2, Init2dbw2.1, 2.2, etc.

Use case Number(s):

Conflicts / Dependencies(required)
Requirements Analyst/ Business Analyst

Are there any conflicts with other requirements / use cases? 

Yes OR No - If yes, what and why?

Next Step (required)
(Requirement Analyst / Business Analyst)

After reviewing the results of the interview, the forum, and all other materials related to this requirement, the analyst should recommend the next step, then attach the Tiny Link (on the Info tab) for this page to the Master List table.

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