Delta July 5, 2018 Architectural Design Document Version 1.0 Project Team D.P. van den Berg 0949036 R.T. van Bergen 0938857 D.J.C. Dekker 0936100 S. van den Eerenbeemt 0954445 J. Mols 0851883 B.F. Rongen 0858160 B.W.M. van Rooijen 0895073 R.P. Schellekens 0944330 A.A. Vast 0854060 G. Walravens 0904152 S. Wessel 0941508 Project Managers S.P.O. Oostveen A. Rajaraman Project Supervisor dr. N. Zannone Customer dr. L. Genga Abstract This is the Architectural Design Document (ADD) for the APD extension developed by Delta. The APD extension adds several features to the existing APD tool, such as user management, experiment management and project sharing. The architectural design decisions in this ADD satisfy the software requirements in the SRD [1]. This document complies with the Software Engineering Standard, as specified by the European Space Agengy [2]. Contents 1 Introduction 6 1.1 Purpose............................................6 1.2 Scope..............................................6 1.3 List of definitions and abbreviations............................6 1.3.1 List of definitions...................................6 1.3.2 List of abbreviations.................................8 1.4 List of references.......................................8 1.5 Overview............................................9 2 System overview 10 2.1 Background.......................................... 10 2.2 Context and basic design.................................. 10 2.3 Design decisions....................................... 10 2.3.1 Extending the APD tool............................... 10 2.3.2 Programming language............................... 11 2.3.3 Operating system.................................. 11 2.3.4 Model-View-Controller design pattern...................... 12 2.3.5 Client-server model................................. 12 2.3.6 Web interface..................................... 12 2.3.7 Access control.................................... 13 3 System context 14 3.1 APD tool............................................ 14 3.2 MySQL............................................. 14 3.2.1 Implementation of MySQL............................. 14 3.3 SMTP mail server....................................... 14 3.3.1 Implementation of the STMP mail server..................... 15 4 System design 16 4.1 Design method........................................ 16 4.2 Decomposition........................................ 16 4.2.1 Back-end decomposition.............................. 16 4.2.2 Front-end decomposition.............................. 19 4.2.3 File structure..................................... 21 4.2.4 Database Design................................... 22 5 Components 24 6 Feasibility and resource estimates 25 6.1 Resource requirements.................................... 25 6.1.1 Using the web application.............................. 25 6.1.2 Hosting the Delta extension............................ 25 6.1.3 Developing the Delta extension.......................... 25 6.2 Performance.......................................... 26 7 Requirements traceability matrix 27 7.1 Software requirements to modules............................. 27 7.2 Modules to software requirements............................. 30 7.2.1 Back-end modules.................................. 30 7.2.2 Front-end modules.................................. 31 Document Status General Title of document Architectural Design Document Document identifier Delta.ADD/1.0 Version 1.0 Authors D.P. van den Berg R.T. van Bergen D.J.C. Dekker S. van den Eerenbeemt J. Mols B.F. Rongen B.W.M. van Rooijen R.P. Schellekens A.A. Vast G. Walravens S. Wessel History Version Date Author(s) Reason 0.1 2018-06-15 D.P. van den Berg Inital draft. S. van den Eerenbeemt J. Mols B.W.M. van Rooijen S. Wessel 1.0 2018-07-15 D.P. van den Berg Added section 4 and implemented S. van den Eerenbeemt feedback. J. Mols B.W.M. van Rooijen R.P. Schellekens S. Wessel Delta Architectural Design Document 4 Document Change Records Section Reason 4.2 Added component decomposition. Delta Architectural Design Document 5 1 Introduction 1.1 Purpose The Architectural Design Document (ADD) describes the fundamental design of the software that will be developed by the Delta team. In this document, an overview of the system is provided. This document also describes the design decisions that were made, and describes the decomposition of the software into several components. It is also specified which software requirements in the SRD [1] each component fulfills. 1.2 Scope The APD tool is designed to extract anomalous patterns together with their correlations. These patterns are extracted from historical logging data from past process executions. Users can upload event logs and process models on which experiments can be run. The results of these experiments can be visualized after they are completed [3]. The purpose of the Delta extension is to extend the currently existing APD tool with several fea- tures. First of all, this extension will support multiple users, which means the tool will need to have proper user management controls. The user management system will be created and several improvements have to be made to the user interface in order to realize these goals. Next to this, visualization of the results is important, as well as reporting on the progress of the experiments. The tool is currently able to discover patterns and subgraphs from a business process model and an event log. These patterns and subgraphs give information on the business process and anomalous traces in the event log. In the current version, however, comparing different result types is cumbersome. Delta will provide a more convenient way to manage experiments and their results as well as the projects they belong to. Furthermore, the administrator will be able to manage the users and the projects created by users, as well as monitor the user activity tracking of each individual user. These controls will also be provided by Delta. 1.3 List of definitions and abbreviations 1.3.1 List of definitions Administrator A registered user with the highest available access rights who manages both the tool and its users. Anomalous subgraph dis- The extraction of recurrent subgraphs involving one or more deviations covery from the process model [3]. APD tool The APD tool is an extension of the Esub tool designed to extract anoma- lous patterns together with their correlations. These patterns are ex- tracted from historical logging data from past process executions. Users can upload event logs and process models on which experiments can be run. After the experiments are completed, the tool supports the users in exploring the obtained results [3]. Business process A set of activities performed in an organization and technical environment that are coordinated to a certain product or service [4]. Child subgraph The child S of a subgraph S 0 is a subgraph which involves S 0 in its definition. Component A part of a phase of an experiment. Delta Architectural Design Document 6 Esub tool An online webtool supporting the visualization and exploration of the out- come of the frequent subgraph mining algorithm SUBDUE [5]. Experiment Both the anomalous subgraph discovery and partial order discovery to- gether. Experiment log A file that tracks all activities performed within an experiment. Experiment phase Anomalous subgraph discovery and partial order discovery are the two phases of one experiment. Event log file A file that consists of traces [3]. Final Result The outcome of an experiment. Graph .g file A file that collects multiple graphs, each involving a set of edges and vertices. Intermediate result The outcome of either a component or an experiment phase. Maximal subgraph A subgraph s is maximal in a set of subgraphs if there does not exist a subgraph s0 such that s0 is a supergraph of s. Minimal subgraph A subgraph s is minimal in a set of subgraphs if there does not exist a subgraph s0 such that s0 is a subgraph of s. Parent subgraph A subgraph S is a parent of another subgraph S 0 if S 0 is a child of S. Partial order discovery An experiment phase creating patterns from anomalous subgraphs and partially ordering them based on their location in the log traces [3]. Petri net A mathematical model used for the specification and the analysis of parallel processes [6]. Process model A representation of the prescribed behavior of a business process [3]. Project A combination of an event log, a process model, and a unique project name. The project is stored together with any experiments run under that project name. Project owner The user who created the project. Registered user A user with a registered account on the APD tool. Responsive A website is responsive when dynamic changes are made to the appear- ance of the site depending on the screen size and orientation of the device being used to view it [7]. Result Either an intermediate result or final result. Subgraph A graph whose vertices and edges are subsets of the vertices and edges of another graph [8]. Supergraph A graph S is a supergraph of graph S 0 if the vertices and edges of S 0 are a subset of the vertices and edges of S. Support The support of a subgraph/pattern is equal to the fraction of graphs which involve the subgraph/pattern at least once [3]. Delta Architectural Design Document 7 Synchronous function A task that have to be completed before a new task can be called. Trace A trace in a business process model is a sequence of events generated during a process execution. Unregistered user A user who does not have an account on the