next up previous
Next: 3 OMT-based design of Up: 2 Management model of Previous: 2.3 Bottom-up Approach: Ensuring

2.4 Application of GAMOCs

The GAMOCs defined according to the previous sections are generic in the sense that they (intentionally) do not contain any specifics for certain applications. In order to support the management of a concrete application, they of course have to be further refined.

Consider the following situation: Given is an application modeled according to the ODP viewpoint concepts, i.e. compliant to the RM-ODP. From this application, take especially the computational and engineering specification and use the information contained therein to instantiate generic information in the GAMOCs. Step three of the approach as mentioned above ensures that enough information is present in these specifications. For example, information in the GAMOCs related to the names of processes which have to be monitored in order to ensure availability can now be set to appropriate default values.

Now that we have sketched the whole process of the definition of GAMOCs, we have to focus on a concrete technique that we can use to model these classes and on tool support for this activity. In the following sections we describe the use of OMT and our experiences with bringing these classes to life, that is implementing the model as distributed CORBA objects.


next up previous
Next: 3 OMT-based design of Up: 2 Management model of Previous: 2.3 Bottom-up Approach: Ensuring
Copyright Munich Network Management Team