data provenance community meeting august 21st, 2014

12
Data Provenance Community Meeting August 21st, 2014

Upload: daniel-stokes

Post on 04-Jan-2016

215 views

Category:

Documents


1 download

TRANSCRIPT

Page 1: Data Provenance Community Meeting August 21st, 2014

Data Provenance Community Meeting

August 21st, 2014

Page 2: Data Provenance Community Meeting August 21st, 2014

2

Meeting Etiquette

Click on the “chat” bubble at the top of the meeting window to

send a chat.

• Please mute your phone when you are not speaking to prevent background noise.– All meetings are recorded.

• Please do not put your phone on hold. – Hang up and dial back in to prevent hold

music.• Please announce your name before

speaking• Use the “Chat” feature to ask questions or

share comments.– Send chats to “All Participants” so they

can be addressed publicly in the chat, or discussed in the meeting (as appropriate).

Page 3: Data Provenance Community Meeting August 21st, 2014

3

Agenda

Topic Time Allotted

General Announcements 1 minuteUse Case Discussion 58 minutesNext Steps/Questions 1 minute

Page 4: Data Provenance Community Meeting August 21st, 2014

4

Next meeting:• All Hands: Thursday August 28th, 2014 – 2:30-3:30 pm ET• http://wiki.siframework.org/Data+Provenance+Initiative

• All meeting materials (including this presentation) can be found on the Past Meetings page:• http://wiki.siframework.org/Data+Provenance+Past+Meetings

General Announcements

Page 5: Data Provenance Community Meeting August 21st, 2014

5

S&I Framework Phases outlined for Data Provenance

Phase Planned Activities Pre-Discovery Development of Initiative Synopsis

Development of Initiative Charter Definition of Goals & Initiative Outcomes

Discovery Creation/Validation of Use Cases, User Stories & Functional Requirements Identification of interoperability gaps, barriers, obstacles and costs Review of Candidate Standards

Implementation Creation of aligned specification Documentation of relevant specifications and reference implementations

such as guides, design documents, etc. Development of testing tools and reference implementation tools

Pilot Validation of aligned specifications, testing tools, and reference implementation tools

Revision of documentation and toolsEvaluation Measurement of initiative success against goals and outcomes

Identification of best practices and lessons learned from pilots for wider scale deployment

Identification of hard and soft policy tools that could be considered for wider scale deployments

We are Here

Page 6: Data Provenance Community Meeting August 21st, 2014

6

Data Provenance –Use Case (Discovery)Ahsin Azim– Use Case Lead

Presha Patel – Use Case Lead

Page 7: Data Provenance Community Meeting August 21st, 2014

7

Week Target Date (2014) All Hands WG Meeting Tasks

Review & Comments from Community via Wiki page

due following Tuesday by 8 P.M. Eastern

10 8/21Review: Scenario #1 and #2 Functional Requirements and Sequence DiagramsIntroduce: Scenario #3 Functional Requirements and Sequence Diagrams

Review Scenario #3 Functional Requirements and Sequence Diagrams

11 8/28Review :Scenario #3 Functional Requirements and Sequence DiagramsIntroduce: Dataset Requirements

Review Dataset Requirements

12 9/4 Review Dataset Requirements and Risks/IssuesIntroduce Risks and Issues

Review Data Set Requirements and Risks And Issues

13 9/18 Finalize Data Set Requirements and Risks/IssuesBegin End to End Review Review Risks/Issues

14 9/25 End-to-End Comments Review & disposition End-to-End Review ends

15 10/2 Finalize End-to-End Review Comments & Begin Consensus Begin casting consensus vote

Proposed Use Case & Functional Requirements Development Timeline

Page 8: Data Provenance Community Meeting August 21st, 2014

8

Agenda

Topic Time Allotted

General Announcements 2 minutes

Use Case Discussion

Discuss Timeline/Progress to Date 2 minutes

Comments and Dispositions 10 minutes

Review Scenario #1 Sections (Functional Requirements and Sequence Diagram) 20 minutes

Review Scenario #2 Sections (Functional Requirements and Sequence Diagram) 20 minutes

Begin Review Scenario #3 Sections (Functional Requirements and Sequence Diagram) 5 minutes

Next Steps 1 minutes

Page 9: Data Provenance Community Meeting August 21st, 2014

9

Progress to Date

Use Case Sections Status

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)

= indicatesthere are 3 sections for development (1 for each of the scenarios identified)

Page 10: Data Provenance Community Meeting August 21st, 2014

Sections for Review

10

Today we will be reviewing: 1. Review Functional

Requirements and Sequence Diagram(s) for Scenarios 1, 2, and 3

Double click the icon to open up the Word Document with the sections for review

Sections for Review

Page 11: Data Provenance Community Meeting August 21st, 2014

11

A look ahead: Data Provenance Next Week

• August 28th, 2014 – All Hands Community Meeting (2:30-3:30)– Continue review of Functional Requirements and Sequence Diagrams

Provide your comments on the bottom of this page http://wiki.siframework.org/Data+Provenance+Use+Cases

Page 12: Data Provenance Community Meeting August 21st, 2014

12

Support Team and QuestionsPlease feel free to reach out to any member of the Data Provenance

Support Team:• Initiative Coordinator: Johnathan Coleman: [email protected] • OCPO Sponsor: Julie Chua: [email protected] • OST Sponsor: Mera Choi: [email protected]• Subject Matter Experts: Kathleen Conner: [email protected] and Bob

Yencha: [email protected] • Support Team:

– Project Management: Jamie Parker: [email protected] – Use Case Development: Presha Patel: [email protected]

and Ahsin Azim: [email protected] – Harmonization: Rita Torkzadeh: [email protected] – Standards Development Support: Amanda Nash:

[email protected] – Support: Lynette Elliott: [email protected] and Apurva Dharia:

[email protected]