Book a Demo

Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.

Prev Next

Modeling Domains

The world and the systems that underpin almost every human activity, from education to aerospace and from mining to manufacturing, require collaboration between multi-disciplinary teams. There are teams of business strategists that steer the ship of the enterprise through often turbulent and uncharted waters. Enterprise Architects that design how the enterprise will operate and change over time. Business Analysts derive requirements from customer workshops and detail processes, services, and information to prepare for technical analysis. Geospatial engineers and informaticians reason about location and its importance to human activity. Technical teams develop applications, information, and database systems in Cloud or hybrid architectures, and systems engineers develop robust cyber-mechanical systems based on detailed designs and architectures.

Enterprise Architect supports all these domains and roles and is a purpose-built collaboration platform where users can chat, message, review, discuss and unite their otherwise disparate models. The power of modeling is the ability to integrate the various system representations and sew together models from multiple domains and disciplines. For example, the ability to integrate models that describe the geospatial aspects of a feature in the world, such as an airport, with regulatory and air traffic control models and baggage handling system models, provides clarity that has not been possible before. The ability to model these concepts in the language of multiple disciplines and then tie them together in a single modeling environment makes Enterprise Architect such a valuable and productive tool.

Modeling Domains



See also


Enterprise Architect enables you to develop large-scale ontologies within the fully-integrated modeling environment, for your project domain.

ODM helps you to develop a formalized representation of business semantics and taxonomies, and a knowledge representation based on those formalizations.

MDG Technology for ODM


Enterprise Architect is one of the few UML tools that integrate Requirements Management with other software development disciplines in the core product, by defining requirements within the model.


Business Modeling

Modeling the business process is an essential part of any software development process, enabling the analyst to capture the broad outline and procedures that govern what it is a business does.

Business Models

Business Rules

Business Rule modeling captures the rules that govern a business, and their relationships with the entities and specific tasks within the organization or system.

Modeling Business Rules


The Business Process Model and Notation (BPMN) is specifically targeted at the business modeling community and has a direct mapping to UML through BPMN Profiles; these profiles enable you to develop BPMN diagrams quickly and simply.

Business Process Model and Notation (BPMN)


Business Process Execution Language is an executable language for specifying interactions with Web Services.

Enterprise Architect uses the BPMN profile as a graphical front-end to capture BPEL Process descriptions.

Business Process Execution Language (BPEL)


SysML is a general-purpose graphical modeling language for specifying, analyzing, designing, and verifying complex systems that might include hardware, software, information, personnel, procedures and facilities.

Systems Engineering

Data Modeling

Enterprise Architect provides easy-to-use tools for building and maintaining all of the fundamental data models - Conceptual, Logical and Physical; because Enterprise Architect lets you visualize each type of data model in the same repository, you can easily manage dependencies between each level of abstraction.

Getting Started


Enterprise Architect supports rapid modeling, forward engineering and reverse engineering of W3C XML schemas (XSD), critical for the development of a complete Service Oriented Architecture (SOA).

XSD Models


Enterprise Architect enables rapid modeling, forward engineering and reverse engineering of W3C XML Web Service Definition Language (WSDL), critical for the development of a complete Service Oriented Architecture (SOA).



The Software and Systems Process Engineering Metamodel (SPEM) is a conceptual framework for modeling, documenting, presenting, managing, interchanging, and enacting development methods and processes.

SPEM 2.0 focuses on providing the additional information structures that you require for processes modeled with UML 2 Activities or BPMN/BPDM.

Software & Systems Process Engineering Meta-Model (SPEM)


ArchiMate is an open-standard enterprise architecture language based on the IEEE 1471 standard, providing a common language for describing the construction and operation of business processes, organizational structures, information flows, IT systems and technical infrastructure.

It enables Enterprise Architects to clearly describe, analyze and visualize the relationships amongst business domains.



ArcGIS is a suite of Geographic Information Systems (GIS) software products developed by Esri.

Geodatabase Design for ArcGIS


The Archetype Modeling Language (AML) defines a standard means for representing clinical information.

Archetype Modeling Language (AML)

Data Flow Diagrams

A Data Flow diagram (DFD) is a graphical representation of the flow of data through an information system; it can also be used to visualize data processing (structured design).

Developing a DFD helps in identifying the transaction data in the data model.

Data Flow Diagrams

Entity Relationship Diagrams

Entity-relationship modeling is an abstract and conceptual database modeling method, used to produce a schema or semantic data model of, for example, a relational database and its requirements, visualized in Entity-Relationship diagrams (ERDs).

ERDs in Enterprise Architect assist you in building conceptual data models through to generating Data Definition Language (DDL) for the target DBMS.

Entity Relationship Diagrams (ERDs)

Eriksson-Penker Extensions

Eriksson-Penker extensions provide a framework for UML business processing model extensions, to which an Enterprise Architect can add stereotypes and properties appropriate to their business.

In Enterprise Architect, the Eriksson-Penker profile provides, through a set of stereotypes, a unique and effective means of visualizing and communicating business processes and the necessary flow of information within an organization.

Eriksson-Penker Extensions

Gang of Four Patterns

Gang of Four (GoF) Patterns are 23 classic software Design Patterns providing recurring solutions to common problems in software design.

Enterprise Architect provides each Pattern through an icon in the Diagram Toolbox.

GoF Patterns


The ICONIX Process is a streamlined approach to Use Case driven UML modeling that uses a core subset of UML diagrams and techniques to provide thorough support of object-oriented analysis and design.

Its main activity is robustness analysis, a method for bridging the gap between analysis and design.


Mind Mapping

A Mind Map is an image-centered diagram used to represent semantic or other connections between words, ideas, tasks or other items arranged radially around a central key word or idea.

A Mind Map is used to generate, visualize, structure and classify ideas, and as an aid in study, organization, problem solving, decision making, and writing.

Mind Mapping


Service Oriented Architecture (SOA) is an architectural paradigm for defining how people, organizations and systems provide and use services to achieve results.



The service-oriented modeling framework (SOMF) is a service-oriented development life cycle methodology, offering a number of modeling practices and disciplines that contribute to a successful service-oriented life cycle management and modeling.

SOMF 2.1

Extended Diagrams

Enterprise Architect provides an additional set of diagram types that extend the core UML diagrams for domain-specific models.

Also, the specialized modeling tools listed in the first part of this table each have their own specialized diagrams.

Analysis Diagram Custom Diagram Requirements Diagram Maintenance Diagram User Interface Diagrams Data Modeling Diagrams Business Modeling/Interaction

Inbuilt and Extension Stereotypes

Behavioral and Structural elements can be extended through the use of stereotypes; Enterprise Architect provides a number of inbuilt extensions.

Extension Stereotypes

Build Your Own Modeling Language

Enterprise Architect enables you to extend the scope both of your modeling and of the UML components you use, through the use of stereotypes, Profiles and Patterns to develop your own modeling applications.

Defining a Modeling Language