System Architect now includes full support for TOGAF 9.1. Included are new symbol types, definition types, and definition properties.

For complete description of TOGAF, go to The Open Group website.

The following new definition types have been added in this release:

The purpose of the Cluster definition is to show the physical grouping of configuration items so that they appear as a single node or resource on the network. Clustering is most often associated with databases and servers. A Cluster is at the same level of abstraction as (physical) Technology Component. A Cluster can have deployed Cluster Instances.

The purpose of the Cluster Instance definition is to show the deployment of a Cluster. Cluster Instances can be represented as “cluster instance" symbols on the Network Infrastructure diagram. A Cluster Instance is at the same level of abstraction as other Configuration Item subtypes (Server Instance, Database Instance, Device Instance, Operating System Instance, Physical Application Component Instance, Physical Technology Component Instance).

A Cluster Instance can be linked to one Cluster. The composition of a Cluster Instance is defined by the Cluster definition.

The purpose of the Network definition is to define the range of IP addresses that can be assigned to hosts and to enable users to model physically distinct networks, such as DEV and PROD, as reflected by their deployment environment. A Network can comprise multiple Subnetworks. There is no symbol for Network; it exists as a definition type only.

The purpose of the Subnetwork definition is to model the logical subdivisions of an IP network. The associated symbol type is assigned to the Network Infrastructure diagram and is represented as a swim lane. Subnetworks can be used to model intranets, DMZ areas and extranets.

This symbol type represents the Cluster Instance definition type.

This symbol type represents the Subnetwork definition type. It is represented as a swim lane. Swim lanes can be oriented horizontally or vertically, based on a diagram property.

The following new definition properties have been added in this release:

The Contains Named Configuration Items property is now a mirrored property. The name of the mirrored property is Contained in Configuration Items. For example, if a Physical Application Component Instance is placed on a Server Instance (via the Contains Named Configuration Items property), then the Contained in Configuration Items property in the Physical Application Component Instance definition will also reflect this.

The CI Relationship is an explicit relationship that can be drawn between any Configuration Item subtype on a Network Infrastructure diagram. With version 11.4.3.5, you can also draw a CI Relationship between Cluster Instances and Configuration Item subtypes.

Network and Subnetwork are new definition types in 11.4.3.5. The properties of these definitions enable support for IPv4 and IPv6 addressing formats. Specifically, you can enter an IPv4 Network ID, such as 123.456.789.012.

IPv6 addresses are defined as 128 bits and are typically expressed in double-byte groups that are delimited by colons. The first 48 bits represent the global routing prefix. The value for an IPv6 routing prefix can be entered into the Routing Prefix (IPv6) property of the Network definition.

Two properties in the Subnetwork definition support IPv4 and IPv6 addressing: Subnet Mask (IPv4) and Subnet Address (IPv6), respectively.

A reference property has been added to the Physical Technology Component Type definition to link it to a Technology Component whose Is Physical property is False (that is, a Logical Technology Component).

The relationship type between Physical Technology Component Type and Logical Technology Component is “realizes”, as in a Physical Technology Component Type realizes a Logical Technology Component.

The purpose for adding this property and relationship is to provide support for a taxonomy of technologies.