← Back | Top

UAT

We are observing UAT phase for one product of many, lets call it “P(X)”

1. P ↔ T cycle: Technology signals P(X) readiness for UAT. After some time feedback arrives on the outcome. That is also the result of Business feedback from step 2 bellow.

flowchart LR
    P(Products) -->|"2:P(X) UAT Outcome"| T(Technology)
    T(Technology) -->|"1:Ready for P(X) UAT"| P(Products)

1. B ↔ P cycle: P reports on UAT result to the business. Business manages the report and sends a decision back to Products

flowchart LR
    B(Business) -->|"2: P(X) UAT Decision"| P(Products)
    P -->|"1: P(X) UAT Report"| B

Deployment

Technology method domain does the product release and deployment to the organization IT Landscape

flowchart LR
    T(Technology) -->|1:Deploy| I(IT Landscape)
    I -->|2:Status| T(Technology)

Termination / Continuation

1. P ↔ T cycle: After Product has signaled start of the deployment to the production, Technology signals P(X) deployment to production. After some time Products signals the start of P(X) project archival. That is also the result of Business feedback from step 2 bellow.

flowchart LR
    P(Products) -->|"2:Archive P(X)"| T(Technology)
    T(Technology) -->|"1:P(X) Deployed to PROD"| P(Products)

1. B ↔ P cycle: Business with Products manages the reasons of continuation or termination of P(X) projects

flowchart LR
    B(Business) -->|"2: P(X) is OK to Archive"| P(Products)
    P -->|"1: P(X) Deployed to PROD"| B

Larger Organizations: Business Domain form the Business Initiatives

Larger organizations can manage several products in the same time. Several B ↔ P ↔ T Flows. One per one product.

Remember: Business Domain is where stake-holders answer the question: WHY? The place where Enterprise Architecture asks the Stake Holders: “Why are we in this boat?”

On the organization landscape (at any given point in time) there can be 1..N Products in different phases of development

Business initiates and manages 1..N Initiatives. Each Initiative produces 1..N Products. Each Product maps to one Technology project.

flowchart TD
    subgraph BPT["BPT Loop"]
        subgraph B["Business Domain"]
            I1(Initiative 1)
            I2(Initiative N)
        end
        subgraph P["Products Domain"]
            P1(Product 1)
            P2(Product 2)
            PN(Product N)
        end
        subgraph T["Technology Domain"]
            T1(Project 1)
            T2(Project 2)
            TN(Project N)
        end
        I1 <--> P1
        I1 <--> P2
        I2 <--> PN
        P1 <--> T1
        P2 <--> T2
        PN <--> TN
    end

One BPT Loop guides one Product from Inception to Deployment.

Complexity multiplies inside domains — not in the loop. The loop is always the same structure. Architecture oversees all initiatives and keeps them aligned.

Method Domains Concept Anatomy

• DBJ Method Domain is conceptually a service
• Each Domain maintains its private persistent storage of deliverables.
• Domain Operations are communicating with other domain
  • Products is communicating with two domains

flowchart LR
    subgraph B["Business Domain"]
        direction TB
        BI(&lt;&lt;Interface&gt;&gt;<br>Business<br>Operations) <-.-> BS(Storage)
    end
    subgraph P["Products Domain"]
        direction TB
        PR(&lt;&lt;Interface&gt;&gt;<br>Products<br>Operations) <-.-> PS(Storage)
    end
    subgraph T["Technology Domain"]
        direction TB
        TE(&lt;&lt;Interface&gt;&gt;<br>Technology<br>Operations) <-.-> TS(Storage)
    end

    B <-->|Information| P
    P <-->|Information| T

That is conceptual view of DBJ Method BPT Domains. Not to be confused with micro services.

Method Domains are operationally decoupled. They live and operate independently of each other. They can be START-ed STOP-ed as a result of information arriving from the adjacent Domain

That seems much more complex in formal definition then in implementation. For example “Business Domain” might keep a simple folder/files structure (as ever before) for initiatives/projects/deliverables.

Keep the Method Domains decoupled. Exchange information with other domains but keep the domain storage private.

Method Domains are organizational units

Method Domains (B,P,T) are implemented as independent organizational units. With internal roles, management and procedures in tune with their reason of existence.