Preprint Article Version 1 This version is not peer-reviewed

Using Logs to Mitigate Process Variability and Reliance on Practitioners in Traditional Business Process Automation Software

Version 1 : Received: 8 August 2024 / Approved: 11 August 2024 / Online: 12 August 2024 (10:42:04 CEST)

How to cite: Menezes, T. M. D.; Salgado, A. C. Using Logs to Mitigate Process Variability and Reliance on Practitioners in Traditional Business Process Automation Software. Preprints 2024, 2024080776. https://doi.org/10.20944/preprints202408.0776.v1 Menezes, T. M. D.; Salgado, A. C. Using Logs to Mitigate Process Variability and Reliance on Practitioners in Traditional Business Process Automation Software. Preprints 2024, 2024080776. https://doi.org/10.20944/preprints202408.0776.v1

Abstract

Context: Business Process Automation (BPA) is adopted by organizations to improve efficiency, reduce costs, and increase overall business performance. Traditional Business Process Automation (TBPA) is one of the three approaches employed to develop a BPA. TBPA entails developing BPA in a programming language for integrating the relevant applications in the digital ecosystem to execute a given process. Process variability and practitioner unavailability encumber the requirements specification for TBPA software. Objective: This work proposes a log-based approach for TBPA software to make software more adaptable to process changes and reduce reliance on practitioners, by providing a higher alignment among business process requirements and software architecture, and employing process mining to semi-automatically discover the business process during requirements elicitation. Method: The research conducted a case study in a technology institute to assess the approach and report its results in practice. Results: The results revealed significant improvements in adaptability to business process changes and decreased the time spent with practitioners, and, efficiency in development. The approach also presented limitations, including human intervention to accurately obtain the business process, complexity to trace the process into the architecture, data privacy concerns, and risk of network traffic overload. Conclusion: This research demonstrated the effectiveness of traceability between process requirements and software architecture, as well as the use of logs and process mining. These methods made TBPA software enhanced the software adaptability to changes and minimized the reliance on practitioners during requirements elicitation respectively.

Keywords

Business Process Automation; Requirements Engineering; requirements specification; software architecture; software design; software development; software engineering

Subject

Computer Science and Mathematics, Information Systems

Comments (0)

We encourage comments and feedback from a broad range of readers. See criteria for comments and our Diversity statement.

Leave a public comment
Send a private comment to the author(s)
* All users must log in before leaving a comment
Views 0
Downloads 0
Comments 0


×
Alerts
Notify me about updates to this article or when a peer-reviewed version is published.
We use cookies on our website to ensure you get the best experience.
Read more about our cookies here.