Architecture Overview

Intro

This section provides a high-level overview of the SCDOM architecture documentation. It outlines the purpose of each submodule, helping readers understand the structure and how to navigate between related documents.

Architecture

Describes the core architecture of the SCDOM platform, including its microservice structure, processing flows, communication patterns, and architectural principles such as DDD, CQRS, and Event-Driven Architecture. It also includes diagrams and component descriptions for all services involved in the order lifecycle.

Refer to: Architecture

TMF622 Inbound API

Describes the REST API exposed to external systems based on the TMF622 Product Ordering Management (opens in a new tab) standard. Includes a list of supported endpoints and links to sample requests.

Refer to: TMF622 Inbound API

BFF API

Documents the Backend-for-Frontend (BFF) API, which acts as the intermediary between the user interface and backend services. Covers exposed endpoints, authentication handling, and forwarding patterns for order-related operations.

Refer to: BFF API

Plan Builder – SpEL Context

Explains the structure of the Spring Expression Language (SpEL) evaluation context used during plan building. Includes Java model classes, supported expressions, and practical examples based on order input.

Refer to: Plan Builders SpEL context – model

Step Executors Contract Models

Defines the message contract between the platform and external Step Executors. Includes command and event definitions, routing keys, and JSON samples for all message types exchanged via messaging.

Refer to: Step Executors model

Testing Methodology

Outlines the test strategy adopted in the platform — including unit tests, integration tests, end-to-end validation, and DOT-based tests for catalogue validation. Provides guidance for customizing tests in deployments.

Refer to: Testing Methodology

TMF ODA Support and Compliance

Explains how the SCDOM architecture aligns with TM Forum Open Digital Architecture (ODA). It includes mapping system components to ODA Building Blocks, detailed TMF Open API compliance evaluation, and highlights of architectural alignment.

Refer to: TMF ODA Support and Compliance