# Process Automation and Blockchain in Intelligence and Investigation Units: An Approach
## 5 Evaluation, Results, and Discussions
### Survey with Specialists
Survey Results  
Figure 13 presents the profile of the 52 specialists who participated in the survey, specifically with regard to the time they were in the organization (years) and their experience in carrying out or supporting intelligence and investigation activities (years). Regarding the academic qualifications of the participants, Figure 14 shows the distribution of the participants by the graduation level. It should be added that, of the specialists who answered the survey, none had experience with methodologies and techniques of process automation. Regarding the answers to the research questions, Figure 15 shows the distribution of the participants' answers per question. The survey showed that 96.15% of the experts who participated agreed that the approach could be performed by business analysts without process automation technical expertise (there were no disagreements, however 3.85% of the participants did not decide whether they agree or not). Positive results (without disagreements) were also identified in the answers to RQ2 (92.31%), RQ4 (92.31%), RQ5 (98.08%), RQ6 (94.23%), RQ7 (96.15%), and RQ9 (88.46%). Regarding the properties and techniques adopted in the potential analysis and priority index calculation of internal processes, 82.7% of the participants agreed that they were applicable and sufficient for the considered scenario. However, 7.68% disagreed and 9.62% remained undecided. Figure 13: Quantitative distribution of specialists by time (in years) in the organization and experience in carrying out or supporting intelligence and investigation activities. Of the four participants who disagreed, none questioned evaluation methods for automation. Concerning the calculation of the priority index, they mentioned that the complexity is not limited only to the execution time. They added that complexity, at least in the scenario in which they operate, is a characteristic that allows them to analyze the degree of difficulty in understanding and explaining a process. The number of existing activities, the number of parallel branches and the existence of loops are examples of characteristics that allow this measurement. For the case of the approach in question, the specialists recommended changing the name of the property to \"execution time\". They agreed that two properties (i.e., transaction volume and time to complete the process) are sufficient for the proposed objective of the approach within of the studied context, and that allows the adoption by users that do not have technical expertise with process automation. Another alternative recommendation is to keep the name of the property as \"complexity\", but provide instructions or recommendations to interested parties regarding the consideration, not only for the process execution time but for the adoption of other metrics that allow for the identification and classification of processes regarding its complexity, such as McCabe's cyclomatic complexity (MCC), cognitive weight and number of activities in a process (NOA) [92; 93]. Following the recommendation of the participants, the name of the property (complexity) was maintained, but instructions/recommendations were added regarding the possibility of including new complexity measurements (in addition to the use of time to complete the process) for users with the intention to adopt the calculation. The additions were included as optional documentation because they contribute to the increase in complexity, application time, or difficulty in using the approach. The use of the time to complete the process was considered applicable and sufficient for the context studied and expected objective. There were also disagreements regarding the common understanding of the results after carrying out the approach. Although 73.07% of participants agreed (9.62% remained undecided), 17.31% of participants found that documenting the results after executing the approach is confusing and that the documentation with instructions for use could contain illustrative examples for better understanding.