Dragon1 EA Modeling Language

Introduction into Dragon1 EA Modeling Language

The Enterprise Architecture Modeling Language as part of Dragon1 is a set of entity classes, symbols and rules for creating formal and informal models in the field of Enterprise Architecture. One of the advantages of using a modeling language for enterprise architecture is higher productivity, efficiency and unambiguity.

The basis is a Meta Meta Model

Dragon1 in its core recognizes the following base class models: meta model, user model and instance model.

The meta meta model consists most importantly of 'entity', 'attribute', 'relationship' and 'state' and with that and other constructus it defines the possible entity classes with which the Dragon1 meta model can be created, and so forth.

The meta model defines concepts and relationships for conceptual modeling. Dragon1 also defines rules on how you can extend the Dragon1 Meta Model with new specific entity classes.

The Dragon1 open EA Method contains an Enterprise Architecture Framework with generic reference models and an EA modeling language. The reference models make use of the modeling language. Dragon1 as modeling language consists of 400+ entity classes or concepts. The download below contains the most recent and full list of these entity classes.

Every entity class is defined and has its own symbol and modeling constraints and rules. Also various types of models, viewpoints, views and visualizations (diagram) are defined like an architecture view layout.

Download:
Dragon1 EA Modeling Language Elements

If in your opinion an important generic entity class or concept used at organizations, enterprises or companies is missing in this list, please notify us via info@dragon1.com and we will take your suggestions into consideration at the Dragon1 Architecture Foundation.

Overview of Core Dragon1 EA Modeling Terms

Dragon1 EA Modeling encompasses modeling at four levels of abstraction: Conceptual Modeling, Logical Modeling, Physical Modeling and Implementation Modeling.

The basics of Dragon1 EA Conceptual Modeling are centered around the following core terms:

  1. architect
  2. owner/client
  3. stakeholder
  4. program of requirements
  5. framework
  6. design
  7. decision
  8. realization, build
  9. need, issue
  10. concern
  11. system
  12. structure
  13. phenomenon
  14. human
  15. location
  16. space
  17. time
  18. money
  19. infrastructure
  20. facility
  21. architecture
  22. construction
  23. operation
  24. decoration
  25. principle
  26. performance
  27. quality
  28. requirement
  29. cost
  30. benefit
  31. (logical) function
  32. (technical) form
  33. ability
  34. capability
  35. disability
  36. objective
  37. model
  38. view
  39. viewpoint
  40. visualization
  41. entity
  42. concept
  43. element
  44. component
  45. technical product
  46. principle
  47. result
  48. person
  49. human
  50. animal
  51. robot
  52. machine
  53. computer
  54. document
  55. enterprise
  56. business
  57. infrastructure
  58. plan
  59. project
  60. budget
  61. solution
  62. deliverable
  63. milestone
  64. phase
  65. stage
  66. activity
  67. task
  68. process
  69. service
  70. product
  71. good
  72. mechanical
  73. manual
  74. automated
  75. robotized
  76. virtual
  77. digital
  78. physical

The core terms explained

In the following paragraphs we will explain what the terms mean, what their relationship is and why you need them as architect. All is explained from the viewpoint of an architect.

Read Also

You might be interested in reading the following items: