This shows you the differences between two versions of the page.
Next revision | Previous revision Next revision Both sides next revision | ||
bpmn-leaks-when-analysis [2018/11/20 12:34] pullonen created |
bpmn-leaks-when-analysis [2019/09/29 16:53] admin |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== BPMN leaks-when analysis ====== | ====== BPMN leaks-when analysis ====== | ||
- | TODO | + | In BPMN leaks-when analysis the input is a BPMN model with annotations in pseudocode to write out how different components are related. |
+ | |||
+ | ===== Annotating the model ===== | ||
+ | The BPMN leaks-when analysis uses the SQL privacy editor as an interface although its input language is not SQL. All tasks that transform the data are annotated to show which components of the inputs are used to compute which outputs and to give names to the computations. | ||
+ | |||
+ | ===== Running the analysis ===== | ||
+ | |||
+ | BPMN leaks-when analysis is accessible from the SQL privacy editor and can be activated by clicking the respective button. | ||
+ | |||
+ | The analysis output is a table that summarizes which components of the inputs flow to the outputs. The cells in the table summarize the conditions and filters that the data passes. For data that //always// flows to the output there were no restrictive filters in the flow. The cell value //never// means that this output is not affected by that input. Finally, the //if// condition indicates that the flow is conditional and the passed filters can be seen when hovering over the cell. | ||
+ | |||
+ | ===== Source code ===== | ||
+ | |||
+ | The source code of the analysis tool is available at [[https://github.com/pleak-tools/pleak-leaks-when-analysis|pleak-leaks-when-analysis]] repository. The user interface of the analysis tool is accessible through [[https://github.com/pleak-tools/pleak-sql-editor|pleak-sql-editor]]. |