This is a guest blog from Fabian Kainzinger (iteratec) – for more see iteraplan blog.
Connections and dependencies of infrastructure elements are simply and effectively modelled using the extended iteraplan meta model: iteraplan 3.1 now supports the usage-relation for infrastructure elements.
Relations between elements of the same building block type differ semantically. iteraplan supports the following kinds of relations: ‘usage’, ‘hierarchy’, ‘successor’ and ‘specialisation’. It depends on the building block type which of these self-referencing relations is available. Starting with iteraplan 3.1 the usage-relation is now available for infrastructure elements. It supports a n:m assignment between infrastructure elements.
Example scenario for the usage-relation
Hence a scenario as follows can be modeled and visualisized: A server environment uses storage components of different availability classes. The server environment itself has multiple availability classes. The respective dependencies between server and storage are modeled via the usage-relation. The hierarchy relation can be used independently from the usage-relation e.g. to document virtualisation or clusters.