A methodology for quality assurance for business process modeling with BPMN: A case study for the SIGEPE software

During the development of computer systems, business process modeling is a phase that delivers important firsthand inputs for requirements engineering. The goal of business process mapping is to understand, improve and organize the activities of the process to ensure efficient and correct implementation. Quality in business process modeling can decisively influence the software quality. Internal quality analysis is made in-house, for the development process, while external quality analysis is made for the final product and satisfaction of the end consumer. Quality assurance comes from quality attributes verified with checklists in iterative cycles. Then, process mapping contributes both to producing consistent artifacts to better communications within the project. This article presents a methodology for quality assurance of process modeling that can be applied for the development of large computer systems. The methodology was used in a complex case study, with the mapping of business processes using BPMN, to develop a system for human resources management within the Ministry of Planning, Budget and Management (MPOG) in Brazil.

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

[2]  Reinhold Plösch,et al.  The Value of Software Documentation Quality , 2014, 2014 14th International Conference on Quality Software.

[3]  C. Wongwatkit,et al.  A development of order processing system: BPMN model , 2012, 2012 14th International Conference on Advanced Communication Technology (ICACT).

[4]  Michael E. Fagan Design and Code Inspections to Reduce Errors in Program Development , 1976, IBM Syst. J..

[5]  Maristela Holanda,et al.  Business process modelling: A study case within the Brazilian Ministry of Planning, Budgeting and Management , 2014, 2014 9th Iberian Conference on Information Systems and Technologies (CISTI).

[6]  Peter Gyngell,et al.  Process Innovation: Reengineering Work through Information Technology , 1994 .

[7]  Dirk Muthig,et al.  A view-based approach for improving software documentation practices , 2006, 13th Annual IEEE International Symposium and Workshop on Engineering of Computer-Based Systems (ECBS'06).

[8]  Howard Smith,et al.  Business Process Management: The Third Wave , 2003 .

[9]  Maristela Holanda,et al.  Software documentation quality: A case study for the software documentation of SIGEPE , 2015, 2015 10th Iberian Conference on Information Systems and Technologies (CISTI).

[10]  James R. Lyle,et al.  A Two-Person Inspection Method to Improve Prog ramming Productivity , 1989, IEEE Transactions on Software Engineering.

[11]  Wei-Tek Tsai,et al.  N-Fold inspection: a requirements analysis technique , 1990, Commun. ACM.

[12]  Claes Wohlin,et al.  An Experimental Comparison of Usage-Based and Checklist-Based Reading , 2003, IEEE Trans. Software Eng..

[13]  V. Daniel Hunt,et al.  Process Mapping: How to Reengineer Your Business Processes , 1996 .

[14]  B BisantDavid,et al.  A Two-Person Inspection Method to Improve Programming Productivity , 1989 .

[15]  Peng Liang,et al.  Knowledge-based approaches in software documentation: A systematic literature review , 2014, Inf. Softw. Technol..

[16]  Jan Recker,et al.  Opportunities and constraints: the current struggle with BPMN , 2010, Bus. Process. Manag. J..