An agile enterprise architecture can first be modeled at a high level and the low level details can emerge later to create an evolving agile enterprise architecture. However, it requires the adoption of a standard approach for modeling the artefacts and there are a number of modeling standards to choose from. The challenge is that each modeling standard differs in its notation and scope.

This paper presents the review of the four well-known modeling standards: ArchiMate, BPMN, UML, and SoaML; and recommends the tailoring of a situation-specific modeling environment for describing and analyzing the agile enterprise architecture artefacts, both at a high and low detailed level.