Architecture as code in Etione
What architecture-as-code means in Etione — describing your architecture in a structured written form so diagrams are generated from it and stay traceable to it.
"Architecture as code" describes an architecture in a structured, written form — rather than as a drawing — so that the diagram is a derived artifact rather than the primary one. Etione is built around this idea.
Why it matters
A diagram drawn by hand is the only copy of the decisions it represents; when the underlying requirement changes, someone has to remember to update the picture, and that step is easy to skip. When the architecture is described as structured text first, the diagram can be regenerated from that description whenever it changes — the description is the source of truth, and the diagram follows it.
This also makes architecture reviewable the way code is: changes to a written description can be read, compared, and discussed directly, rather than requiring a visual diff of a picture.
How it works in Etione
- Write the requirement. Describe the systems, actors, layers, or process steps you want modeled, in as much concrete detail as you have.
- Generate the diagram. Etione produces a diagram — ArchiMate, C4, or BPMN, depending on what you're modeling — directly from that description.
- Revise the description, not the picture. When something needs to change, update the written requirement and regenerate, rather than hand-editing the diagram. This keeps the diagram and the description from drifting apart.