Solution Building Blocks


Solution Building Blocks (SBBs) represent components that will be used to implement our required capability/competencies. For example, a network is a building block that can be described and then put to use to realise solutions for the enterprise.

Building blocks represent (potentially re-usable) components  that we combine with other building blocks to deliver architectures and solutions. Our building blocks can be defined at various levels of detail, depending on the stage of architecture development has been reached.

For instance, at an early stage, a building block can simply consist of a name or an outline description. Later on, a building block may be decomposed into multiple supporting building blocks and may be accompanied by a full specification. Building blocks can relate to "architectures" (things that guide and shape what we have and do) or "solutions" (things we have to execute what we do).  

Below is our current list of used/reusable solution building blocks. Each link opens a catalogue. When you are looking for connections between entries in different catalogues first open the catalogues for each entry and if a link exists to entries in other catalogues it will be shown against that entry.

All new or changed solutions should normally use existing solution building blocks. If there are solutions that need to use new or changed building blocks they should  be reviewed as part of the solution conformance process and given either architecture approval or a dispensation in order to progress to the build phases of development.

Item SBB Types Name Details
01 Business Services The physical implementation of the managed business activities/processes we carry out aligned to our contracts for the operation of these services.

See ABB business services for more details about the logical structure of services.
02 Business Products The physical combination of SBBs that make up the products offered to our customers.

Products are also visible in the architecture continuum where they represent the logical combination of ABBs that make up our offerings to our customers.
03 Business Workflows, procedures and work instructions The instructions for how actors (systems or people performing roles) should carry out their business activities (processes) in line with the organisation's wishes.
04 Business Trained people People with the skills to perform their roles in line with the workflows, procedures and work instructions.
05 Data Physical data entities The design of the physical data entities, building on the logical data entities and taking account of the implementation technology and performance and security requirements in the real world.
06 Data Physical data components The physical products, environments and structures we use that enable us to capture, manipulate, store, access and secure our data.
07 Data Databases, file systems, files The storage context for data that we wish to store, view and use. This may be in a database management system (such as Oracle, SQL Server, MySQL) a file system that supports data and indexes (such as ISAM, VSAM) or a text style file that holds data and sometimes metadata (such as Acsii files, HTML, XML).
08 Application Physical application components A grouping of software modules that deliver a defined set of business functionality and can be deployed and managed as a unit. These may be purchased "off the shelf", customised or written from scratch. They are normally combined into identifiable "systems" for ease of management and control.
09 Application / Technology Software products             

It is usually basic software (such as an operating system, programming language or database management system) that is used to create/support application components.

10 Application / Technology Software code The code written in a specific language (such as C#, Java, Visual Basic, Perl, HTML) often using a software product development environment such as Visual Studio or Eclipse to support one of more physical application components.
11 Technology Physical technology components
(Buildings and other facilities)
Buildings, environments, machines and other materials that are used by people and systems to carry out their business activities.
12 Technology Physical technology components
(Data centres)
The environment where we run managed servers and/or store data. This may be our own centres, a supplier or partners' centre or a generic cloud based environment.
13 Technology Physical technology components
(Server devices)
The computing platforms that run in the back end layer supporting the processing, storage and/or transport of data for many users and/or client devices.
14 Technology Physical technology components
(Client devices)
The computing platforms that we use to access and manipulate data. These may be internal or external to the organisation and include PC workstations, PC laptops, Tablets, Phones and other specialised devices.
15 Technology Physical technology components
(Data Networks)
A set of managed nodes and connectors that link  computing devices and sensors. These can be very large of various sizes and coverage  (LAN, WAN, MAN & PAN). They may be private to our organisation, public (the Internet) or functionally a hybrid (e.g. using VPNs over the internet).

  Created by M.J. Anniss Ltd.                                               -top                                            By using this website, you agree with this website disclaimer.