Architecture Tutorial Overview of Today’s Talks Provenance Data Structures Recording and Querying Provenance –Break (30 minutes) Distribution and Scalability Security Methodology

Architecture Tutorial Querying for Provenance by Simon Miles

Architecture Tutorial P-Structure To help execute queries about the past processes in an application, a provenance store categorises recorded p-assertions in a larger data structure The p-structure is a navigable hierarchy exposed through query interfaces of the provenance store.

Architecture Tutorial Collect p-assertions together in a view. A view is the set of assertions by 1 actor about 1 interaction. A view contains: – An actor identity – A set of p-assertions A view is one of two view kinds: sender or receiver Donor Data Collector User Interface

Architecture Tutorial Interaction Records

Architecture Tutorial Query Types There are two types of query over a provenance store: –A process documentation query is a query over the p-structure to retrieve individual pieces of data, e.g. XQuery or XPath –A provenance query is a query for the provenance of an entity, making use of the process documentation to determine this

Architecture Tutorial Provenance Queries Example provenance question: –What is the provenance of a donor organ’s diagnosis? Or can be rephrased as… –Why was a potential donor organ accepted / rejected for use? May be asked when a possible mistake was made, or just for regular auditing The results of a query is a subset of the recorded process documentation

Architecture Tutorial Provenance of Donor Diagnosis Donation Decision Donor Data Collector User Interface

Architecture Tutorial Provenance of Donor Diagnosis Donation Decision Donor Data Collector User Interface Decision Request User Interface Donor Data Collector Patient (in Brain Death Notification) Brain Death Manager User Interface Is Response To Is Decision On Justification Report Donor Data Collector User Interface Is Justified By

Architecture Tutorial Provenance of Donor Diagnosis Donation Decision Donor Data Collector User Interface Decision Request User Interface Donor Data Collector Donor Data Collector Testing Lab EHCR Donor Data Collector EHCRS Patient (in Brain Death Notification) Brain Death Manager User Interface Is Response To Is Based On Patient Test Results Test Results Donor Data Collection Is Decision On Justification Report Donor Data Collector User Interface Is Justified By

Architecture Tutorial Provenance of Donor Diagnosis Donation Decision Donor Data Collector User Interface Decision Request User Interface Donor Data Collector Donor Data Collector Testing Lab EHCR Donor Data Collector EHCRS Patient (in Brain Death Notification) Brain Death Manager User Interface Is Response To Is Based On Patient Test Results Test Results Donor Data Collection EHCR Request EHCRS Donor Data Collector Is Response To Testing Lab Donor Data Collector Request Blood Tests Is Response To Is Decision On Justification Report Donor Data Collector User Interface Is Justified By

Architecture Tutorial Provenance of Donor Diagnosis Donation Decision Donor Data Collector User Interface Decision Request User Interface Donor Data Collector Donor Data Collector Testing Lab EHCR Donor Data Collector EHCRS Patient (in Brain Death Notification) Brain Death Manager User Interface Is Response To Is Based On Patient Test Results Test Results Donor Data Collection Data Collection Request Donor Data Collector User Interface EHCR Request EHCRS Donor Data Collector Is Response To Was Caused By Testing Lab Donor Data Collector Request Blood Tests Is Response To Was Caused By Is Decision On Justification Report Donor Data Collector User Interface Is Justified By Request Blood Tests Donor Data Collector User Interface Was Caused By

Architecture Tutorial Provenance Queries A provenance query is made up of two parts: –Query Data Handle Identifies the entity of which you want to find the provenance, e.g. the donor organ decision –Relationship Target Filter Scopes the query results, so that only a manageable amount of relevant information is returned

Architecture Tutorial Query Data Handles Identifies a particular entity at the time of a particular event For example, a patient at the end of a transplant operation In our model, events are identified as the sending or receiving of messages The provenance of an entity is the process by which it came to be in the state it is in at that event

Architecture Tutorial Query Data Handles For a provenance store, a query data handle is a search within process documentation for a given documented entity Therefore, a query data handle is expressed as a search over the p-structure, e.g. in XPath In the example, the entity, the donation decision, is documented in the interaction between the User Interface and Donor Data Collector Donation Decision Donor Data Collector User Interface

Architecture Tutorial Relationship Target Filters To scope the results of a provenance query, a relationship target filter is used The filter is a function over an object of a relationship (a relationship target) returning true or false, depending on whether that object should be included in the results Donor Data Collector Testing Lab Test Results Decision Request User Interface Donor Data Collector Test Results Is Based On

Architecture Tutorial Relationship Target The set of information about an object of a relationship –Relationship name –Data item content –Parameter name –Source and sink of interaction –Asserter identity –Provenance store location –View kind (sender/receiver) Donor Data Collector Testing Lab Test Results Decision Request User Interface Donor Data Collector Test Results Is Based On

Architecture Tutorial Exclude “Is Justified By” Relation Donation Decision Donor Data Collector User Interface Decision Request User Interface Donor Data Collector Donor Data Collector Testing Lab EHCR Donor Data Collector EHCRS Patient (in Brain Death Notification) Brain Death Manager User Interface Is Response To Is Based On Patient Test Results Test Results Donor Data Collection Data Collection Request Donor Data Collector User Interface EHCR Request EHCRS Donor Data Collector Is Response To Was Caused By Testing Lab Donor Data Collector Request Blood Tests Is Response To Was Caused By Is Decision On Justification Report Donor Data Collector User Interface Is Justified By Request Blood Tests Donor Data Collector User Interface Was Caused By

Architecture Tutorial Exclude Donor Data Collection Parameter Donation Decision Donor Data Collector User Interface Decision Request User Interface Donor Data Collector Donor Data Collector Testing Lab EHCR Donor Data Collector EHCRS Patient (in Brain Death Notification) Brain Death Manager User Interface Is Response To Is Based On Patient Test Results Test Results Donor Data Collection Data Collection Request Donor Data Collector User Interface EHCR Request EHCRS Donor Data Collector Is Response To Was Caused By Testing Lab Donor Data Collector Request Blood Tests Is Response To Was Caused By Is Decision On Justification Report Donor Data Collector User Interface Is Justified By Request Blood Tests Donor Data Collector User Interface Was Caused By

Architecture Tutorial Exclude Process Marked with Tracer Donation Decision Donor Data Collector User Interface Decision Request User Interface Donor Data Collector Donor Data Collector Testing Lab EHCR Donor Data Collector EHCRS Patient (in Brain Death Notification) Brain Death Manager User Interface Is Response To Is Based On Patient Test Results Test Results Donor Data Collection Data Collection Request Donor Data Collector User Interface EHCR Request EHCRS Donor Data Collector Is Response To Was Caused By Testing Lab Donor Data Collector Request Blood Tests Is Response To Was Caused By Is Decision On Justification Report Donor Data Collector User Interface Is Justified By Request Blood Tests Donor Data Collector User Interface Was Caused By

Architecture Tutorial Summary The p-structure is the schema of a provenance store and a categorisation of p-assertions The process documentation query interface allows querying actors to search and extract process documentation from the p-structure The provenance query interface allows querying actors to find the provenance of an application entity Querying for provenance involves following relationships back from the documentation of the entity, to find its causes Results are scoped to that relevant to the querier

Architecture Tutorial Questions? Simon Miles