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.

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

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.

Statement An architectural building block is the logical definition of a functionality Description The abbreviation ABB is used for an architectural building block. An architecture building block describes the functionalities that are offered to a higher-level entity. An ABB describes WHAT is needed, without writing to a specific solution. The higher-level entity can be a service or a composite ABB. An ABB can be composed of one or more SBB. These SBB are the implementation of the functionality. In other words, the SBB realizes the ABB. Features

• Description of a functionality
• Description of the behavior of information provision elements without features of physical implementation
• ABB is logical, without technical specification or brand names
• Infrastructural and application layers are the most important application area in the current phase of this model.
• Architecture building blocks are related to qualities, constraints and principles.
• This is the framework within which, for example, a product manager can select a product.
• When a product is at the end of the LCM, the frameworks in the ABB can be be used again to select a new product.
• The basic principle is to prevent an ABB from being written to an available solution. This should therefore be solution and technology neutral.

Producer of artifacts, data and information that serve as input for preparing architect artifacts (in the architecture repository).

A shorthand representation of "access to integrated information to support business process improvements" representing a desired state of an enterprise’s infrastructure specific to the business needs of the organization.

Statement A building block is a defined and recognizable architectural concept that meets an information provision need. Description A building block is described in this document an abstract concept that has been developed into three concrete specializations: service, ABB and SBB. Within our definitions, building blocks are seen as synonymous with an architectural pattern. The three specializations have a hierarchy. In our model, a service is the highest level of abstraction, within which Architecture building blocks are recognized which are implemented by one or more solutions building blocks. An important characteristic of building blocks is that they can be composed. This composition can be done in two ways:

• A building block is a composition of building blocks of the same specialization (for example a service is composed of one or more subservices)
• A building block is served by a composition of one or more building blocks from the underlying layer (for example a service is realized by multiple behavioral elements in an ABB.
• Composite building blocks are seen as synonymous with an architectural pattern within our definitions.

The composition of the specializations is developed for the specializations of the building blocks. The composition within building blocks can consist of several layers. However, it is desirable that the number of levels of building blocks within a specialization (Service, ABB or SBB ) remains limited. If a catalog becomes too complex due to the number of layers and building blocks, it is better to split a catalog. Features

• A building block has a defined boundary and is recognizable as a specific architectural concept.
• A building block is reusable.
• A building block is loosely coupled.
• A building block can interact with one or more other building blocks of different types.
• A building block is part of a catalogue.
li>
• Template for a delivery that meets a combination of requirements and wishes.
• A building block can consist of other building blocks and therefore becomes a composite building block.< /li>
• A building block can be part of a composition (composite building block).
• Building blocks can be recursive and in that case they are composed.

A representation of holistic, multi-dimensional business views of: capabilities, end-to-end value delivery, information, and organizational structure; and the relationships among these business views and strategies, products, policies, initiatives, and stakeholders.

There is one central location within XXX (the central D&A environment) for receiving, storing, validating, processing, 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.

Delivery of data or information to this data process.

Data or information management principles set frameworks for change in the organization, often within projects within the data roadmap. Elaborated in the selection of existing standards such as DMBoK, ArchiMate. The frameworks are developed on the basis of principles based on the principles within the enterprise architecture.

Sending data or information from data process.

XXX justifies the handling of data and information and is demonstrably in control - Rational Supervisors and stakeholders want certainty about the quality and careful handling of data and information. - Implication Data and information is auditable in design, existence and operation, whereby the measures taken are appropriate to the value that data and information represents.

Any communication or representation of facts, data, or opinions, in any medium or form, including textual, numerical, graphic, cartographic, narrative, or audio-visual forms.

Description of the aspects of the tooling when working with an architecture repository. On the one hand the required functionalities and on the other hand a list of various available tools.

1. A discrete behavior requestable from an application (e.g., log in, book train seat, transfer money).
2. The automated elements of a business service.

1. The lifecycle management of information and related technology used by an organization.
2. An umbrella term that includes all or some of the subject areas relating to the computer industry, such as Business Continuity, Business IT Interface, Business Process Modeling and Management, Communication, Compliance and Legislation, Computers, Content Management, Hardware, Information Management, Internet, Offshoring, Networking, Programming and Software, Professional Issues, Project Management, Security, Standards, Storage, Voice and Data Communications. Various countries and industries employ other umbrella terms to describe this same collection.
3. A term commonly assigned to a department within an organization tasked with provisioning some or all of the domains described in (2) above.
4. Alternate names commonly adopted include Information Services, Information Management, et al.

Data and information are handled with care, taking into account the applicable values, standards and laws and regulations - Rationale XXX is at the heart of society. The stakeholders expect XXX to comply with all relevant regulations and handle all data and information from all involved with care. Careful use of this can positively influence the image of XXX. - Implication XXX has laid down the rules for handling data and information in the XXX code of conduct for all employees. Relevant legislation and regulations (including those regarding privacy and competition) are identified and included in XXX standards frameworks and policies.

1. The ability to share information and services.
2. The ability of two or more systems or components to exchange and use information.
3. The ability of systems to provide and receive services from other systems and to use the services so interchanged to enable them to operate effectively together.

Data and information is provided with definitions and characteristics - Rationale Data and information is findable, available, readable and interpretable. For this purpose, data and information is labelled, classified and protected in line with the value it represents. - Implication Metadata, definitions, classification system and descriptions are available and applied.

Responsible for the use and deployment of the models in the architecture repository. Has a coordinating and controlling task for all modeling roles involved in the architecture. Monitors the consistency of the architecture repository and provides modellers with information and training on the use of the architecture repository.

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.

All data and information has an owner. - Rationale Structured and explicit ownership is necessary to be able to make decisions about the use and management of data and information and to set priorities. - Implication XXX-wide frameworks (policies, guidelines and standards) are necessary to deal adequately with data and information. A division of the XXX data and information landscape with recognizable boundaries is necessary to clearly organize ownership and responsibilities for data and information. Be clear about the roles (owner, user, editor) and associated tasks and authorities. Taking ownership and accepting someone else.

Unlocking a number of functionalities related to the management of personal and team activities and communication.

Making presentations for different purposes and target groups to present knowledge and information

The quality of data and information is actively managed and improved throughout the entire life cycle - Rationale Data and information is the raw material for business processes. Good quality ensures greater efficiency, reliability and compliance for everyone involved. The quality of data and information is crucial for making the right decisions. - Implication Quality management is assured throughout the entire life cycle of data and information. Focus on 'First Time Right' (Lean principle) and where necessary a control/review step.

Recipient of data to a business role of data and information from this data process.

For (master) data and information there is only ''one version of the truth'' - Rationale There is only ''one version of the truth''. Data and information is what it pretends to be. This prevents confusion and mistrust, unnecessary difference analyses, and inefficiency. - Implication One-time registration of master data, which can then be used in multiple places and a central data warehouse from which information products are drawn. Version management is applied, where applicable in collaboration with chain partners.

A system that manages all of the data of an enterprise, including data and process models and other enterprise information.

Data and information has an appropriate level of security - Rationale Adequate security of data and information prevents unauthorized use, supports the integrity of XXX and guarantees the continuity of business processes and services. - Implication Complying with the XXX policy on the security of data and information. This consists of a framework for Information Security, a risk-driven approach and a classification system to determine the desired level of security, and sets of measures appropriate to the importance (for XXX and for individuals) of the data and information.

Standards Information Base.

For (master) data and information there is only 'one version of the truth'. The leading source must be identified for each root and reference entry. As much master and reference data as possible must be centrally recorded in TABS and distributed from there to user systems...

special ETL process to transform specific data from the source to the master data. For example, consider an ETL process based on XMI, AMEF or BPMN exchange formats from the architecture repository to the consuming information systems.

The Standards Information Base (SIB) establishes the standards that new architectures must meet, which may include generic architectural languages and frameworks, industry standards, selected vendor products and services, or shared services already implemented within the organization.

A database of standards that can be used to define the particular services and other components of an Organization-Specific Architecture.

Life cycle management is applied to all data and information - Rationale Data and information has value in all life phases (from creation to deletion/destruction) and must be treated appropriately in all phases. - Implication Demonstrable organization and design of transfer between the different phases of data and information and monitoring the execution of all transfer tasks.

Supplier of data from a business role of data and information to this data process.

Data and information may be shared within legal and policy frameworks - Rationale Sharing unless, both internally and externally. XXX is at the center of society. The external stakeholders expect transparency and openness and internal transparency contributes to improving services. - Implication The confidentiality classification determines with whom and how information may be shared with others. The person who edits the information is responsible for complying with the policy on handling the information.

XXX data and information is of value to business operations - Rationale Data and information is used to improve the performance of XXX and the services provided to travelers. It is therefore an asset and is therefore controlled, secured and managed like other business assets: based on risk assessment and cost consideration. - Implication Data and information is managed adequately, with the measures appropriate to the value assigned and the risk associated with it.

The building block model consists of the generic entities building block and catalog. These form the basis of a reference architecture. Catalogs are groupings of building blocks within a specific domain. Multiple catalogs will be created that are related to each other and overlap within the visualizations. The advantage of the design of working with catalogs and building blocks is:

• Registers are created of reusable architectural components aimed at a specific field of work.
• The use of building blocks brings standardization and encourages reuse of architectural configurations.
• Building blocks makes the architecture and development process easier.
• Architectural product catalogs aimed at specific professional fields are being developed. This has a positive influence on the service provided to the rest of the organization.

The building blocks have three specializations, the definitions of which have been worked out in detail. These descriptions are elaborated in the paragraphs below. If relevant, additional information has been added to this elaboration, such as links to Togaf and examples of the implementation of these architectural concepts The model uses a pragmatic model with regard to the associations between Service and SBB. From ArchiMate perspective, the route from service is via ABB to SBB. This is characterized by the fact that the functional aspect is well embedded in the building block model. When publishing these models, a possibility is sought to generate reports and web pages that do not contain data relevant to the model for non-architecture stakeholders, which may mean that in a number of situations the ABBs do not have to be developed. Applying the direct association between service and SBB in the modeling does not meet the viewpoints.

Create a service oriented model for system integration Use services and interfaces to demonstrate how the components interact Model how the HR system and the Webform system exchange information Create an ArchiMate diagram of this service orientation

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.

Description of the aspects of the tooling when working with an architecture repository. On the one hand the required functionalities and on the other hand a list of various available tools.