Modeling Business Rules for Supervisory Control of Process-Aware Information Systems

Collection and Elicitation of Business Process Compliance Patterns with Focus on Data Aspects

“…Around one third of the papers proposes their own compliance monitoring or compliance management framework (Awad et al 2015;Barnawi et al 2016;El Gammal 2012;Elgammal et al 2016;Giblin et al 2006;Gong et al 2016;Ly 2016;Ly et al 2011Ly et al , 2015Maggi et al 2011;Papazoglou 2011;Schumm et al 2010;Thullner et al 2011;Turetken et al 2012). Those frameworks mainly try to comprehensively address the topic of compliance verification by checking compliance at design-time (Awad 2010; Awad and Weske Awad et al 2009Awad et al , 2011Becker et al 2010;Bernardi et al 2014;Cheikhrouhou et al 2014;El Gammal 2012;Elgammal et al 2010Elgammal et al , 2016Gomez-Lopez et al 2013;Ly 2016;Ly et al 2011;Schumm et al 2010;Stuht et al 2012;Turetken et al 2012) or checking compliance based on execution traces at the runtime of a business process (Awad et al 2015;Barnawi et al 2016;Chesani et al 2008Chesani et al , 2009De Masellis et al 2014;El Gammal 2012;Lam 2017;Ly 2016;Ly et al 2015;Maggi et al 2011;Ramezani 2017;Santos et al 2012).…”

Eunomia (Ευνομiα): A Requirement Engineering Based Compliance Framework for Software Systems

“…There are some works that address subsets of these factors that help to ensure continuous compliance (Maxwell, Anton, 2010;Breaux, Vail & Anton, 2006;Schmidt, Anton & Earp,2012;Massey et al 2014;Massey et al 2010;Maxwell & Anton, 2010;Antón, Earp & Carter, 2013;Yu, Shinpei & Motoshi 2017;Ghanavati et al,2014;Flowerday & von Solms 2005;KPMG, 2008;Armellin et al, 2011;Galán et al, 2016;Linh et al, 2015;Namiri & Stojanovic, 2007;Santos et al, 2012;Ingolfo & Souza, 2013;Siegbahn & Engel, 2009), but none addresses all factors. That is the purpose of this thesis: To improve compliance with software requirements and legislation in the scenario where the legislation, the context, and the requirements can change, given a pre-existing set of requirements.…”

“…Other works (Ghanavati, Amyot, 2009;Businska et al, 2012;Massey at al 2010;Maxwell, Anton, 2010;Antón, Earp, Carter, 2013 ) propose how to guarantee compliance between business processes and law (Ghanavati, Amyot, 2009;Businska et al, 2012) or between law and software requirements (Massey at al 2010;Maxwell, Anton, 2010;Antón, Earp, Carter, 2013). Since we are dealing with continuous compliance, we also review the works related to goal model and compliance (Yu, Shinpei, Motoshi 2017) (Ghanavati et al,2014), continuous compliance (Flowerday and von Solms 2005;KPMG, 2008;Armellinet al, 2011;Galán et al, 2016), and compliance monitoring (Linh et al, 2015;Namiri and Stojanovic, 2007;Santos et al, 2012;Ingolfo and Souza, 2013;Siegbahn and Engel, 2009). Breaux and Anton (2005) propose a method called Semantic Parametrization that is used together with goal analysis for the derivation of semantic models of Policy Privacy Documents.…”

“…The majority of works thatdeal with Compliance Monitor focus on establishing compliance in business process model scope (Linh et al, 2015;Namiri and Stojanovic, 2007;Santos et al, 2012). The works that focus on requirements (Ingolfo and Souza, 2013;Siegbahn and Engel, 2009) are concerned in only one aspect of change the environment.…”

“…In the scope of monitoring the business process (Linh et al, 2015;Namiri and Stojanovic, 2007;Santos et al, 2012) there are different approaches: some focus in design time, other in compliance checking architectures or post-mortem conformance checking. As our focus is compliance with requirements, we do not focus on those works.…”