Interaction Design. Sequence diagrams were designed for three common scenarios of the monitoring system: starting the monitoring of a new SLA, requesting a monitoring report, and responding to a monitoring event. For the first scenario, starting the monitoring of an SLA (see Figure 7.3), we assume that an SLA has been constructed using the DSL described earlier. The user first exports the monitoring specification and uploads it the the orchestrator component. The orchestrator then passes the specification to the monitor component, which start by parsing the monitoring specification and storing the result. This process also registers it as an active SLA if its validity is correct. A confirmation is then returned to the user. The second scenario, obtaining a report (see Figure 7.4), starts with a request from the user or client to the orchestrator. The orchestrator then tells the monitor to obtain the required data. The monitor fetches the SLA and determines which operations are required to obtain all the data. It then performs all the required operations and stores them. The orchestrator then requests analysis by the analyser, which starts by fetching the monitoring data and SLA. It then uses its expression solver to check every agreement in the SLA. The result of this analysis is again stored and an identifier is returned to the orchestrator. The orchestrator then tells the explainer to process the analysis result into a report. The explainer first fetches the analysis result and the SLA, and uses these to create a report. This report is stored and an identifier is returned to the orchestrator, which fetches the report and returns it to the user. <<controller>> Orchestrator <<service>> Monitor <<service>> Explainer [for each operation] retrieveData data monitoringDataId [for each agreement] getReport report Figure 7.4: Sequence diagram for obtaining a report from the monitoring system. receiveEvent getSla determineOperations loop analyseResults getMonitoringData getSla determineAgreements loop storeAnalysisResult analysisResultId explainResults getNotification notify ionId notificat fy noti <<service>> Explainer <<service>> Analyser <<controller>> Orchestrator <<service>> Monitor Service Figure 7.5: Sequence diagram of an event-based monitoring situation. The third scenario, responding to a monitoring event (see Figure 7.5), starts with a situation where the service wants real-time decision support. To obtain this, it sends an event to the monitor, which checks it with the re...
Interaction Design. Other design support work related to information system construction. Data processing services include but are not limited to：
