Data Provenance –Use Case (Discovery) Ahsin Azim– Use Case Lead Presha Patel – Use Case Lead 1

Agenda Topic Time Allotted General Announcements2 minutes Use Case Discussion Progress to Date1 minute Review Definitions1 minute Review Actors & Roles5 minutes Review Activity Diagrams/Base Flows50 minutes Next Steps1 minutes 2

Sections for Review 3 Today we will be reviewing: 1.Actors & Roles 2.Activity Diagrams 3.Base Flows Double click the icon to open up the Word Document with the sections for review

4 Progress to Date Use Case SectionsStatus In Scope Out of Scope Assumptions Context Diagram User Stories Pre Conditions Post Conditions Actors & Roles Activity Diagrams Base Flows Functional Requirements Sequence Diagrams Dataset Requirements = section developed = section under development(% completed) = indicates there are 3 sections for development (1 for each of the scenarios identified)

Use Case Definitions 5 Draft Definitions for the Use Case terms below have been posted on the Data Provenance Glossary Page: Should you have any comments on the definitions, please post them on our Use Case Feedback form: TermDefinition Data SourceA role played by a system that creates data (acting as the true source). End PointA role played by a system that receives the data. Transmitter A role played by a system that serves as a pass through, transporting data from a data source and transmitting that data (unchanged) to an end point. Assembler A role played by a system that extracts data from one or more data sources and compiles all of the data so that the output equals the sum of the data source inputs in aggregate. There is neither less nor more data available in the output of an assembler than what can be created by joining all data from the input data sources. The provenance of the output data is no different than the provenance of the input data (with the exception of the provenance information added to indicate the role of the system responsible for assembling the information). (NOTE: this implies machine logic) Composer A role played by a system that extracts data from one or more data sources and compiles the data so that the output is less or more than just the sum of the inputs from the data source. A system playing the role of a composer takes an active role in picking and interacting with the source data. It may even interact with a human use to incorporate additional data or update the available information before creating the output data which it dispatches to an end point. The provenance of any data created, updated or omitted by during the interaction is attributed to system playing the role of the Composer or the human operator using the system playing the role of the Composer. (NOTE: this implies human logic is involved where there is a human system operator and machine logic may being applied depending on the functionality of the system acting as the Composer)

A look ahead: Data Provenance Next Week 6 August 21 st, 2014 – All Hands Community Meeting (2:30-3:30) – Begin review of Functional Requirements Provide your comments on the bottom of this page

Support Team and Questions Please feel free to reach out to any member of the Data Provenance Support Team: Initiative Coordinator: Johnathan Coleman: OCPO Sponsor: Julie Chua: OST Sponsor: Mera Choi: Subject Matter Experts: Kathleen Conner: and Bob Yencha: Support Team: – Project Management: Jamie Parker: – Use Case Development: Presha Patel: and Ahsin Azim: – Harmonization: Rita Torkzadeh: – Standards Development Support: Amanda Nash: – Support: Lynette Elliott: and Apurva Dharia: 7