Classification and an optional declaration
The DBJ Taxonomy is a single tree. The top level is an ordered list of categories: Conceptual, Logical, Physical, Implementation. Below it sit the capabilities. Every item has exactly one place in that tree, and the place is its stable ID.
Link To the Taxonomy Core
That is the whole core. It is deliberately small, and nothing in it is optional. Those names are the keywords.
What is Classified
WE us the term Item to denote the “things” we are classifying. Item is anything stored and classified in an Organization or BPT Domain or on a project: a document, a software product, a service, a physical book. The Taxonomy core does not say more than that, and does not need to. The taxonomy only gives each item a place. With a single primary aim: To be found later.
Why do we classify? To understand what is in the storage. What is exactly the item classified. And to understand each other in the organisation, when exchanging the information. In English: When talking.
Often each team decides on more details to be recorded with project items.
What is Optional
Optional: Item Declaration
If end when taxonomy does not describe the item sufficiently, an organization decides how much goes into an optional Item Declaration: Item Declaration. General recommendation is to keep it Minimal: the item’s place in the tree, plus one or two attributes (for example owner). Best is to jump straight into examples.
The DBJ Taxonomy is the only classification logic “allowed”. An Item Declaration does not classify, it details the item. It adds attributes that describe an item in more detail. Each organization decides if item record is necessary and how complex it needs to be.
Item Declaration Example
Use case: Jane (an Architect) is starting to document the conceptual architecture of the “Product X”. In agreement with her Product Domain team, she will add particular Item Declaration. Uniform, simple and agreed on the level of the domain team. That is important because every deliverable document will start with the same front matter.
| Attribute | Value |
|---|---|
| Item Title | Conceptual architecture of Product X |
| DBJ Taxonomy ID | Conceptual: Business, Information |
| Lifecycle | Draft |
| Tags | integration, security |
| Owner | Jane |
The Taxonomy ID is one category name plus one to four of its capabilities names. Only the Taxonomy ID says what the item is, and where it is in the info space. All other attributes describe it. Keep separate item location from its description.
The same example as front matter of a Markdown file:
---
# Item Declaration
# as defined by the organization
title: Conceptual architecture of Product X
# DBJ Taxonomy classification
taxonomy: "Conceptual: Business, Information"
lifecycle: Draft
tags: [integration, security]
owner: Jane
# The rest of the document front matter
# as per author's or organization rules
version: 0.1
---
From abstraction heavy we came to this simple text. And importantly it is ubiquitous. Thus everyone on the team will expect and use the same Item Declaration. Even everyone in the organization, not just the project, domain or the team.
Important: this is activity done once per organization lifetime. It is then applied inside each domain team.
Why not put all of it into the Taxonomy core
Straight Answer: Taming the Organization info space Complexity. A model with user defined, optional, independent item declarations, and to everyone’s liking, can not be drawn as one hierarchy. That invites the “tag” concept to become an escape route. One can simply invent the tags, and be very careful in the process. Complexity can very easily escalate.
A single tree is simpler and stricter. But simplicity is not understood immediately, by everyone on the team. Consistent and simple classification schema takes maturity, and organizations that never had to classify find it initially hard.
So the Item Declaration is entirely an optional extension, applied after the item is classified by the taxonomy tree.
Maturity leads to simplicity
The same reasoning behind the DBJ CMM Levels 3/4/5 used as required “entry ticket”. An organization (and individual) must be mature enough to loop through the BPT at the speed of AI. Simplicity is the prize for that maturity, not a starting point. Simplicity makes AI speed possible.
Rule of thumb
- The taxonomy tree says what an item is.
- The Item Declaration says more about it, if required.
Real life Example
Village library is built and now the books have arrived. Hundreds of various books. How are they going to be stored, so that later they can be found, when public starts coming in.
First step is to devise an classification and logic, and then implement it. In a usable shape and form.
Example Library: Books. Three books, each classified under Conceptual, each with an Item Declaration as front matter. Enough to start and then expand for hundreds of books, to be stored in the library.