Page info
title title

This page is the master list for organizing stakeholder business requirements for the existing semantic infrastructure, that may impact the new CBIIT semantic infrastructure roadmap. The Semantic Infrastructure Roadmap replaces the 2009 Semantic Infrastructure Concept of Operations. Any requests which do not fit into the seven initiatives described by the Semantic Infrastructure Concept of Operations were also documented. After collection of more details on all the requirements, a UML Model depicting the high level technical service requirements and their decomposed use cases was developed. To communicate requirements for the existing infrastructure not listed here, the contact was Denise Warzel. For requirements pertaining to the new CBIIT semantic infrastructure, the contact was Dave Hau. For semantic infrastructure requirements for caEHR, the contact was John Speakman.

The following are links to related pages.

• UML Model of Use Cases by Requirement Level (pdf version)
• UML Model of Use Cases by Requirement Level (html version)
• A roadmap for requirement analysis for ECCF traceability
• SI Service Categories derived from initial use case analysis
• Supplemental Requirements Input page
• Requirements Elicitation Stakeholder Participants
• Requirements Elicitation Progression
• Explanation of Master List columns

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>