## 4 Integrative Example
### The Game Stream Service  
The _PER_ of this profile was set to 60, as video games usually maintain a frame rate of around 30 to 60 FPS (images or frames per second) to reflect the quality of service (the perceived quality by the user) that these types of applications strive for [36]. Our Default Run Probability was set to 0 and our stop probability to 0 because the instance of this profile is always triggered by one of its operations. The parameters, available in Table 8, have a size relative to the network requirement of the application: 25 Mbits/second or 0.00468 MB per millisecond. When the parameters' direction is set to \"external\", they can be accounted for as network consumption, reducing the need for creating more profiles. \begin{table}
\begin{tabular}{c c c c} \hline \hline
**Cycle** & **Timed Exp.** & **Min. Run Time (s)** & **Max. Run Time (s)** \\ \hline
1 & 1 & 1800 & 3600 \\ \hline
1 & 2 & 0 & 3600 \\ \hline
1 & 3 & 1800 & 3600 \\ \hline
2 & 2 & 1800 & 3600 \\ \hline
2 & 3 & 3600 & 3600 \\ \hline \hline \end{tabular}
\end{table} 
Table 6: Catalog Service: run constraints per timed expectation per cycle. \begin{table}
\begin{tabular}{c c} \hline \hline
**Operation ID** & **Description** \\ \hline
1 & Selected game initialization \\ \hline
**(b)** Triggers \\ \hline
**Value (ID)** & **Type** \\ \hline Run & State \\ \hline
**(c)** Results \\ \hline
**Parameter ID** & **Operation ID** \\ \hline
1 & 2 \\ \hline \end{tabular}
\end{table} 
Table 7: Catalog Service: the description, triggers, and results of operation 1. \begin{table}
\begin{tabular}{c c c c c c c c c c c c} \hline \hline
**Cycle** & **Timed Exp.** & **Run Prob.** & **Stop Prob.** & **Elasticity** & **Min. Run** & **Max Run** & **Min. Stop** & **Max. Stop** & **Neg. Run** & **Pos. Run** & **Neg. Stop** & **Pos. Stop** \\
1 & **Override** & **Override** & **Override** & **Prob.** & **Prob.** & **Prob.** & **Prob.** & **Prob.** & **Prob. Mod.** & **Prob. Mod.** & **Prob. Mod.** \\ \hline
1 & 1 & 0.1 & 0.9 & True & 0 & 0 & 0 & 0 & 0.001 & 0 & 0 & 0 \\ \hline
1 & 2 & 0 & 1 & False & 0 & 0 & 0 & 0 & 0 & 0 & 0 & 0 \\ \hline
1 & 3 & 0.7 & 0.4 & True & 0.3 & 0.8 & 0 & 1 & 0.05 & 0.05 & 0.05 & 0.05 \\ \hline
2 & 1 & 0.3 & 0.2 & False & 0 & 0 & 0 & 0 & 0 & 0 & 0 & 0 \\ \hline
2 & 2 & 0.7 & 0.4 & True & 0.3 & 0.8 & 0 & 1 & 0.05 & 0.05 & 0.05 & 0.05 \\ \hline
2 & 3 & 0.8 & 0.1 & True & 0.3 & 0.8 & 0 & 1 & 0.05 & 0.05 & 0.05 & 0.05 \\ \hline \hline \end{tabular}
\end{table} 
Table 5: Catalog Service: elasticity constraints per timed expectation. The operations in this profile, as defined in Table 9, hold a circular relationship among them. This results in the operational loop illustrated in the diagram of Figure 7, where the parameters, triggers, and results match the definitions above. In addition to this, we set a maximum and minimum amount of time the operations can be sustained (in seconds) in compliance with the time constraints of the business model. To conclude the modeling of the Game Stream Service, we populated the operations with hardware consumption values, a fundamental part of the BBCP. The values were taken from the official system requirements found on the application's webpage ([[https://www.nvidia.com/en-eu/geforce-now/system-reqs/](https://www.nvidia.com/en-eu/geforce-now/system-reqs/)]([https://www.nvidia.com/en-eu/geforce-now/system-reqs/](https://www.nvidia.com/en-eu/geforce-now/system-reqs/)), accessed on 2 August 2024), considering 60 frames per second at a 1080 p image resolution as our target performance and a computer with Windows as the consumer platform. The storage consumption was excluded, as it does not appear to have a minimal requirement during run time.