SI Conop Initiatives Requirements Master List

<?xml version="1.0" encoding="utf-8"?>
<html>
_NOTOC_
:VKC_Twitter

SI Init Sidebar

<center>Please note - This page outlines SI Elicitation from 2009 and Early 2010. Please see the Semantic Infrastructure V2.0 Roadmap for details about the evolution of CBIIT Semantic Infrastructure</center>

This page is the master list for organizing Semantic Infrastructure V1 stakeholder business requirements that may impact the new CBIIT semantic infrastructure V2 Roadmap. The SI V2 Roadmap will replace the 2009 SI V1 Concept of Operations. Any requests which do not fit into the seven initiatives previously described by the Semantic Infrastructure Concept Of Operations were also documented. After collecting more details on all the requirements, a UML Model depecting the high level technical service requirements and their decomposed use cases was developed (see link below). If you have a requirement for the existing infrastructure that is not listed here, please contact Denise Warzel, if it pertains to SI V2, Dave Hau, or if it pertains to semantic infrastructure requirements for caEHR, John Speakman.

[UML Model of Use Cases by Requirement Level (pdf version)|https
//wiki.nci.nih.gov/download/attachments/20285848/10_06_17_UMLofREQUIREMENTS.pdf]

[UML Model of Use Cases by Requirement Level (html version)|http
//informatics.mayo.edu/UML_Model_Of_Use_Cases/index.html]

[A roadmap for requirement analysis for ECCF traceability]

;[SI Service Categories derived from initial use case analysis]

;[Link to Supplemental Requirements Input page|https
//wiki.nci.nih.gov/x/mIk1AQ]

[Requirements Elicitation Stakeholder Participants]

;[Requirements Elicitation Progression]

;[Explanation of Master List columns]

Unknown macro: {paneltitle=|borderStyle=dashed|borderColor=#ccc|bgColor=#fff}

Topic	Infrastructure Service	Type	Submitter	Req Statement	'''Interview Analyst	'''Use Case Analyst	Phase I Target	'''Requirement Link(s)	Notes
Knowledge Management

Enterprise Vocabulary | Manage & Create Model Metadata

Use Cases - Init1bes1.pm1

Integrated tools for model loading, traceability

Knowledge Management

Manage & Create Model Metadata

Ashwin Mathur

Baris

n/a

<|-- | A - Use Case Template (text) in Round 2 with other Metadata Repository UI related functional requirements submitted.

C - Initial analysis

C - Use Cases --> | Formal Requirements Statement | Requirements Input - Init1bes5 | Portal that integrates tools |

Knowledge Management

Manage & Create Model Metadata

Sal Mungal

Baris

<|-- | W - Use Case Template (text) in Round 4 with other Metadata Repository UI related functional requirements submitted.

C - Interview Sal Mungal

C - Decompose forum and other materials --> | Formal Requirements Statement | Requirements Input - Init1bes6 | makes easier to use tools in a workflow, expose more metadata |

ICR-caIntegrator2

Knowledge Management

Enterprise Vocabulary | Align Models | Juli Klemm

Anand Basu | Shantanu | n/a | Patrick

<|-- | I - Prepare Use Cases

C - Conduct initial analysis

C - Use Cases--> | Formal Requirement Statement and Draft prioritized use cases | Requirements Statement - Init1pm24

Use Cases - Init1pm24.pm15 | Related to dynamic extensions |

Knowledge Management

Manage & Create Model Metadata

Sal Mungal

Baris

<|-- | W - Use Case Template (text) in Round 4 with other Metadata Repository UI related functional requirements submitted.

C - Interview Sal Mungal

C - Decompose forum and other materials--> | Formal Requirement Statement and Draft list of prioritized use cases | Requirements Input - Init1bes7 | Adjustable UI for the user to customize views of metadata |

Knowledge Management

Manage & Create Model Metadata

Bilal Elahi

Patrick

n/a

Shantanu

<|-- | A - Use Case Template in Round 2

C-Formal Requirements Statement --> | Formal Requirements Statement; Develop summary list of use cases (Most common queries) | Requirements Input - Init1pm2

Easier to use Browser - User Centered Design details attached

Knowledge Management	Manage & Create Model Metadata	Robert Freimuth	Hua	Hua	Patrick	Formal Requirements Statement and Use Case Summary	Requirements Input - Init1hm1	Make it easier to reuse/map CDEs to models, improve matching algorithms
Knowledge Management	Manage & Create Model Metadata	Sal Mungal	Baris	Baris	Patrick

<|-- | W - Use Case Template (text) in Round 4 with other Metadata Repository UI related functional requirements submitted.

C - Interview Sal Mungal

C - Decompose forum and other materials --> | Formal Requirements Statement | Requirements Input - Init1bes6 | Display usage information in browsers, use this to organize search results |

Knowledge Management

Knowledge Management

Enterprise Vocabulary | Manage & Create Model Metadata

Knowledge Management

Enterprise Vocabulary | Manage & Create Model Metadata

Align Models | Brian Davis
Tommie Curtis | Baris | n/a | Patrick

<|-- | A - Use Case Development

C - Complete Questionnaire to include summary/formal Requirements Statement

C - Use Cases --> | Formal Requirements Statement | Requirements Input - Init1bes9

Use Case - Init1bes9.pm11 | leverage semantics of existing content to find/reuse content from different sources to create Forms |

Knowledge Management

<|-- | W - Use Case Template (text) in Round 4 with other Metadata Repository UI related functional requirements submitted.

C - Follow up Interview --> | Formal Requirements Statement | Requirements Input - Init1hm4 | leverage semantic metadata and model relationship to find/reuse content |

Knowledge Management

Knowledge Management

Manage & Create Model Metadata

Hannes Niedner

Baris

Patrick

<|-- | WR - Interview Hanne Niedner in Round 4

C - Decompose forum and other materials -> | Formal Requirements Statement | Requirements Input - Init1bes8 | Need to be able to register java classes that are comprised of CDEs that are associated with different Object Classes - remove the one domain class<>one object class limitation for model registration |

Knowledge Management

Manage & Create Model Metadata

Tejas Dave

Baris

Patrick

<|-- | A - Review Use Cases

C - Interview Tejas Dave

C - Decompose forum and other materials

C - Use Cases --> | Formal Requirements Statement and Use Case Summary | Requirements Input - Init1bes1
Use Cases - Init1bes1.pm9 | Ability to compare Object Classes, Models, etc. |

Validation

Enterprise Vocabulary | part of Manage & Create Metadata

Align Models | Sharon Gaheen

Sal Mungal | Baris | Baris | Patrick

<|-- | W - Add more use cases for new requirement

A - Review Use Cases

C - Interview Sharon Gaheen

C - Decompose forum and other materials

C - Use Cases --> | Formal Requirements Statement and Use Case Summary | Requirements Input - Init1bes4

Requirements Input - Init3bes20

Use Cases - Init1bes4.pm10

Circular References | This set of requirements and use cases is for the ability to validate models against standard models and best practices, such as checking models for cyclic references. It may or may not end up as an SIW enhancement. |

Knowledge Management

Visualize Models

Denise Warzel

Baris

<|-- | WR - Waiting room since it overlaps with an existing 'Presentation of search results' requirement for which use cases will be developed.

C - Decompose forum and other materials --> | Requirements Input - Init1bes11 | Improve browsing of registered models with visualization tools |

Knowledge Management

Manage & Create Model Metadata

Ashwin Mathur

Patrick

n/a

Shantanu

<|-- | A - Review of Use Cases

C - Questionnaire --> | Formal Requirements Statement and 2-4 Detailed use cases | Requirements Input - Init1pm5

Use Cases - Init1pm5.u | Models |

Knowledge Management

Manage & Create Model Metadata

Ashwin Mathur

Patrick

n/a

Shantanu

<|-- | A - Use Case Model in Round 2

C - Questionnaire --> | Formal Requirements Statement and 2-4 Use Cases | Requirements Input - Init1pm6

Use Cases - Init1SDpm6.100.u | Models |

Knowledge Management

Manage & Create Model Metadata

Bilal Elahi

Patrick

n/a

Shantanu

<|-- | A - Use Case Model in Round 2, coordinate with Automate Loading process (Patrick)

C - Formal Requirement Statement --> | Formal Requirements Statement and 2-4 Use Cases | Requirements Input - Init1pm7

Use Cases - Init1pm7.SD200.u | support end-to-end annotation and loading of models, traceability; the need to submit a model to be loaded by someone else may go away; this could be a short term solution, depending on LOE to implement |

Knowledge Management

Environmental Vocabulary | Manage & Create Model Metadata

Align Models | Denise Warzel | Patrick | n/a | Shantanu

<|-- | A - Use Case Template in Round 2

C - Questionnaire --> | Formal Requirements Statement; Summary Use Cases | Requirements Input - Init1pm8

Better support for annotating and loading models

Enterprise Vocabulary

Align Models

Elizabeth Hahn-Dantona

Hua

<|-- | W - Use Case template

C - Interview --> | Formal Requirements Statement | Requirements Input - Init1hm5 | Make all VCDE approved terminologies available for model annotations |

Knowledge Management

Manage & Create Model Metadata

Sal Mungal

Patrick

n/a

Patrick

<|-- | C - Develop Use Cases

C - Use Cases --> | Formal Requirements Statement and 2-4 Summary Use Cases | Requirements Input - Init1pm9

Use Cases - Init1pm9.pm16 - Automate

Use Cases - Init1pm7.SD200-Automate caDSR model submission

Use Cases - Otherhm2.pm13 - Conditional CDEs | Automate creating CDEs from skip patterns of Forms, workflow to automate annotation and loading of Models |

Knowledge Management

Manage & Create Model Metadata

Denise Warzel
Dianne Reeves

Baris

<|-- | W - Use Case Template (text)

C - Interview Dianne Reeves

C - Decomposed forum and other materials --> | Formal Requirements Statement | Requirements Input - Init1bes13 | Models |

Knowledge Management	Manage & Create Model Metadata	Denise Warzel	Shantanu	n/a	Summary Requirements statement	Requirements Input - Init1sd15	Provide ability to generate customized reports from metadata content
Knowledge Management	Manage & Create Model Metadata	Sal Mungal Tejas Dave	Baris	Baris

<|-- | WR - Combine with Customizable Download; Develop Use Case Template (text) in Round 4

C - Interview Tejas Dave

C - Decompose forum and other materials --> | Formal Requirements Statement | Requirements Input - Init1bes2 | Allow federation of content, current limitation of what can be extracted/easily downloaded |

Knowledge Management

Manage & Create Model Metadata

Bilal Elahi

Baris

n/a

<|-- | WR - User Centric Design materials available for development of use cases

C - Decompose forum into requirements statement --> | Requirements Input - Init1bes3(UCD) | allow users to search for and customize download, not just CDEs |

Knowledge Management

Manage & Create Model Metadata

Konrad Rokicki

Baris

n/a

Patrick

<|-- | C - Use Case Template (text) in Round 2 with other Metadata Repository UI related functional requirements submitted.

C - Contact Konrad Rockiki for clarification of requirement and potential overlap with existing CDE Browser functionality

C - Decompose forum and other materials

C - Use Cases --> | Formal Requirement Statement and Use Case Summary | Requirements Input - Init1bes10

Use Cases - Init1bes10.pm17 | This feature already exists, clarify use cases to ensure that all are supported

Retrieving Content for CDEs |

Knowledge Management

Manage & Create Model Metadata

Tejas Dave

Patrick

n/a

Patrick

<|-- | C - Use Case Template (text) and document CRUD services

C - Formal Requirements Statement

C - Use Cases --> | Formal Requirements Statement | Requirements Input - Init1pm10

Use Cases - Init1pm10.pm20 | Examples of High Level Services for retrieving MDR content, caDSR Services Wiki |

Knowledge Management

Manage & Create Model Metadata

Juli Klemm

Hua

Patrick

<|-- | C - Use cases Template (Text) in Round two

C - Interview Rakesh Nagarajan and Mukesh Sharma

C - Use Cases --> | Formal Requirement Statement and Use Cases Summary (List) | Requirements Input - Init1hm2

Use Cases - Init1hm2.pm6 | related to metadata for caB2B and Dynamic Extensions Services |

Knowledge Management

Transformation | Manage & Create Model Metadata

Search Models | Todd Parnell | Shantanu | n/a | Patrick

<|-- | A - Validate and prioritize use cases, identify missing/gaps, develop next level use case model (text step-by-step for success scenario)

C - Decomposed forum and other materials

C - Use Cases --> | Decomposed forum and other materials | Requirements Input - Init1sd2

Use Cases - INIT1SD2.pm7 | caB2B use cases for improving metadata for services |

Knowledge Management

Enterprise Vocabulary | Manage & Create Model Metadata

Align Models | Robert Freimuth | Shantanu |

<|-- | C - complete Questionnaire Init1SD20, develop formal requirement statement and 2-4 Summary level use cases

C - Decomposed forum and other materials --> | Formal Requirements Statement | Requirements Input - Init1sd20 | provide capabilities to build cde-cde mapping and metadata mapping for use in services |

Knowledge Management

Enterprise Vocabulary | Manage & Create Model Metadata

Knowledge Management / Transformation

Enterprise Vocabulary | Manage & Create Model Metadata

Align Models | Frank Hartel | Patrick | Patrick

<|-- | A - Review Use Cases

I - Interview Smita

C - Use Case Template --> | Formal Requirements statement; Summary Use Cases | Requirements Input - Init1pm11

Use Cases - Init1pm11.pm3 | Services |

MD Anderson Federated Registries

Knowledge Management

Enterprise Vocabulary | Manage & Create Model Metadata

cancerGrid Federated Registries	Constraint	Supplement Specification Req. for Federated MDRs	Steve Harris	Formal Requirements Statement; Summary of Services Use Cases (see Michael Riben)	caBIG Stakeholders - 11179 and Forms metadata exchange
Medidata	Knowledge Management

Enterprise Vocabulary | Manage & Create Model Metadata

Align Models | Christo Andonyadis | Patrick | n/a | Patrick

<|-- | C - Use Case Development based on Recent Usage Scenarios

C - Use Cases --> | Requirements Input - Init1pm13

Use Cases - Init1pm13.pm14 | Commercial COTS vendors - Form and CDE Services - CTMS WS |

Knowledge Management

Enterprise Vocabulary
Transformation

Manage & Create Model Metadata

Align Models | Sal Mungal | Denise | Mohamed Patrick

<|-- | A - Interview Rakesh to clarify use cases described by Avinash

C - Formal Requirement Statement

C - Use Cases --> | Formal Requirements Statement | Requirements Input - Init1dbw6

Use Cases - Init1dbw6.pm8 |

Metadata repositories should contain corresponding metadata	Knowledge Management	Manage & Create Model Metadata	Baris Suzek	Formal Requirements Statement	Guide to Mentors
Policies/protocols that will ensure concurrent registration of model/metadata	Knowledge Management /Transformation	Manage & Create Model Metadata	Baris Suzek	Formal Requirements Statement	Guide to Mentors
Knowledge Management /Transformation	Manage & Create Model Metadata	Denise Warzel	Patrick	Baris	Patrick

<|-- | A - Review/Harmonize Use Cases with ISO 210909

C - Use Cases --> | Formal Requirements Statement; Summary Use Cases | Requirements Input - Init1pm14

Use Cases - Init1pm16.pm4 (ISO 21090) | Services for data integration |

Mapping/transformation support for ISO21090 data types

Knowledge Management /Transformation

Enterprise Vocabulary | Manage & Create Model Metadata

[ Use Cases - Init1pm16.pm4 (ISO 21090)|https://wiki.nci.nih.gov/x/IQhyAQ] | Services for data integration |

Constraint	Supplementary Specificagtion - use of .NET tools	Tracy Safran	Patrick	Formal Requirements Statement	Requirements Input - Init1pm15	Services
Knowledge Management

Enterprise Vocabulary | Manage & Create Model Metadata

Align Models | Frank Hartel | Patrick | See 21090 Datatype Support | Requirements Input - Init1pm16 (ISO 21090)

[ Use Cases - Init1pm16.u (ISO 21090)|https://wiki.nci.nih.gov/x/IQhyAQ] | Services for data integration |

21090 Datatype Support

Knowledge Management

Enterprise Vocabulary | Manage & Create Model Metadata

Align Models | Christo Andonyadis | Patrick |

<|-- | I - Interview Avinash, Christo and Todd Parnell

C - Use Case Template

C - Decompose forum and other materials

P - Interview/Review with Charlie Mead --> | Formal Requirements Statement, Summary Use Cases | Requirements Input - Init1pm16 (ISO 21090)

[ Use Cases - Init1pm16.u (ISO 21090)|https://wiki.nci.nih.gov/x/IQhyAQ] | Services for data integration

caBIG Community - (Avinash Shanbhag CBITT Leader) |

Knowledge Management

Enterprise Vocabulary | Manage & Create Model Metadata

Knowledge Management

Enterprise Vocabulary | Manage & Create Model Metadata

HL7 MDR Requirements

Knowledge Management

Enterprise Vocabulary | Manage & Create Model Metadata

Knowledge Management

Enterprise Vocabulary | Manage & Create Model Metadata

Vocabulary Management

<|-- | W - Use case development

C - Follow-up via email to refine requirements (who is the actor/business goal/success scenario)

C - Decompose into questionnaire

C - Use Cases --> | Formal Requirements Statement, Summary Use Cases | Requirements Input - Init1hm6

Use Cases - Init1hm6.pm18 |

Knowledge Management

Enterprise Vocabulary | Manage & Create Model Metadata

Align Models | Brian Davis | Shantanu | n/a | Shantanu

<|-- | A - Review/Harmonize with ISO 21090 Use Cases

C - Decompose forum and other materials --> | Formal Requirements Statement | Requirements Input - Init1sd5

Use Cases - Init1pm16.u (ISO 21090) | Services for data integration |

Knowledge Management

Enterprise Vocabulary | Manage & Create Model Metadata

Use Cases - Init1pm16.u (ISO 21090) | Services for data integration |

[ Validation of harmonization

https://cabig-kc.nci.nih.gov/Vocab/forums/viewtopic.php]

Knowledge Management

Enterprise Vocabulary | Manage & Create Model Metadata

Align Models | Sal Mungal | Formal Requirements Statement | Assertation test |

Semantic web vs grid tools	Not Defined	Sal Mungal	Formal Requirements Statement
Usage Tracking/Statistics for Semantic Infrastructure Services	Constraint	In supplementary specification Model Admin. Requirement	Ken Buetow
Knowledge Management

Enterprise Vocabulary | Manage & Create Model Metadata

Knowledge Management

Enterprise Vocabulary | Manage & Create Model Metadata

Conformance Profiles

Knowledge Management

Manage & Create Model Metadata

Frank Hartel interview:

John Koisch

Paul Boyes | Baris | Baris |

<|-- | I - Record 4-5 new requirements that resulted from interview

C - Interview w/Koish and Paul Boyes in Round 1 --> | Formal Requirements Statement and summary of high level use cases (actor, bus goal, success scenario) | Requirements Input - Init3bes14 | caBIG Community - Support for ECCF Use Cases
Arch WS Presentation |

Conformance Profile Browser

Knowledge Management

Manage & Create Model Metadata

John Koisch

Paul Boyes

Linda Schmandt | Baris |

<|-- | W - Follow-up interview for use case development

C - Formal Requirement Statement --> | Requirements Input - Init3bes16 | caBIG Community - Support for ECCF Use Cases |

Conformance Profile Registry (or Repository) and Format

Knowledge Management

Manage & Create Model Metadata

John Koisch

Paul Boyes | Baris |

<|-- | W - Follow-up interview for use case development

C - Formal Requirement Statement --> | Requirements Input - Init3bes17 | caBIG Community - Support for ECCF Use Cases |

Conformance Profile Editor

Knowledge Management

Manage & Create Model Metadata

John Koisch

Paul Boyes | Baris |

<|-- | W - Follow-up interview for use case development

C - Formal Requirement Statement --> | Requirements Input - Init3bes18 | caBIG Community - Support for ECCF Use Cases |

Testing conformance with conformance profiles

Knowledge Management

Manage & Create Model Metadata

John Koisch

Paul Boyes

Linda Schmandt | Baris |

<|-- | W - Follow-up interview for use case development

C - Formal Requirement Statement --> | Requirements Input - Init3bes19 | caBIG Community - Support for ECCF Use Cases |

Support for Knowledge Management to Discoveries: Scientific Workflows and Artificial Intelligence

Knowledge Management /Transformation

Enterprise Vocabulary | Manage & Create Model Metadata

Align Models | Yolanda Gil | Denise | Patrick

<|-- | I - and document use cases

C - Interview

C - Use Cases
W --> | Formal Requirements Statement, 2-4 Use Cases | Requirements Input - Init3dbw2

Use Case Statements - Init3dbw2.pm21 | Wings Semantic Workflows
[ Requirements for caBIG Infrastructure to Support Semantic Workflows|https://wiki.nci.nih.gov/download/attachments/20285848/Requs_caBIG_InfrastructureSupportSWorkflow.ppt]
Recommendations for caBIG to Support Semantic Workflows
Use Cases for Semantic Workflows in caBIG |

caBIG Rules Engine White Paper v4

Knowledge Management

Enterprise Vocabulary | Manage & Create Model Metadata

Align Models | Joel Saltz |

Formal Requirements Statement

Knowledge Management

Manage & Create Model Metadata

Jyoti Pathak

Formal Requirements Statement

Knowledge Management

Enterprise Vocabulary | Manage & Create Model Metadata

Align Models | Frank Hartel | Patrick |

Formal Requirements Statement

Requirements Input - Init4pm18

Knowledge Management

Enterprise Vocabulary | Manage & Create Model Metadata

Align Models | Joshua Phillips | Patrick |

Requirements Input - Init4pm19

Semantic Web Applications to CTMS Use Cases

Knowledge Management

Search Models

Robert Freimuth

Shantanu

<|-- | A - Interview and/or follow-up via email with originators

C - Decomposed forum and other materials --> | Formal Requirements Statement | Requirements Input - Init4sd16 | caGrid querying |

Knowledge Management

Manage & Create Model Metadata

Search Models | Cui Tao | Hua | Hua | Shantanu

<|-- | C - Use Cases Template

C - Interview Cui Tao

C - Review forum details --> | Formal Requirements Statement | Requirements Input - Init4hm1

Use case - Init4hm1.SD210 |

Knowledge Management

Search Models

Sharon Gaheen

Shantanu

n/a

<|-- | C - Develop Summary Requirements Statement

C - Decomposed forum and other materials --> | Formal Requirements Statement | Requirements Input - Init4sd8 |

LexEVS "Portal" for use by other apps

Knowledge Management

Search Models

Dave Hau

Knowledge Management

Enterprise Vocabulary | Manage & Create Model Metadata

Search Models

Align Models | Craig Stancl |

Formal Requirements Statement

Knowledge Management

Enterprise Vocabulary | Manage & Create Model Metadata

Search Models

Align Models | Craig Stancl | Baris | Patrick

Formal Requirements Statement

CTS2 SFM DSTU Final 20090322

Knowledge Management

Enterprise Vocabulary | Manage & Create Model Metadata

Search Models

Align Models | Larry Wright |

Formal Requirements Statement

Knowledge Management

Model Administration

Guoqian Jiang

Hua

Formal Requirements Statement

Requirements Input - Init4hm1

Knowledge Management

Model Administration

Guoqian Jiang

Patrick

Formal Requirements Statement and 2-3 Summary Use Cases

Requirements Input - Init5pm20

Knowledge Management

Enterprise Vocabulary | Manage & Create Model Metadata

Align Models | Jyoti Pathak | Patrick | n/a | Shantanu

<|-- | A - 2-4 Use Cases if possible

C - Decompose Formal Requirements Statement --> | Formal Requirements Statement | Requirements Input - Init5pm21 |

Knowledge Management

Enterprise Vocabulary | Manage & Create Model Metadata

Align Models | Hannes Niedner | Patrick |

Formal Requirements Statement

Requirements Input - Init5pm22

Knowledge Management

Enterprise Vocabulary | Manage & Create Model Metadata

Search Models

Align Models | Guoqian Jiang | Hua |

Formal Requirements Statement

Requirements Input - Init5hm1

Knowledge Management

Enterprise Vocabulary | Manage & Create Model Metadata

Search Models

Align Models | Christo Andonyadis | Hua | n/a | Patrick

<|-- | C - Use Case Summary

C - decompose into questionnarie

C - Use Cases --> | Formal Requirements Statement | Requirements Input - Init1hm2

Use Cases - init1hm2.pm22 |

Constraint

Supplemental Specification Requirement on Ontology Best Practices

Jyoti Pathak

Shantanu

Formal Requirements Statement

Requirements Input - Init5sd9

FDA

NA

No Requirement Specified

Margaret Haber

Formal Requirements Statement

caBIG

Constraint

Supplemental Specifications Requirement, build a Glossary of Model Terms

Hannes Niedner

Shantanu

Hua

Formal Requirements Statement

Requirements Input - Init6sd10

Knowledge Management

Enterprise Vocabulary | Manage & Create Model Metadata

Search Models

Align Models | Daniela Smith | Shantanu |

Formal Requirements Statement

Requirements Input - Init6sd11

Knowledge Management

Enterprise Vocabulary | Manage & Create Model Metadata

Search Models

Align Models | Robert Freimuth | Shantanu |

Formal Requirements Statement C - Decomposed forum and other materials

Requirements Input - Init6sd30

metamodel for LIMS

Knowledge Management

Enterprise Vocabulary | Manage & Create Model Metadata

Search Models

Align Models | Joel Saltz | Patrick | Shantanu | Shantanu

<|-- | A - Review Use Cases

I - Interview Joel Saltz

C - Use Case Template in Round 1 --> | Requirements Input - Init6pm23

Use Cases - Init6pm23.u | Integration Use Cases |

Knowledge Management

Enterprise Vocabulary | Manage & Create Model Metadata

Align Models | Brian Davis | Shantanu | n/a | Shantanu

<|-- | A - Use Case Development

C - Decompose into requirements statement --> | Formal Requirements Statement | Requirements Input - Init6sd12 |

CDISC SHARE

Knowledge Management

Enterprise Vocabulary | Manage & Create Model Metadata

Knowledge Management/Transformation

Enterprise Vocabulary | Manage & Create Model Metadata

Search Models

Align Models | Frank Hartel | Shantanu | n/a | Patrick

<|-- | C - Use Case Development

C - Formal Requirement Statement

C - Use Cases --> | Formal Requirements Template Decomposed forum and other materials | Requirements Input - Init1sd13

Use Cases - INIT1SD13.pm23 |

Knowledge Management

Manage & Create Model Metadata

Sal Mungal

Hua

n/a

Patrick

<|-- | C - Use Case Development
C - Develop narrative (actor, bus goal, success scenario)

C - Use Cases --> | Formal Requirements Statement; High level use cases for Services | Requirements Input - Otherhm1

Use Cases - Otherhm1.pm12 | Related to Christo Andonyadis requirements - See 8 Other |

Support for Reusable Modules/Sections of Forms

Knowledge Management

Manage & Create Model Metadata

Dianne Reeves

Denise

n/a

Patrick

<|-- | A - Develop narrative (actor, bus goal, success scenario)

Use Cases --> | Formal Requirements Statement; High level use cases for Services | Use Cases - Init8pm25.pm24 | Make Form Modules reusable |

Knowledge Management

Manage & Create Model Metadata

Sal Mungal

Hua

Baris

Patrick

<|-- | C - Develop formal requirement statement

C - Use Cases --> | Formal Requirements Statement | Requirements Input - Otherhm2

Use Cases - Otherhm2.pm13 |

Support for Structured Eligibility

Knowledge Management

Enterprise Vocabulary | Manage & Create Model Metadata

Search Models

Align Models | Christo Andonyadis | Denise | Patrick | Patrick

<|-- | A - Interview or Group Discussion to develop high level use case scenarios

C - Use Cases --> | Formal Requirement Statement and Use Cases Summary | Requirements Input - Init1dbw7

Use Cases - Init1dbw7.pm19 | caBIG Community |

caEHR Content Development

NA

No Requirement Specified

Gilberto Fragoso

caEHR SI Services

NA

No Requirement Specified

Gilberto Fragoso

ICRi WG Use Case Scenarios

Knowledge Management

Enterprise Vocabulary | Manage & Create Model Metadata

Search Models

LS and CS Business Architecture Modeling Use Cases

Knowledge Management

Enterprise Vocabulary | Manage & Create Model Metadata

Search Models

Align Models | Juli Klemm | Denise |

<|-- | I - write/review up requirements statements: overlaps with ICRi WG Use Case Scenarios

C - CBIIT Interview --> | Formal Requirements Statement | Life Sciences and Clinical Sciences Governance |

Seamless integration of Data and Services through workflows

Knowledge Management

Manage & Create Model Metadata

Search Models | Anand Basu | Denise |

C - CBIIT Interview | Formal Requirements Statement | Requirements Input - Otherdbw7 | Application Engineering |

Contractor and Software Vendor Application Development Support

Knowledge Management

Enterprise Vocabulary | Manage & Create Model Metadata

Search Models

Federated Data w/single source of 'truth'

Knowledge Management

Manage & Create Model Metadata

John Speakman

Denise

<|-- | I - Write up requirements Statements

C - CBIIT Interview --> | Formal Requirements Statement | Requirements Input - Otherdbw4 | Ability to have data spread over the grid/internet, but know which data is the original, source of truth |

CTMS Interoperability Scenarios: Maximize reuse, Minimize development

Knowledge Management

Enterprise Vocabulary | Manage & Create Model Metadata

Search Models

CTMS Interoperability Scenarios |

Programmatic access to 'Materials and Methods' section of a paper

Knowledge Management

Enterprise Vocabulary | Manage & Create Model Metadata

Search Models

Align Models | Ian Fore | Denise | Patrick

<|-- | I - Write up requirements statement

C - CBIIT Interview

C - Use Cases --> | Formal Requirements Statement | Requirements Input - Otherdbw3

Use Cases - Otherdbw3.pm23 | Similar to Yolanda's semantic workflows |

Registration of Models in GME

Knowledge Management

Manage & Create Model Metadata

Search Models | Tony Pan | Baris | n/a |

<|-- | W - Observe (A requirement that can be for Architecture or Semantic Infrastructure)

C - Write up requirements statement

C - CBIIT Interview --> | Formal Requirements Statement and Use Cases | Requirements Input - Init8bes15 |

TCGA AIM-E Integration Use Cases

Knowledge Management

Manage & Create Model Metadata

Search Models | Tony Pan

Daniel Rubin

Paul Mulhern | Shantanu | Shantanu

<|-- | A - Write up requirements statement

A - Develop Use Cases to describe the as-is and to-be scenarios for integration services --> | Formal Requirements Statement and Use Cases | Requirements Input - InitotherSD75 |

Harmonize and reuse metadata across different terminologies

Knowledge Management

Enterprise Vocabulary | Manage & Create Model Metadata

Search Models

Align Models | Dianne Reeves | Denise |

<|-- | A - Develop Use Cases

C - Requirements Statement --> | Formal Requirements Statement and Use Cases | Requirements Input - Init1dbw11 |

US Department of Defense (USDOD)	NA	No Requirement Specified	Nancy Lawler	Formal Requirements Statement	Requirements around need for secure content
Rules/OWL2 Based Inferencing	NA	No Requirement Specified	Cecil Lynch	Formal Requirements Statement
HHS OS - Data.gov	NA	Some References to Linked Data and Cloud Computing, but no clear KR Requirement.	George Thomas	Formal Requirements Statement, high level use cases	ppt links

semantic.data.gov discussion |

Curator Harmonization Activities

Knowledge Management

Manage & Create Model Metadata

Search Models | Tommie Curtis | Denise |

<|-- | A - Use Case Development

C - Requirements Statement --> | Formal Requirements Statement, high level use cases | Requirements Input - Init1dbw12 |

Support for Curation Workflow Activities

No Requirement defined, most likely it is

Federated Metadata Registries	No Requirement Defined, Most likely a design constraint	Requirement for Federated MDRs captured in the Supplemental Specifications	Saurin Mehta	Denise	Formal Requirements Statement, high level use cases	Novartis MDR
Canada Infoway Clinical Concept Representation	No Clear Requirement Defined.	Discussion presentation on identifying Clinical Concepts through use of HL7 and Clinician Feedback.	Mark Shafarman, Bill Gilliam	Formal Requirements Statement, high level use cases	Canada Infoway Clinical Concept ppt

Explanation of Master List columns

Infrastructure -
**IS09 Validation - The Validation service verifies structural and semantic consistency across messages used in interoperability scenarios.
**IS10 Transformation - The Transformation service provides a functional end point to manage and enact mappings between syntactically disparate information types.
**IS11 Knowledge Management - Knowledge Management service represents a series of capabilities around the storage, versioning, searching, discovery, and expression of the semantics supporting key capabilities.
**IS12 Service Contract Management - Service Contract Management service represents a series of capabilities around the storage, versioning, searching, discovery and expression of the contract semantics supporting interoperability.
**IS13 Enterprise Vocabulary - Enterprise Vocabulary services support the management, storage, and mapping of terminologies and value sets.
Topic - is the forum topic title off the request whether it be from the Spring Requirements Forum, the Winter Requirements Forum or a title given to a request that came directly from a customer or stakeholder.
Submitter - is the stakeholder requesting the new feature or work.
Requirement Statement - is the person initiating the process whether pulling information from the forums or receiving requests from stakeholders
Interview Analyst - is the person in direct contact with the submitter in order to extract requirements.
Use Case Analyst - is the person taking the requirements in order to create use cases.

<!--*Activities - is a list of tasks related to this requirement and their status.

- Follow-up interview
- Observe
- Use Case Template (text)
- Use Case Model (formalized/UML diagram)
- Group Discussion
- Prototype
  Activities are marked with one of the following codes for status:
I = In process
W = Waiting for Approval
A = Approved
C = Completed
WR = Waiting Room-->
Phase 1 Target - the goal to be achieved in phase 1
Requirement Link(s) - artifacts created during the requirements process
Notes - notes related to this requirement

</html>

Content

Space Tools

SI Conop Initiatives Requirements Master List

Explanation of Master List columns