| name | business-information-concept-modeling |
| description | Derives business concepts and relationships from capabilities, value streams and processes. Use when linking business architecture artefacts to information concepts for data modelling. |
| aliases | ["business-information-concept-modelling","information-concept-modeling"] |
Business Information Concept Modelling
When to use
Use when translating business architecture into conceptual data, ontology or semantic models.
Objective
Produce a practical, concise, traceable architecture artefact that a coding agent can use to guide implementation or review.
Procedure
- Review business artefacts.
- Extract nouns, events, roles and artefacts.
- Normalise synonyms.
- Define candidate concepts.
- Define semantic relationships.
- Remove implementation-only terms.
- Link to source artefacts.
- Hand off to conceptual data modelling.
Required outputs
- Concept list
- Definitions
- Relationships
- Synonyms/homonyms
- Traceability
- Exclusions
Best-practice alignment
Align with BIZBOK business architecture practice: keep capabilities, value streams, processes, organisation, information concepts, initiatives and metrics separate, then link them from strategy to execution.
Quality checks
- Concepts have definitions.
- Relationships use business semantics.
- Traceability exists.
Avoid
Do not convert every noun into an entity.
Mini example
From an onboarding value stream, extract concepts such as Customer, Application, Identity Evidence, Eligibility Decision and Account. Record synonyms like applicant/customer, define relationships such as customer submits application, and exclude implementation-only terms such as API payload or staging table. Hand the agreed concepts to conceptual data modelling with source traceability.
References
Verification
