Figure An.03 - Anomaly Management Entity Details

<font color="#29313b">The following diagram further defines the Anomaly and AnomalySpecification classes with its associated entities and attributes. Anomaly class and its derivatives represent the administrative view of the particular Anomaly being managed and will be compliant with the AnomalySpecification throughout its lifecycle. In addition to this each Anomaly also contains additional composed entities such as AnomalyCategory, AnomalyGrouping etc which has corresponding specifications to define the characteristics. Anomaly operational state is reported through AnomalyReport. The component that act on the AnomalyReport , for example  a specialized ClosedLoop controls the operational state depending on the contextual information ,  policy or the workflow associated with the closed loop. It is assumed that closed loop can be realized using an orchestration pattern or a choreography pattern. In an orchestrated closed loop, the specific workflows control the anomaly management operational sequence, whereas in a choreographed closed loop the anomaly management is controlled by a predefined configuration and event patterns being exchanged by specialized components. </font><br/><br/>