Introduction

A beloved child bear many names. The word “IT Architect” is term that is used often and is a term that is covering a lot. We have defined six more specific architect roles to make it more precise which competences that are in demand in the specific activities in the FDA. An ”IT architect” can, in principle, cover one or more (but rarely all) of these six roles. 

Many organizations – especially the public ones – do not have any employees with a title where Architect is part of the title in relation to IT and digitalization. More often, the title is IT Chief, Consultant, Project Manager or Developer. In other organizations – especially in IT vendor companies – you have IT Architects, Solution Architects or Security Architects. You could easily have defined other roles, than the six we describe here. But our goal is to create a connection to the most used Architectural frameworks. The examples above will typically manage one or more of the six roles, that we have defined. On the other hand, the six roles have a responsibility to ensure the solution is well connected and that security is handled in a good way.

The six roles

  • Enterprise Architect – focus on the proactive in maintaining the Enterprise Architecture in order to have overview over the connections and to involve technical experts when needed.
  • Business Architect - focus on analysis, modelling and optimal processes in order to support business processes.
  • Information Architect – focus on information modelling and database structures.
  • Application Architect – focus on applications and services.
  • Technology Architect – focus on the technological infrastructure and the technical sides of databases and applications.
  • Solution Architect - focus on implementation of solutions in the organizations.

Application

FDA do not describe the level of relations between the roles that need to be in place for a project, and does not describe how and if the roles can be combined. It is not likely to have an ”IT Architect” that have all six roles. On the other hand, is it not expected that every organization has (at least) six full year architect employees, hired in.

It is important to notice that the goal is to describe which competences the different roles is expected to have, and even though you will find guidance to what the different roles is named, it is not the goal to discuss titles, specific job profiles or the amount of full-time employees that is needed.

The need for the roles is dependant of the kind of architecture project that needs to be done. If there only is limited need for a specific competence, it might be worthwhile to hire in an external, whereas it will make sense to hire, or use, internal resources to the more broadly used roles in the architectural project.

About the role descriptions

Each role is described completely systematically and aligned, with the following point:

  • Description – what is the exact and most important architect roles tasks in the Architecture project?
  • Competence profile – which competences will the role typically have?
  • Good advice – further statement to whom that will typically possess the role.

 

Approach

The roles are made with input from different sources and methods like TOGAF and FDA, literature and experience, that is found relevant to be used in an Enterprise Architecture project.

The six roles are weighted based on two business related-, six general- and three technical competences. The competence levels are weighted on a scale from 0 – 5, where 1 is no knowledge (not relevant) and 5 is an expert (need high class competences). We have used half measures as well, to be more precise in the measure of competences.


Last updated 2020-12-23 by the Advisory Board for Danish IT Society Architecture Certification.


Competences

Competence Levels