Gap
Ontology: Techno Order
Code: —
A gap is defined as an outcome of a gap analysis between two plateaus, usually an architecture or the operations of a current and a desired situation.
The gap concept is linked to two plateaus (e.g., Baseline and Target Architecture, or two subsequent Transition Architectures), and represents the differences between these plateaus.
The concept is illustrated in the "Need to innovation" pattern (model) pattern.
Category: Implementation and Migration Extension
Examples: Gap between the Baseline and Target infrastructure
Typical Relationships:
- Composition, Aggregation, Specialisation
Source: Archimate 2.1, Chapter 11 Implementation and Migration Extension.
Questions, answers and comments
Add a New Comment
Children of Gap:
Gap in the tree of Model element:
-
Model element
- Application Component
- Assessment
- Business actor
- Business Role
- Capability
- Collaboration
- Communication Path
- Constraint
- Course of Action
- Deliverable
- Device
- Distribution Network
- Driver
- Equipment
- Event
- Facility
- Function
- Gap
- Goal
- Grouping
- Interaction
- Interface
- Junction
- Location
- Material
- Meaning
- Network
- Node
- Object
- Outcome
- Plateau
- Principle
- Process
- Requirement
- Resource
- Service
- Stakeholder
- System Software
- Value
- Work Package
