BPM Synthetic UI Logs Collection
收藏资源简介：
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 <SeedLog, Case-level variability conf., Scenario-level variability conf.>. 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 <Problem, LogSize, Balanced?>. 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.
本数据集包刊载于<em>BPM Demos&Resources</em>（BPM演示与资源）出版物中，标题为<em>BPM Hub: An Open Collection of UI Logs</em>（BPM中心：开放UI日志集），包含合成用户界面（User Interface, UI）日志及对应截图。这些UI日志高度贴合行政领域的真实业务场景，其复杂度可通过活动数量、流程变体数量以及影响决策点结果的视觉特征进行衡量。本数据集采用BPM日志生成工具（BPM Log Generator）生成，该工具需以下初始生成配置：<strong>初始生成配置</strong>种子日志（Seed Log）：为每个流程变体及其关联截图各提供一个实例。可变性配置：案例级：指用户可引入或修改的内容变体，例如文本输入内容、可选选项、复选框等的变体。场景级：指变更流程截图中不同应用的图形用户界面（Graphical User Interface, GUI）外观与观感相关的组件。<strong>数据集包内容</strong>本数据集包包含三个独立流程P1、P2、P3，均提供了初始配置，即由<种子日志，案例级可变性配置，场景级可变性配置>组成的三元组。各流程特征如下：P1. 客户创建活动数：5变体数：2决策点：围绕邮件接收环节是否存在附件展开。P2. 客户删除。系统内用户存在性校验活动数：7变体数：2决策点：基于客户关系管理系统（Customer Relationship Management, CRM）中用户搜索结果判定，以复选框形式体现。P3. 客户删除。客户付款校验活动数：7变体数：4决策点：涉及两个条件：邮件中存在可证明发票已付款的附件；用户CRM档案中存在未结发票。上述流程均仅包含单个决策点、无循环且按顺序执行，以确保非交错执行模式。其中P3的决策点由两个视觉特征共同决定，因此复杂度更高。<strong>UI日志生成</strong>针对每个流程，通过应用案例级可变性配置生成事件数范围为{10, 25, 50, 100}的不同规模日志。当日志规模超出预设值时，将移除最后一个实例以保证日志完整性。每种日志规模均对应平衡日志与非平衡日志两类：平衡日志的各变体实例分布近似均等；非平衡日志的最频繁变体与最稀少变体的实例频率差异超过20%。<strong>场景</strong>为保证实验结果的可靠性，针对每个<流程，日志规模，是否平衡>三元组，共生成30个场景。这些场景在场景级存在细微差异，尤其体现在截图中应用的外观观感与用户界面层面。每个场景包含对应特定流程、按日志规模（10, 25, 50, 100）及是否平衡（平衡、非平衡）分类的UI日志。存储UI日志及对应截图的文件夹命名规则为：sc{场景ID}_size_{日志规模}_{是否平衡}。<strong>附加工件</strong>此外，每个流程还包含两个附加工件：initial_generation_configuration文件夹：存储使用[5]所述工具生成流程数据所需的配置数据。decision.json文件：指定驱动决策点处决策行为的判定条件。<strong>decision.json</strong>decision.json作为测试预言，用于为挖掘得到的数据提供验证标签。其包含两个主要模块："UICompos"与"decision"。"UICompos"模块：为每个与决策相关的活动设置一个键，存储代表涉及的UI组件及其边界框坐标的键值对。"decision"模块：基于上述UI组件，定义案例匹配特定流程变体的判定条件。
