2. Dragon1 EA Method: Core Concepts

2.1 Definitions

For this standard, the following terms and definitions apply. Merriam-Webster's Collegiate Dictionary should be referenced for all other terms not defined by Dragon1.

2.2 Dragon1 Method

A reference structure consisting of four ways: the way of thinking, way of working, way of representing, and way of supporting.

2.3 Dragon1 Framework

A reference structure used to classify elements of the Dragon1 language. It consists of layers and aspects.

Note: The Dragon1 Core Framework is defined in detail in Section 3.4.

2.4 Dragon1 Modeling Language

The part of the Dragon1 method that defines the entity classes and relationships to model Enterprise Architectures. It includes entity classes from several layers, like Governance, Business, Data, Application, and IT Infrastructure.

2.5 Aspect

Classification of elements based on layer-independent characteristics related to the concerns of different stakeholders. Used for positioning elements in the Dragon1 metamodel. See also Section 2.6.

Note: Aspects are described in Section 3.4.

2.6 Attribute

A property associated with an Dragon1 language entity class or relationship.

2.7 Entity class

Something in the Dragon1 meta-model. Used to define and describe the constituent parts of Enterprise Architectures and their unique set of characteristics.

2.8 Conformance

Fulfillment of specified requirements.

2.9 Conforming Implementation

An implementation that satisfies the conformance requirements defined by the conformance clause of this standard. See Section 1.3.

2.10 Core Entity Class

A structure or behavior element in one of the core layers of the Dragon1 language.

Note: Core entity classes are described in detail in Section 4.1.

2.11 Composite Entity Class

An entity class consisting of other entity classes from multiple aspects or layers of the language.

2.12 Concept

Either an element or a relationship.

Note: The top-level language structure is defined in detail in Section ...

2.13 Element

Either an element or a relationship.

2.14 Component

Either an element or a relationship.

2.15 Technical Product

Either an element or a relationship.

2.16 Layer

An abstraction of the Dragon1 framework at which an enterprise can be modeled.

2.17 Model

Either a collection of concepts in the context of the Dragon1 language structure or a set of related entities.

Note: The top-level language structure is defined in detail in Section 3.2.

For a general definition of model, see the Dragon1 Framework.

2.18 View

A view is a set of contextual filters of a model. A view can be seen as a subset of a model. If a stakeholder with his or her needs, knowledge, and concerns looks at a model, some data entities will have no meaning, are not seen or overlooked and some data entities will have meaning or form a pattern that others just don't see.

2.19 Relationship

A connection between a source and target concept or entity. Classified as structural, dependency, dynamic, or other.

Note: Relationships are defined in detail in Chapter 5.

Architecting Solutions

DEMO: Concept Mapping Software

How to use Dragon1 EA Tool

Learn to generate architecture diagrams using repositories
DEMO: BPMN Onboarding Process Example

DEMO: BPMN Onboarding Process Diagram - Measure Rules Compliance

Manufacturing, Financial Solutions
DEMO: Enterprise Architecture Blueprint Template

DEMO: Generate an Enterprise Architecture Blueprint to discover and solve RISK

Banking, Logistics, Healthcare
DEMO: Strategy Map Template

DEMO: Generate Strategy Map for CLOUD ADOPTION

Government, Logistics, Banking
DEMO: Process Application Map

DEMO: Generate Landscape for RPA AUTOMATION

Retail, Agriculture, Energy, Oil & Gas
DEMO: Data Mapping Software

DEMO: Generate Application Landscape for SECURITY

Automotive, Financial Services, Health Care