Solution Building Block (SBB)

Introduction:

Solution Building Blocks (SBBs) represent the actual products, services, or components required to implement architecture. These blocks are specific, tangible, and are directly mapped to deliverables in an enterprise's technical or business domains.

Characteristics of SBBs:

1. Tangible and Realizable:

   • Unlike ABBs, which are conceptual, SBBs deal with real-world technologies, systems, or processes.

2. Implementation-Ready:

   • Detailed to a level where they can be developed or acquired.

3. Vendor-Specific or Technology-Oriented:

   • Often align with specific software, platforms, or services (e.g., SAP for ERP, AWS for cloud hosting).

4. Traceability to ABBs:

   • SBBs realize the concepts and capabilities defined by ABBs.
   • Example: ABB might describe "Payment Gateway Functionality," while the SBB specifies the technology like Stripe or PayPal.

5. Lifespan Management:

   • SBBs may evolve as technology or business needs change.

SBB Structure:

A typical Solution Building Block includes:

Attribute	Description
Name	Clear identification and purpose of the SBB.
Purpose / Specification	Functional and non-functional requirements, including performance, scalability, and compliance.
Relationships	Connections to other SBBs or ABBs.
Implementation Details:	Platforms (e.g., Java, .NET, Kubernetes). Technologies (e.g., specific APIs or tools).
Constraints/Vendor/Product Information	Commercial or open-source solutions, such as Oracle DB, Salesforce.
Requirements/Standards and Guidelines	Adherence to enterprise policies, such as data security protocols.

Approach

We can use a left-to-right approach, such as starting from foundational Solution architecture to common solution architecture to industry-specific solution architecture.