Search keyword in element

ABB

Architecture Building Block.

ABB Catalogue

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

Applying architecture building blocks

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.

Architecture Building Block

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.

Architecture Building Block

A constituent of the architecture model that describes a single aspect of the overall model.

Building block

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.

Propagating and degrading architecture

Parts of specific architectures such as project or domain architectures may have a generic character, making reuse desirable. This means that parts of these project architectures will propagate to a more generic architecture such as a reference architecture or architecture building block. Demotion from generic to specific is also possible.

Solution Building Block

A candidate solution which conforms to the specification of an Architecture Building Block.

Example ABB basic wordprocessing

Example of an Architecture Building Block starting from the application catalog of building blocks. This provides a recognizable example of office automation and part of it, namely word processing as a service that can be offered to parts of the organization.

Applying architecture building blocks

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.