Reference Architectures are “standardized architectures that offer a reference framework for a specific domain, sector, or area of interest.” A reference model provides a clear, often one-page, overview of the domain in question—something that is reusable and can, of course, be adapted to fit the organization’s needs. Examples of reference model types include the Business Reference Model (BRM), Technology Reference Model (TRM), and the Information Reference Model (IRM).
ALSO READ: The value of Reference Architectures
There are numerous industry reference models available for public use, but the real value comes from taking these models and transforming them into reference models tailored to the organization. These customized models can foster discussions, encourage reuse, and offer traceability to other parts of the architecture.
Reference models often begin as a Microsoft PowerPoint slide, a Visio diagram, or even as populated cells in an Excel spreadsheet. While this works well for communication and conveys the message effectively on a one-off basis, in Enterprise Architecture, reference models are rarely used in isolation. They must be connected to other areas, so we must use a standard to link the reference model elements, such as ArchiMate.
A common question arises: “What concept should I use to represent the ‘blocks’ in this reference model?”
This area can lead to days or even weeks of discussion. However, arguing over this point defeats the purpose of using reference models to provide a clear and consistent framework. We need to agree on the representation and then apply it consistently. To answer this question, we must closely examine the specific reference model. I’ll refer back to the three examples mentioned earlier.
Essentially, when describing the ‘Business on-a-page’, we decompose higher-level ‘areas’ into sub-areas, and then further into more detailed components. It should define “what the organization does,” which often offers a significant hint.
For those with at least a basic understanding of ArchiMate, the model is likely outlining some form of ‘behavior,’ and this behavior should be business-oriented in nature. This points to a Business Function!
Microsoft Industry Reference Architecture for Banking
Like the Business Reference Model, the Technology Reference Model typically describes ‘Infrastructure on-a-page’, but again in a more functional perspective – it should not be about the fine-level of detail of server x, y and z, processors and that type of technical information.
Considering these points, we are again looking at Infrastructure Services and Infrastructure Functions (i.e., behavior).
The Cloud Ecosystem Reference Model
So far in the two examples above, we notice that ‘behavior’ concepts appear to be used – this is usually the case for a range of reference models. ‘Structural’ concepts usually tie closer to implementation after all.
The Information Reference Model describes the common ‘information’ available within the organization (something like the TM Forum SID is good inspiration). Putting it into perspective, the use of behavioral concepts does not fit – thus, we logically look at the ‘passive structure’ column (which describes ‘objects’ of some sort).
As the ArchiMate stalwarts are aware, there could be a decision to make on whether we use Business Objects or Data Objects to represent the elements of the Information Reference Model. This, again, is subject to interpretation, but generally, something as high-level as ‘information’ may best sit as a Business Object.
The Information Framework (SID)
You can use various ArchiMate concepts to represent elements in reference models. Still, the key is to agree on a standard and stick to it, ensuring consistency in its application and sharing the results. Using the right enterprise architecture tool is crucial in this process, as it helps to design reference architectures effectively and ensures that all elements are accurately represented, which is essential for performing impact analysis and maintaining validity across the architecture.
ALSO READ: Choosing the right enterprise architecture tool
One final point focuses on presenting to ‘non-technical’ stakeholders. While architects may create reference models using standardized ArchiMate notation to establish valid relationships and enable impact analysis, there is no reason why the output cannot be tailored for the audience. For example, it could be presented in a simplified or ‘inform’ type viewpoint that is more accessible to non-technical stakeholders.
