This Meta Model customization has been created with the aim to embrace various Cloud Services providers’ solutions. In this customization, cloud services are “first” provider agnostic (they appear as “green cloud” symbols), but at time the provider is defined for a “Cloud Architecture Diagram”, the symbols in the diagram adapt their appearance to the corresponding symbol of the provider, as characterized along categories and instances defined for this provider.

The providers that QualiWare currently support are:

Using the Cloud Services Meta Model

The goal in using this Meta Model, is not only to describe and manage the cloud architecture knowledge, but also to relate the described and modeled cloud services elements to the Enterprise Architecture elements which have been defined, described, modeled prior to define the operational cloud implementation.

The guidance provided below is based on a set of use cases which aim at defining, describing and modeling a “Cloud Architecture Diagram”, and the embedded “Groupings”, Services and Flows, as well as managing the reference relationships to Enterprise Architecture elements.

Defining a “Cloud Architecture Diagram”

The QLM user creates a new “CloudArchitectureDiagram” the same way as for any other diagram he/she is used with. Then by opening this diagram for the first time, the user is asked to associate it to the Cloud Provider as on the image.

This is explained in our Cloud Architecture Diagram

Clustering

Clustering provides users with a new way of interacting with content in their repository. It provides an enhanced analysis capability directly from the 3D Visualizer by logically grouping objects based on their relationships, concepts, and definitions. Filters can be applied to the clusters through the table-based view using existing functionality to focus analysis efforts (for example only clustering objects that are related to a risk with a high impact). The number of clusters can also be defined by the user to provide a broader or more concise result.

API Architecture Metamodel

An Application Programming Interface (API) is a construct that enables communication between systems. Integration between systems in complex environments continues to be a business priority to support automation activities. An API can be purpose-built for a bespoke integration (typical of legacy systems), or alternatively a standard connector can be developed between industry standard systems such as ERP’s and Service Management platforms. Managing these integrations becomes a complex operational task as updates and new releases to the integrated systems (and enabling technologies), can lead to intensive release management and testing activities. Security is also of utmost concern when managing integrations as the API provides a potential entry-point from either system integration direction – the API has become a preferred target for malicious attacks on systems and networks.

Ontologies in QualiWare

This page is intended to help users model knowledge using the QualiWare GOWL implementation delivered in release 10.8 of QualiWare.

Using the Cloud Services Meta Model

Defining a “Cloud Architecture Diagram”

Related Posts

Clustering

API Architecture Metamodel

Ontologies in QualiWare