Introducing implementation elements
Without being implemented, all your architectural work and artifacts will remain theoretical. Good presentations and nicely published enterprise content are great achievements, but they will not make things happen. Your next action is to convert your architectural artifacts into actionable plans and start building what you have been planning for. In this subsection, we will introduce you to the implementation elements and how to use them to model your plans, so let's start with the plateau element.
Defining plateaus
"A plateau represents a relatively stable state of the architecture that exists during a limited period of time" (https://pubs.opengroup.org/architecture/archimate3-doc/chap13.html#_Toc10045450).
A plateau represents the state of the architecture. It can be a past, present, or future state. When we mentioned the as-is, in transition, and to-be architectures in the previous Introducing strategy elements section...
