Indicators for Open Issues in Business Process Models

[Context and motivation] In the early phases of requirements engineering, often graphical models are used to communicate requirements. In particular, business process models in graphical languages such as BPMN can help to explain the process that a software system should support. These models can then be used to derive more detailed requirements. [Question/Problem] Often, such models are incomplete showing only the most important cases or contain labels in natural language that are prone to ambiguities and missing information. The requirements engineer has to identify missing / ambiguous information manually. The aim of this paper is to discuss certain classes of such potential problems and how they can be found automatically. [Principal ideas/results] First, we analyzed a collection of business process models and found that they frequently contain typical types of problems. Second, we described those potential problems in a formal way. We present a catalogue of indicators for potential problems and suggest questions to be asked by a requirements engineer for getting additional information about the depicted process. We also developed a tool prototype that uses a combination of linguistic analysis and inspection of the control flow. This tool prototype was applied to 2098 business process models. [Contribution] The paper presents a catalogue of potential problems in business process models. It also shows how these problems can be identified automatically.

[1]  Leonardo Guerreiro Azevedo,et al.  Detection of naming convention violations in process models for different languages , 2013, Decis. Support Syst..

[2]  Derek Miers.  Best Practice (BPM) , 2006, ACM Queue.

[3]  Sven J. Körner,et al.  RESI - A Natural Language Specification Improver , 2009, 2009 IEEE International Conference on Semantic Computing.

[4]  Volker Gruhn,et al.  Reducing the cognitive complexity of business process models , 2009, 2009 8th IEEE International Conference on Cognitive Informatics.

[5]  Stefania Gnesi,et al.  Applications of linguistic techniques for use case analysis , 2003, Requirements Engineering.

[6]  William Empson,et al.  朦胧的七种类型 = Seven types of ambiguity , 1930 .

[7]  Patrick Delfmann,et al.  Supporting Terminological Standardization in Conceptual Models - a Plugin for a Meta-Modelling Tool , 2014, ECIS.

[8]  Patrick Pantel,et al.  VerbOcean: Mining the Web for Fine-Grained Semantic Verb Relations , 2004, EMNLP.

[9]  Jörg Becker,et al.  Generalizability and Applicability of Model-Based Business Process Compliance-Checking Approaches — A State-of-the-Art Analysis and Research Roadmap , 2012 .

[10]  Doina Bucur,et al.  A survey of formal business process verification : From soundness to variability , 2013, BMSD 2013.

[11]  Volker Gruhn,et al.  A heuristic method for detecting problems in business process models , 2010, Bus. Process. Manag. J..

[12]  Alex Kass,et al.  Using syntactic and semantic analyses to improve the quality of requirements documentation , 2014, Semantic Web.

[13]  Juan Sánchez,et al.  Business Process Modelling and Purpose Analysis for Requirements Analysis of Information Systems , 2008, CAiSE.

[14]  Volker Gruhn,et al.  Checking Properties of Business Process Models with Logic Programming , 2007, MSVVEIS.

[15]  Stefania Gnesi,et al.  An Automatic Quality Evaluation for Natural Language Requirements , 2001 .

[16]  Volker Gruhn,et al.  Detecting Common Errors in Event-Driven Process Chains by Label Analysis , 2011, Enterp. Model. Inf. Syst. Archit. Int. J. Concept. Model..

[17]  Bhawna Nigam,et al.  Tool for Automatic Discovery of Ambiguity in Requirements Too l for Automatic Discovery of Ambiguity in Requirements Tool for Automatic Discovery of Ambiguity in Requirements Tool for Automatic Discovery of Ambiguity in Requirements , 2012 .

[18]  Luisa Mich,et al.  Requirements for tools for ambiguity identification and measurement in natural language requirements specifications , 2008, Requirements Engineering.

[19]  Giuseppe Lami,et al.  An Empirical Study on the Impact of Automation on the Requirements Analysis Process , 2007, Journal of Computer Science and Technology.

[20]  Volker Gruhn,et al.  Flexible Evaluation of Textual Labels in Conceptual Models , 2015, EMISA.

[21]  Erik Kamsties,et al.  Ambiguity in Requirements Specification , 2004 .

[22]  Erik Kamsties,et al.  From Contract Drafting to Software Specification: Linguistic Sources of Ambiguity , 2003 .

[23]  Mathias Weske,et al.  Action patterns in business process model repositories , 2012, Comput. Ind..

[24]  Monique Snoeck,et al.  A systematic literature review of studies on business process modeling quality , 2015, Inf. Softw. Technol..

[25]  Giancarlo Guizzardi,et al.  Requirements engineering based on business process models: A case study , 2009, 2009 13th Enterprise Distributed Object Computing Conference Workshops.

[26]  András Pataricza,et al.  Methods of checking general safety criteria in UML statechart specifications , 2005, Reliab. Eng. Syst. Saf..

[27]  Siri-on Setamanit,et al.  Evaluating the impact of requirements analysis tools using simulation , 2008 .

[28]  Miles Osborne,et al.  Processing natural language software requirement specifications , 1996, Proceedings of the Second International Conference on Requirements Engineering.

[29]  Michael Fellmann,et al.  State-of-the-art of Business Process Compliance Approaches: A Survey (Extended Abstract) , 2014, EMISA.

[30]  Hajo A. Reijers,et al.  Improving the process of process modelling by the use of domain process patterns , 2015, Enterp. Inf. Syst..

[31]  Jan Mendling,et al.  On the Usage of Labels and Icons in Business Process Modeling , 2010, Int. J. Inf. Syst. Model. Des..

[32]  Jan Mendling,et al.  On the refactoring of activity labels in business process models , 2012, Inf. Syst..

[33]  Francis Chantree,et al.  Identifying Nocuous Ambiguities in Natural Language Requirements , 2006, 14th IEEE International Requirements Engineering Conference (RE'06).