## 4 Use Case
### Systematic Approach for SCVAD Modeling
#### 4.3.1 Adverse Process Modeling
The mutually exclusive execution of activities AE1.1, AE1.2, or AE1.3 triggers the 'final diagnosis of pump thrombosis (AE1)', and the termination of the adverse process AE1 is determined by the timing executed by the 'time counting' activity. As illustrated in Figure 11, the simultaneous execution of the activities'symptoms of HF or persistent low flow', 'abrupt drop in blood flow', and 'abrupt drop in power consumption' enables the identification of pre-pump thrombosis and records this information through the execution of the 'database registration' activity. Figure 12 illustrates the introduction of control elements and resources for sharing and representing data flow with the external environment. As illustrated in Figure 13, the simultaneous execution of the activities 'high power consumption','symptoms of hemolysis', and 'pump with vibration signals' enables the identification of intra-pump thrombosis and records the information through the execution of the 'database registration' activity. Figure 14 illustrates the introduction of control elements and resources for sharing and representing data flow with the external environment. As illustrated in Figure 15, the simultaneous execution of the activities'symptoms of HF or persistent low flow','slow decrease in blood flow', and'slow decrease in power consumption' enables the diagnosis of the thrombosis location (anastomosis stenosis or obstruction at the outflow cannula) through the execution of the 'echocardiographic diagnosis' activity and subsequent recording of the post-pump thrombosis through the execution of the 'database registration' activity. Figure 16 illustrates the introduction of control elements and resources for sharing and representing data flow with the external environment. Figure 16: PN corresponding to the adverse activity ‘post-pump thrombosis AE1.3’. Figure 15: PFS and detailing of the adverse activity ‘post-pump thrombosis AE1.3’. Finally, the diagnosis is carried out according to the logic described in the PFS model presented in Figure 17, considering the adverse activities 'pre-pump thrombosis AE1.1', 'intra-pump thrombosis AE1.2', or 'post-pump thrombosis AE1.3' detailed in the PN as illustrated in Figure 18. The conclusion of the adverse process AE1 is triggered by the execution of the activity 'final diagnosis of pump thrombosis (AE1)' concurrently with the execution of the 'time count' activity presented in Figure 12.0  
Figure 12.1 PFS and detailing of the activity ‘time counting’. Figure 12.2 PFS and detailing of the activity ‘final diagnosis of pump thrombosis (AE1)’. Figure 12.3 PN corresponds to the ‘final diagnosis of pump thrombosis (AE1)’ activity. As illustrated in Figure 17, following the execution of the 'database access' activity, information is collected to diagnose one of the adverse activities AE1.1, AE1.2, or AE1.3. Subsequently, the diagnosis of the adverse process AE1 is finalized and registered. Figure 18 illustrates the introduction of control elements and resources for sharing and representing data flow with the external environment. As shown in Figure 19, two sequential activities were specified for monitoring the maximum allowable time for patient care, namely,'start of counting time' and 'end of counting time'. The maximum patient care time is monitored using a countdown timer with watchdog logic. The medical team also interacts with the diagnostic modules, allowing the time count to be aborted by medical decisions if the adverse process deteriorates before the maximum allowed time is reached. The model in PFS for the 'end of time count' activity is shown in Figure 20, and the corresponding PN is shown in Figure 12.4  
As illustrated in Figure 20, two mutually exclusive activities determine the end of the time count, namely,'maximum time', triggered by a countdown timer, and 'abort time Count', which can be triggered at any time by the medical team's command. Figure 21 shows the introduction of control elements and resources for sharing and representing data flow with the external environment.