EA · AI · ROI
A shared vocabulary is a prerequisite for CMM Level 3. All staff should be able to define and apply these terms without reference.
| Term | Definition |
|---|---|
| TOGAF | The Open Group Architecture Framework. The world’s most widely adopted Enterprise Architecture framework, providing the ADM guidance, reference models, and governance structures. |
| DBJ Method | A right-sized adaptation of TOGAF designed for smaller, fast-moving organisations. Preserves TOGAF’s maturity model and domain structure while reducing ceremonial overhead. |
| Enterprise Architecture (EA) | The practice of aligning an organisation’s strategy, processes, information, and technology into a coherent, governed whole. EA makes complex decisions tractable and auditable. |
| CMM | Capability Maturity Model. A five-level framework (Initial → Repeatable → Defined → Managed → Optimising) that measures the maturity of an organisation’s processes and practices. |
| CMM Level 3 (Defined) | The state where processes are fully documented, standardised, and integrated across the organisation. All domains operate from a shared playbook. Boot Camp target. |
| Domain | One of three organisational operating areas in the DBJ Method: Business, Products, or Technology. Each domain has a distinct mandate, accountabilities, and artefact responsibilities. |
| Business Domain | Sets strategic intent, commissions initiatives, defines outcome criteria, and conducts User Acceptance Testing (UAT). Owns the decisions on why and the what. |
| Products Domain | Translates Business strategy into Technology-ready requirements. Manages the backlog, owns the solutions, and coordinates UAT. The bridge domain in the (BPT) B→P→T→P cycle. |
| Technology Domain | Builds, integrates, and operates systems per the product specifications. Applies technical governance and architecture standards. Owns the how it’s built decisions. |
| (BPT) B→P→T→P Cycle | The DBJ Method’s core operating rhythm. Business commissions → Products translates → Technology builds → Products stages for UAT → Business accepts. Iterative and domain-explicit. |
| UAT | User Acceptance Testing. The formal process by which the Business domain validates that a delivered increment meets the outcome criteria set at commission. Outcome is passed onto “final” P –> T for deployment and the cycle closure. |
| Bridge to AI | The DBJ thesis that CMM maturity is the prerequisite for responsible AI adoption. AI is layered into processes progressively at L3 (documentation), L4 (decision support), and L5 (optimisation). |
| (DBJ) ADM | Architecture Development Method. Simplified TOGAF phase model (Preliminary → A through H → Requirements Management) for developing and evolving enterprise architecture. |
| Domain Lead | The designated accountable person for architecture decisions within a domain. Co-owns cycle governance alongside other Domain Leads. Escalates cross-domain conflicts to shared resolution. |
![]() |
|---|
| © dbj@dbj.org | CC BY SA 4.0 |