A group of elements that have similar characteristics.
A first example. In object-oriented design, a layer is a group of classes that have the same set of link-time module dependencies to other modules. In other words, a layer is a group of reusable components that are reusable in similar circumstances. (Wikipedia: Layer (object-oriented design)).
A second example. The Shearing layers concept views buildings as a set of components that evolve in different timescales, from the site that is "eternal", to stuff that twitches around daily to monthly; (Wikipedia: Shearing layers).
A third example is elaborated in greater detail because of our interest in Enterprise Architecture. The ArchiMate Framework defines three main layers for modelling an enterprise (ArchiMate 2.1 Chapter 2.5 Layering), and a "layer extension" for modelling change.
In Archimate 3, strategy elements were added to the standard.
The core layers, and the strategy elements come with a number of concepts that cover these aspects:
Finally Archimate contains an "aspect extension" Motivation Extension to model motivational concepts such as goal, Principle and requirement.
The layers defined by Federal Enterprise Architecture Framework differ somewhat from those of Archimate.
The backlinks below usually do not include the child and sibling items, nor the pages in the breadcrumbs.
- Active structure aspect
- Application Layer
- Application Reference Model (ARM)
- Behaviour aspect
- Business Layer
- Collaboration
- Context of the Work
- Digital public services
- Enterprise architecture framework
- Enterprise models for the #2030Agenda
- European public services
- Event
- Federal Enterprise Architecture Framework
- Function
- Implementation and Migration Extension
- Interaction
- Interface
- Interoperability layers
- Model
- Model element
- Motivation Extension
- Object
- Passive structure aspect
- Physical Elements
- Process
- Service
- Strategy elements
- Technology Layer
- Token
- View
#tagcoding tags for goods, services and bads