Artifact-based vs. human-perceived understandability and modifiability of refactored business processes: An experiment

Caivano, Danilo; Fernández-Ropero, María; Pérez‐Castillo, Ricardo; Piattini, Mario; Scalera, Michele

doi:10.1016/j.jss.2018.06.026

Cited by 14 publications

(9 citation statements)

References 20 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…(iii) ird, generated processes are raw results that may lack a certain quality with respect to comprehensibility and modifiability. In this sense, we could consider enriching the transformation algorithms by means of refactoring techniques [40][41][42] so that human-perceived quality measures could be improved. (iv) Finally, we aim to generate standard event logs, such as XES format [19], for Non-PAISs.…”

Section: Discussionmentioning

confidence: 99%

“…e BPD approach can generate business processes of different sizes and structures that may be characterized by connectivity, density, and separability of artifacts. Generated processes may recurrently present disadvantages regarding quality parameters such as comprehensibility and modifiability [40]. Process refactoring [40][41][42] includes techniques to write alternative process instances by adding, deleting, or redistributing existing process artifacts.…”

mentioning

confidence: 99%

“…Generated processes may recurrently present disadvantages regarding quality parameters such as comprehensibility and modifiability [40]. Process refactoring [40][41][42] includes techniques to write alternative process instances by adding, deleting, or redistributing existing process artifacts. Artifacts may be activities, gateways, events, or control flows.…”

mentioning

confidence: 99%

“…Refactoring processes quality is evaluated using artifact-based measurements. Caivano et al [40] evaluate the process quality perceived by experts (human-perceived measures). ey compare both, artifactbased and human-perceived quality measures to conclude that "Process refactoring is worthwhile so that humans reach better levels of comprehensibility and modifiability.…”

mentioning

confidence: 99%

“…Generated BP: "Activity #64 SA of Facilities and Equipment." Control Flow of Activities and Time Rules (TCs and TDs) extracted from the project plan.possibility of enriching the transformation algorithms with process refactoring patterns to improve the quality of them regarding parameters such as comprehensibility and modifiability[40][41][42].…”

mentioning

confidence: 99%

See 4 more Smart Citations

Practical Experiences in the Use of Pattern-Recognition Strategies to Transform Software Project Plans into Software Business Processes of Information Technology Companies

Arévalo

Ramos

Gutiérrez

et al. 2019

Scientific Programming

View full text Add to dashboard Cite

Business process management (BPM) is a strategic advantage for all kinds of organizations, including information technology companies (ITCs), which cannot stay out of the BPM approach. ITCs manage business processes like projects to create and maintain software. Although Project Management Systems (PMSs), such as Microsoft™ Project Server® (MPS®), are considered as non-process-aware information systems (Non-PAISs), they may be a source to generate processes. In this paper, we propose a reverse engineering approach, which uses patterns to transform software projects stored in MPS® legacy databases into software business processes. For this, we base on the model-driven engineering paradigm and deal with the time perspective of the processes. This kind of experiences are scarce or almost nonexistent, so we show the AQUA-WS project case study, which runs with MPS® as source system and software process modeling languages as target systems. ITCs can benefit from this research by gathering knowledge about perspectives of their processes that would otherwise be wasted, such as executed projects or expired documents used in Non-PAISs. This fact can become a key factor for ITCs, which can increase their competitiveness and reduce software costs, as part of the BPM lifecycle of continuous improvement.

show abstract

Section: Discussionmentioning

confidence: 99%

mentioning

confidence: 99%

mentioning

confidence: 99%

mentioning

confidence: 99%

mentioning

confidence: 99%

See 3 more Smart Citations