Dragon1 Code of Ethics and Professional Conduct

This code is about certified Dragon1 enterprise architects (EAs) and NOT building architects or landscape architects for the physical world

Ethics and integrity are essential to our work

EAs are dedicated to the highest standards of professionalism, integrity and competence. The Dragon1 Code of Ethics guides EAs conducts in fulfilling those obligations. The Code applies to the professional activities of all EAs.

The Code

The Dragon1 Code of Ethics is arranged in three levels of detail:
  • Canons (broad principles of conduct)
  • Ethical standards per canon (more specific goals toward which each should aspire)
  • Rules of conduct per canon (mandatory requirements).

The Dragon1 Code applies to the professional activities of Dragon1 certified enterprise architects (EAs). It addresses responsibilities to thepublic, which the profession serves and enriches; to the clients andusers of enterprise architecture.


Canon I - General Obligations

EAs must maintain and advance their knowledge (permanent self training) of enterprise architecture, innovations, hype cycles and trending topics, respect the body of knowledge of Dragon1, contribute to its improvement, thoughtfully consider the social and environmental impact of their professional activities, and exercise learned and uncompromised professional judgment.

Ethical Standard: Knowledge and Skills:

EAs should strive to improve their professional knowledge andskills.


1. In practicing enterprise architecture, EAs shall demonstrate a consistent pattern of reasonable care and competence and shall apply the technical knowledge and skills which is ordinarily applied by EAs of good standing practicing in the same locality.

2. EAs will escalate to the owner/client if there is no valid and approved of a financial business case, design contract, business model, program of requirements, context diagram or another important key document available.

3. EAs will proactively (without being asked) suggest to use audit reports as input for (high level) requirements and create a functional sketch of the business model of the owner/client’s organization to use to discuss solution requirements with the owner/client and stakeholders.