Package org.processmining.analysis.conformance

Contains classes related to the Conformance Analysis Plugin.

See:
          Description

Interface Summary
ThreadNotificationTarget An object which has to be notified after the thread is done.
 

Class Summary
AnalysisMethodExecutionThread Custom thread implementation that executes the given AnalysisMethod and provides those categories with the results that have asked for it.
BehAppropriatenessAnalysisGUI Creates the GUI for the "Behavioral Appropriateness" tab in the results frame.
BehAppropriatenessVisualization Overrides the default Petri net visualization to add behavioral appropriateness diagnostics.
ConformanceAnalysisConfiguration Creates a configuration object that contains all the analysis categories and options that are available for the ConformanceAnalysisPlugin.
ConformanceAnalysisPlugin The plugin provides some basic conformance analysis between a log and a Petri net model by replaying the log in the model in a non-blocking way.
ConformanceAnalysisResults Displays the analysis results for the chosen categories in a generic way.
ConformanceAnalysisSettings Displays the analysis settings frame that precedes the actual conformance analysis.
ConformanceLogReplayResult Contains all the results obtained during log replay analysis.
ConformanceMeasurer Actually takes those measurements that are needed to calculate the selected conformance metrics.
DiagnosticAuditTrailEntry Diagnostic data structure for an audit trail entry.
DiagnosticLogEvent Data structure to represent a log event, i.e., the actual type of log event, such as 'A complete' (i.e., including event type and opposed to the audit trail entry, which is an occurrence of a log event).
DiagnosticLogEventRelation Data structure for keeping track of the log event relations in a log trace or an execution trace of a model.
DiagnosticLogReader This class is used to enhance the log reader with conformance check results.
DiagnosticLogTrace A data structure that collects diagnostic information for a process instance in the context of conformance checking.
DiagnosticPetriNet This class is used to enhance the petri net model with conformance check results.
DiagnosticPlace The diagnostic place can be enhanced by diagnostic information to be stored during log replay and will be used to form a part of the diagnostic Petri net.
DiagnosticPNEdge The diagnostic edge can be enhanced by diagnostic information to be stored during log replay and will be used to form a part of the diagnostic Petri net.
DiagnosticTransition The diagnostic transition can be enhanced by diagnostic information to be stored during log replay and will be used to form a part of the diagnostic Petri net.
DisplayState Storing the visualization state of the conformance analysis result.
FitnessAnalysisGUI Creates the GUI for the "Fitness" tab in the results frame.
FitnessLogTraceVisualization Overrides the default visualization methods to show the selected log traces instead of the model.
FitnessVisualization Overrides the default visualization methods to include all the diagnostic information being requested.
StateSpaceExplorationMethod  
StateSpaceExplorationResult  
StrAppropriatenessVisualization Overrides the default Petri net visualization to add structural appropriateness diagnostics.
StructAppropriatenessAnalysisGUI  
StructuralAnalysisMethod Invokes all structural analysis methods (i.e., for which only a process model is necessary).
StructuralAnalysisResult Contains all the results obtained during the structural analysis.
 

Package org.processmining.analysis.conformance Description

Contains classes related to the Conformance Analysis Plugin. Most information systems log events (e.g., transaction logs, audit trails) to audit and monitor the processes they support. At the same time, many of these processes have been explicitly modeled. For example, SAP R/3 logs events in transaction logs and there are EPCs (Event-driven Process Chains) describing the so-called reference models. These reference models describe how the system should be used. The coexistence of event logs and process models raises an interesting question: “Does the event log conform to the process model and vice versa?”. To tackle the problem, we distinguish two dimensions of conformance: fitness (the event log may be the result of the process modeled) and appropriateness (the model is a likely candidate from a structural and behavioral point of view).