Kenchiku has an opinionated model for documenting your enterprise architecture.
Though standard modeling languages like UML and ArchiMate are powerful, they can be too complex for many organizations. We feel that they often require too much-specialized knowledge to describe the architecture of a business.
We have, therefore, created a lighter model. Like C4 did for software development, the kenchiku model is based on a few simple concepts that can be used to model the most important aspects of your enterprise architecture.
| Concept | Description |
|---|---|
| Account | You need an account to access kenchiku. Billing and reporting |
| Workspace | A workspace groups your architecture objects and views for one consistent entity (e.g., a company or a large department). Note that, for the time being, there are no links between objects of different workspaces. |
| Model Object | A model object can be an actor, a capability, a business process, or any object managed by kenchiku that is part of the lightweight model. |
| Report | A report in kenchiku provides a summarized view of your architecture's elements, performance, and metrics, helping stakeholders understand and analyze the structure and effectiveness of the enterprise architecture. |
Actor
People or systems that interact with applications (Customer, Account Manager, Bookkeeper).
Application
People or systems that interact with applications (Customer, Account Manager, Bookkeeper).
Business Process (PRO)
Business processes that are used to achieve a business goal.
Capability
A capability represents a specific ability or function that an organization can perform to achieve a business goal. It encompasses processes, resources, and skills required to deliver value and support the overall enterprise architecture.
Data Exchange
Data exchanges between applications. You specify which data objects are exchanged (Customer, Invoice...), what the source and target applications are (CRM->Web Site), and what underlying middleware is used (Kafka, Kong API Gateway).