Glossary
> Start > ArchiMate Results > Enterprise Architecture Language > Glossary
abstract syntax
A description of the structure of a modelling language in terms of the possible concepts and possible relationships between them, independent of their representation.
abstraction
The reduction of an entity to the characteristics that are essential from a specific point of view.
architect
The person, team, or organisation responsible for architecture. [IEEE 1471]
architectural description (AD)
A collection of products to document an architecture. [IEEE 1471]
architecture
The fundamental organisation of a system embodied in its components, their relationships to each other, and to the environment, and the principles guiding its design and evolution. [IEEE 1471]
concept
A mental abstraction of something in the real world.
concern
The interest of a stakeholder, resulting from a stakeholder's goals, and the role played by some system. [Da Vinci]
concrete syntax
The description of the appearance of a modelling language in terms of the representation of concepts and relationships.
design
The part of a development process whose purpose it is to decide how a system will be implemented. [UML 1.3 Glossary]
domain
An area where one logically coherent, overall solution can be applicable. [CITA]
enterprise architecture
An enterprise-wide integrating framework for business architecture (strategy, governance, organisation, process), information architecture, application architecture and technology architecture.
framework
A basic structure, a frame of reference, or a systematic set of relationships. [IMTI]
generalisation
A taxonomic relationship between a more general element and a more specific element. [UML 1.3 Glossary]
implementation
A definition of how something is constructed or computed. [UML 1.3 Glossary]
inheritance
The mechanism by which more specific elements incorporate characteristics of more general elements. [UML 1.3 Glossary]
metamodel
A model that defines the language for expressing a model. [UML 1.3 Glossary]
methodology
A set of instructions, rules, and/or guidelines that defines the process of achieving a specific task. [IMTI]
model
An approximation, representation, or idealisation of selected aspects of the structure, behaviour, operation, or other characteristics of a real-world process, concept, or system. [STR]
reference architecture
A reference model mapped onto components that will cooperatively implement the functionality defined in the reference model, and relationships between these components. [BCK]
reference model
A generally accepted abstract representation that allows users to focus on establishing definitions, building common understandings and identifying issues for resolution. [JTA]
refinement
A relationship that presents a more detailed specification of something that has already been specified at a certain level of detail. [UML 1.3 Glossary]
relationship
A concept that represents a connection between two or more other concepts.
representation
The visual appearance of a concept or model amenable to human interpretation.
semantics
Formal or informal description of the meaning (possibly in a specific context or for a specific purpose) of the concepts and relationships in a modelling language.
stakeholder
An individual, team, or organisation (or classes thereof) with interests in, or concerns relative to, a system. [IEEE 1471]
syntax
Rules describing the allowed combinations of the categories distinguished in a language.
See also: "abstract syntax"; "concrete syntax".
system
A collection of components organised to accomplish a specific function or a set of functions. [IEEE 1471]
view
A representation of a whole system from the perspective of a related set of concerns. [IEEE 1471]
viewpoint
A specification of the conventions for constructing and using a view. A pattern or template from which to develop individual views by establishing purposes and audience for a view and the techniques for its creation and analysis. [IEEE 1471]
visualisation
The way in which the content of a model or view are presented to the user.
IEEE Computer Society, (2000), IEEE Std 1472-2000: IEEE Recommended Practice for Architectural Description of Software-Intensive Systems, Oct. 9, 2000.