Stakeholders

A number of generically named stakeholders. Stakeholders have concerns and requirements for the use of an architecture repository. However, they do not necessarily have to be a participant in the project that introduces the architecture repository. Please note that this is often organization specific in nature. In this model only a number of generic stakeholders are named. Therefore, feel free to adapt this model to your own context so that it corresponds to the stakeholders relevant within your organization.

Diagram in standard mode

Management organization

From an architectural perspective, management organization is important for providing frameworks and guidelines regarding the management of the various artifacts and described in the various architectures.


Details van Management organization

Development teams

If architectures are implemented in custom solutions, the developers of these custom solutions will, on the one hand, provide frameworks and guidelines for the architecture and, on the other hand, they will be consumers of the architecture artifacts and implement them in functioning solutions.


Details van Development teams

Project managers

Changes in the organization are often introduced into the organization on a project-by-project basis. Projects determine the planning and execution of the architecture work and make use of the architecture artifacts. The projects set requirements for the support from architecture and the products to be delivered by the architecture.


Details van Project managers

Legislation and compliance

I regard legislators and compliance institutions as invisible stakeholders. However, they set frameworks for the architectures within the organization. This makes them highly relevant stakeholders. Consider, for example, the GDPR.


Details van Legislation and compliance

Management

Management indicates what the goals and drivers are of the organization. The frameworks for architecture arise from this. In addition, management determines the order of the architectural work to be carried out.


Details van Management

User organization

User organization indicates which requirements, wishes and limitations exist regarding the artifacts to be developed within the architecture and the resulting implementations to the target architecture.


Details van User organization

Sectoral reference architectures

Sectoral reference architectures have already been drawn up within some sectors, such as the reference architectures within national and international governments (EU). The architectures established within it are a precondition for the architectures within your own organization.


Details van Sectoral reference architectures

Supplier

More and more organizations are opting for standard solutions for the design of the various architectures. In this case, the supplier of these solutions involved is a stakeholder from the perspective of supplying certain solutions and a customer of the architectural artifacts.


Details van Supplier

Modeling teams

Depending on the structure of the organization, (partial) models are developed by different teams with different roles in addition to the architects. For example, information analyst, data modeler, software development teams, etc.


Details van Modeling teams

Architecture team

Team that will use the architecture tool in the architecture processes. They are therefore not only stakeholders but also play an important role in the processes.


Details van Architecture team