Product

Product is the middle segment of the BPT loop. It is the alignment point — the place where Business declarations are translated into specifications that Technology can implement.

Product does not declare and it does not implement. It aligns.

What happens in Product

Product monitors the Business repository. When the ICL ADM wheel places a Conceptual deliverable there — a capability declaration, an architecture vision, a product definition — the Product segment picks it up and acts.

Acting means: translating the Business declaration into Logical and Physical specifications. Workflows, interface contracts, data models, integration requirements. These are the artifacts that Technology can build from.

Product does not reach back into Business to negotiate the declaration. It works with what the Business repository contains.

Product Artifacts

Product Artifacts are the Logical and Physical outputs produced inside the Product segment — and also the Logical/Physical deliverables the ICL ADM wheel places directly into the Product repository.

Workflows — sequenced activity and decision flows describing how a declared product operates
Interface contracts — API definitions, message schemas, integration specifications
Data models — Logical data structures that support the declared product
Physical specifications — platform, hosting, and deployment constraints the product must satisfy

These artifacts are the formal input to the Technology segment. They are placed in the Product repository. Technology monitors that repository.

“Application” and “Product”

In TOGAF ADM terms, this layer is called the Application Layer — the ADM step that covers information systems architecture. In BPT operational terms it is called Product. Both names refer to the same position in the model. Throughout this KB, Product is the operational name; Application Layer is the formal ADM reference.

The boundary

Product owns the alignment — the translation between what Business declares and what Technology builds. It does not own strategy (Business) and it does not own implementation (Technology). Engineering concerns that surface during Product work are passed to the Technology repository as constraints, not resolved inside the Product segment.

© dbj@dbj.org , CC BY SA 4.0