Init6SD10-Clarification of the model madness, please

Date: 

01/05/2010

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

Init6SD10

Originator/Customer's Name:

  Hannes Neidner                                                                                 

Originator/Customer's Company:

SanDiego Supercomputer Center UCSD

Summary of requirement pre-interview, by Reviewer:

The Actor is a Cancer researcher purely from a domain side wanting to get acquainted with various caBIG tools models.

Business goal is to make documentation supporting the model as informative as possible to a layman.


Requirement:
1)When submitting a new model or modifying an existing one it should be accompanied with a document/s which, in a very easy to understand language explain the purpose, utility, constraints, the relationships, instructions to use, future scope and path and outlook for each of the models;

2) There needs to be a crystallized definition of each model type (Domain Model, Domain Object Model, Domain Information Model, Domain Analysis Model, Business Architecture Model) how they are created and how they relate to one another

3) There needs to be traceability of individual specifications /requirements throughout the design/specification/modeling process: starting from abstract (implicit or explicit)requirements formulation to the concrete implementation.

4) More clarity is needed on the question of UML versus OWL as
 choice for the formal model representation

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

Group discussion

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

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

High Level Use Case Summary)
Requirements Analyst/Business Analyst

Please write a short descriptive narrative use case. 

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