A reference architecture is an abstract architecture in which a number of generic frameworks or building blocks are described. Organization-specific (domain and solution) architectures are drawn up based on reference architectures.

There is one central location within XXX (the central D&A environment) for receiving, storing, validating, processing, modeling, integrating and delivering current and historical data and information products from various external and internal (XXX) sources and domains. . The data foundation/data hub is not intended as a conduit for data. Data foundation adds value to the data flow. The central data foundation functions in two ways: as a 'data hub' function and as a DWH/dashboard and reporting function. Both are fully aligned and therefore we use "a single source of truth" both in your planning and in steering based on the realization.

Name=[Graydon] e-mail bijlagen klaarzetten;Type=Activity;

A component is part op the active structure and the application layer

Name=113801 - RWS project Masterplan Eindhoven;Type=Package;

Name=114306 - LSA;Type=Package;

Name=114663 - WBSO - UP-NL;Type=Package;

Development and preferably deployment of AA / AI models takes place in the central D&A environment. For performance, privacy or data availability reasons, it may be necessary to deploy the models decentrally.

Architecture Building Block.

Catalog of Architecture Building Blocks with which a number of services can be realized. The catalog functions as an additional form of navigation for future users

Abstract Logical data entity is a hierarchical division of logical data entities. With the help of specialization, the characteristics of an abstract logical data entity are transferred to a concrete data entity. So attribute 1-3 is also an attribute of the concrete logical data entity. Multiple hierarchies can be created based on multiple specialization connections between data entities.

The technique of providing summarized or generalized descriptions of detailed and complex content.

A person, organization, or system that has one or more roles that initiates or interacts with activities; for example, a sales representative who travels to visit customers. Actors may be internal or external to an organization.

Architecture Development Method.

Management of personal and shared agendas.

In the previous chapters we discussed the different dimensions of introducing an Architecture Repository. In this chapter we discuss a number of tools that support and simplify the introduction of an architecture repository. We are working on this based on Sparx Enterprise Architect, a modeling tool for various modeling languages. This makes it extremely suitable for setting up Sparx Enterprise Architect as an architecture repository. The elaborations of these tools have all been developed based on Sparx Enterprise Architect.

Name=Alternatieven;Type=Package;

Name=Alternatieven;Type=Package;

An ambassador (preferably at management) level is needed for the architecture and the use of architecture repositories. For example, for safeguarding interests, making and keeping resources available and involvement in the planning of activities

Exchange of (partial) models based on the ArchiMate exchange standard so that exchange with other (ArchiMate) modeling tools is possible.

What are the relevant application functions to support the stated work processes. These can then be linked to modules in the architecture tool or to requirements (during a selection process).

Name=Applicatie;Type=Package;

Name=Applicatie;Type=Package;

A description of the structure and interaction of the applications as groups of capabilities that provide key business functions and manage the data assets.

This is the development of a products and services catalog for application services that are offered to the environment within and outside the organization.

Naming Conventions Usage: Noun (name of the package). For example: MsWord, Autonomy Federator

An encapsulation of application functionality aligned to implementation structure, which is modular and replaceable. It encapsulates its behavior and data, provides services, and makes them available through interfaces.

Naming Conventions Usage: verb. Example: Billing, Search, Indexing.

Application interfaces for application to application integration. This includes fully automated system integration processes, ETL implementations and automated and managed file transfers.

Application integration interfaces for machine 2 machine integration

Naming Conventions Usage: Noun. Example: Search Gui, VM—search service Web service.

Overview or basic map of the existing or future information systems, components and applications within the domain of architecture.

The collection of technology components of hardware and software that provide the services used to support applications.

Naming Conventions Usage: Noun in the ing form. For example: Transaction processing, Indexing.

Naming Conventions Usage: Noun. For example: GUI, REST API, Web Service.

Standardization of architectural models simplifies the creation, use and evaluation of these architectures. The use of templates makes this standardization possible. Introducing and maintaining templates is therefore a work process.

The XXX-wide Enterprise Data Warehouse (EDW) is modeled according to the XXX-wide Business (Data) Object Model

Introduction Applying building blocks describes the design and definition of building blocks. Building blocks are introduced to an organization from the perspective of:

• Reuse.
• Decoupling
• Generalization and specialization.
< li>Standardization.
• Interaction between providers and consumers of information provision. concepts (currently applications and infrastructure, but this must also be applicable to business architecture).
• Specification of costs and revenues.
• Improve (accelerate) services.
li>
• Information security.

This document consists of the following parts:

• Model: describes the definition, characteristics and relationships of the concept building block and the associated specializations
• ArchiMate viewpoints: development of the viewpoints for the building blocks. These viewpoints are composed of a limited set of ArchiMate elements and associations.
• Examples of elaboration of the various building blocks within the ArchiMate viewpoints defined above
• Sparx implementation, how this is done is implemented in Sparx and how it is communicated/published to the various stakeholders.

- master and reference data must comply with the BOM. - Transactions must comply with the BOM, which concerns the granularity of quantities and frequencies (time aspect). - Interpretation of source data according to BOM definitions​

After approval in the AB Applications, the secretary of the AB App informs the relevant SA with the request to contact the model managers for an appointment to transfer everything to production: with cc to the model managers mailbox.

Architectural models can always be more beautiful and detailed. This is often unnecessary and even undesirable. These overmodeled architectures must also be maintained and managed at a later stage. In addition, a detailed model is neither relevant nor clear for many stakeholders.

ArchiMate is an enterprise architecture modeling language that is used at a higher level of abstraction and is combined with other modeling languages such as BPM and UML for desired detail.

Here the viewpoints are described for solution architectures in particular, based on a different approach than the method with Viewpoints as described in the ArchiMate documentation. This is an elaboration of an organization that has determined a number of viewpoints for its own context. It is important that the viewpoints are related to each other. Within the viewpoints we work with:

• Primary elements (green border), these are elements that in principle must be elaborated in these diagrams.
< li>Secondary elements (orange border) are elements that may be used in these diagrams

It is important that we keep the number of concepts relatively limited and that the different viewpoints are related to the project package template for project or solution architectures.