|
A-ESA Element |
Description |
Lean Mode |
|
Application Logic Service |
Represents
explicitly defined non-GUI application behavior and control
logic, or composition. |
|
|
Application Service |
A piece of software deliverable in association with end-user
distribution package(s). |
|
|
Architecture Principle |
Represents a
qualitative statement of intent that must be met by the
architecture. It¨s part of a guideline framework. |
Y |
|
Artifact |
Represents an
additional solution specification or design piece. It can be
a class, method, namespace, document, deliverable, project
or the like. |
|
|
Capability |
Represents an
EA-level ability that a structural element (such as a
functional service) possesses. |
|
|
Cloud |
A particular area of computer system capabilities and
resources available on-demand, independent of its location. |
|
|
Data Service |
A
self-contained piece of information that has a clear meaning
to the application, and can be a standalone data object, or
a federated, integrated piece of data service. |
|
|
Data Store |
Represents a
data store and is a self-contained piece of information that
has a clear meaning to the application, and can be a
standalone data object, or federated, integrated piece of
data service. |
Y |
|
Deliverable |
Represents a
defined outcome, generally more of a concern from a solution
management perspective. |
|
|
Deployment Package |
Contains
functional services based on their unique service-level
characteristics. |
Y |
|
Domain |
A concept of
the functionality or boundary where multiple elements are
controlled under the same scope. |
Y |
|
Entity |
A distinct object, concept, or thing that exists
independently and has specific attributes and
characteristics. |
|
|
Event Service |
A planned occurrence or activity with a specific purpose, or
a service for managing and facilitating events. |
|
|
Extension |
A flexible
representation for model element addition, including a
non-IT element or external system element. |
|
|
Frontend |
Represents mobile apps, web apps, portlets, reactive apps,
API consumers, etc. |
|
|
Generic Service |
Covers
well-defined capability, business or application activities
in a specific solution context, and serves as a logical
service, an architectural service, a process service, or a
functional service including app logic service, data
service, tech service, or user interface service. |
Y |
|
Goal |
Represents desired future state and objective. |
|
|
Grouping |
Represents a
logical representation, a layer or a generic composition or
aggregation of elements. |
Y |
|
Governance |
Embodies IT
architecture standards, compliance, and criteria. |
|
|
Key Choice |
It is an
architecturally significant decision, gap analysis,
risk/assessment, issue resolution or solution assurance and
governance based on the collective solution strategy. |
Y |
|
Location |
A place where
structural elements are positioned or communicated. |
|
|
Message |
Represents a unit of data sent between components to
communicate information. |
|
|
Microservice |
A small, independent service that performs a specific
function. |
|
|
Middleware |
It represents
system or intermediate software that provides services to
software applications. |
Y |
|
Network |
Denotes a set
of structures, products, and services that enable the
connection of system nodes for data transmission. |
|
|
Node |
Generally
represents a hosting resource that interacts with other
resources, or a hardware service. |
Y |
|
Note |
Represents the
commentary or interpretation of the architecture. |
Y |
|
Process |
Represents a process service or multiple contained services. |
|
|
Queue |
A data structure that holds and orders messages or tasks for
processing. |
|
|
Risk |
Represents a
constraint, a potential issue, something that hasn¨t
happened, or key decisions that need to be addressed. |
|
|
Role |
A
responsibility for performing a specific behavior. It
represents an actor, a user or a user group. |
Y |
|
Requirement |
Represents a
concise statement of needs in a broad sense, such as rule. |
Y |
|
Service Component |
Represents the
implementation of service responsibility or functionality. |
Y |
|
Service Interface |
Represents an access point where services are made available
to a user, service, or service component. |
|
|
System/Device |
A collection
of hardware and software pieces and a set of relationships
for specific business functions. |
Y |
|
Task/Activity |
A business
function, an activity, a use case, or a piece of work
assigned to a role in a process. |
Y |
|
Technical Service |
It represents
a behavior that is independent of the application-specific
logic context. |
|
|
UI Service |
An interactive
service usually with a visual presentation. |
|
|
Use Case |
Describes the
interactions between a role and a system to achieve a goal. |
|
|
Value |
Represents the
relative importance, worth of a vision or concept from an
enterprise perspective. |
|
|
View Frame |
Used to help
scale an architectural design as a drilldown view or
solution plateau. |
|
|
Virtual Service |
Represents an
intangible asset or information, or a technical service
without a physical IT service form or clear interface. |
|
|
Association Relationship |
Represents a
generic or an unspecified relationship. |
Y |
|
Flow Relationship |
Represents the
movement from one element to another. |
Y |
|
Realization Relationship |
Moves from an
abstract element to a concrete one. |
|
|
Composition Relationship |
Composed of
one or more other elements. |
|