DOI: 10.5281/zenodo.8083836
title: BPM Synthetic UI Logs Collection

description: This data package described in the <em>BPM Demos&Resources</em> publication entitled: "<em>BPM Hub: An Open Collection of UI Logs</em>", consists of synthetic UI logs along with corresponding screenshots. The UI logs closely resemble real-world use cases within the administrative domain. They exhibit varying levels of complexity, measured by the number of activities, process variants, and visual features that influence the outcome of decision points. For its generation, the BPM Log Generator tool has been used, which requires the following initial generation configuration: <strong>Initial Generation Configuration</strong> Seed log: Includes a single instance for each process variant and their associated screenshots. Variability configuration: Case-level: Refers to variations in the content that can be introduced or modified by the user, such as variations in the text inputs, selectable options, checkboxes, etc. Scenario-level: Refers to varying the GUI (Graphical User Interface) components related to the look and feel of the different applications appearing in the process screenshots. <strong>Data Package Contents</strong> The data package comprises three distinct processes, P1, P2, P3, for which their initial configuration is provided, i.e., a tuple of &lt;SeedLog, Case-level variability conf., Scenario-level variability conf.&gt;. They are characterized by the following: P1. Client Creation Activities: 5 Variants: 2 Decision point: Revolves around the presence of an attachment in the reception of an email. P2. Client Deletion. User's presence in the system Activities: 7 Variants: 2 Decision point: Based on the result of the user's search in the Customer Management System (CRM), represented by a checkbox. P3. Client Deletion. Validation of customer payments Activities: 7 Variants: 4 Decision: Involves two conditions: The presence of an attachment justifying the payment of the invoices in the email. The existence of pending invoices in the user CRM profile. These problems depict processes with a single decision point, without cycles, and executed sequentially to ensure a non-interleaved execution pattern. Particularly, P3 shows higher complexity as its decision point is determined by two visual characteristics. <strong>Generation of UI Logs</strong> For each problem, case-level variations have been applied to generate logs with different sizes in the range of {10, 25, 50, 100} events. In cases where the log exceeds the desired size, the last instance is removed to maintain completeness. Each log size has its associated balanced and unbalanced log. Balanced logs have an approximately equal distribution of instances across variants, while unbalanced logs have a frequency difference of more than 20% between the most frequent and least frequent variants. <strong>Scenarios</strong> To ensure the reliability of the obtained results, 30 scenarios are generated for each tuple &lt;Problem, LogSize, Balanced?&gt;. These scenarios exhibit slight variations at the scenario-level, particularly in the look and feel and user interface of the applications depicted in the screenshots. Each scenario consists of UI logs that correspond to specific problems categorized by log size (10, 25, 50, 100) and balanced? (Balanced, Unbalanced). Folders containing UI logs and their corresponding screenshots are organized in folders named as follows: sc{scenarioId}_size_{LogSize}_{Balanced?}. <strong>Additional Artefacts</strong> In addition, each problem includes two more artefacts: initial_generation_configuration folder: Holds the data needed for problem data generation using the [5] tool. decision.json file: Specifies the condition driving the decision made at the decision point. <strong>decision.json</strong> The decision.json acts as a testing oracle, serving as a label for validating mined data. It contains two main sections: "UICompos" and "decision". The "UICompos" section includes a key for each activity related to the decision, storing key-value pairs that represent the UI components involved, along with their bounding box coordinates. The "decision" section defines the condition for a case to match a specific variant based on the mentioned UI components.