According to the ArchiMate 3.2 Specification1, the ArchiMate core language defines a structure of generic elements and their relationships, which can be specialized in different layers. Three layers are defined within the ArchiMate core language as follows:
The Business Layer depicts business services offered to customers, which are realized in the organization by business processes performed by business actors and roles.
The Application Layer depicts application services that support the business, and the applications that realize them.
The Technology Layer comprises both information and operational technology. You can model, for example, processing, storage, and communication technology in support of the application world and Business Layers, and model operational or physical technology with facilities, physical equipment, materials, and distribution networks.

Based on the ArchiMate 3 documents or objectives, the generic metamodel defines two main types of elements: structure and behavior. Structure elements represent the structural concepts that model the static construction or composition of concepts of the same or different types. Behavior elements represent units of activity performed by one or more active structure elements.

According to the standard notation conventions, a structure element is denoted by a rectangle with rounded corners. A structure element represents an entity that has a state and exhibits some behavior. Examples of structure elements are actors, roles, components, nodes, and objects.

The diagram uses the ArchiMate notation for a goal element and an aggregation relationship. A goal element represents an end state that a stakeholder intends to achieve. An aggregation relationship indicates that a whole is composed of parts. In this case, the goal 'Reduce Expense Ratio from 13% to 11%' is composed of three sub-goals that contribute to its achievement.