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

Model Templates

Model templates generated by Enterprise Architect are designed to assist in the creation of projects and models for both new and experienced users.

The templates are provided through the Model Wizard, for the model types available under the Basic UML 2 Technology and Core Extensions technology.

Each template provides a framework of packages, diagrams, representative elements and connectors on which to build a model appropriate to your purpose. These include overview diagrams that provide an introduction to the terminology and icons used in the model templates, and give a quick guide to the UML concepts important to the templates and how they are applied in Enterprise Architect. This information is provided either in Note elements or via Hyperlinks to the Enterprise Architect Help and other Sparx Systems website resources.




See also

Business Process Model

The Business Process model describes both the behavior and the information flows within an organization or system.

As a model of business activity, it captures the significant events, inputs, resources, processing and outputs associated with relevant business processes.

The Business Process Model

Business Models

Analysis Diagram

Business Modeling/Interaction


Requirements Model

The Requirements model is a structured catalogue of end-user requirements and the relationships between them.

The Requirements Management facilities built into Enterprise Architect can be used to define Requirement elements, connect Requirements to other model elements, connect Requirements into a hierarchy and report on Requirements.

Requirements Management

Requirements Management in Enterprise Architect



Use Case Model

The Use Case model describes a system's functionality in terms of Use Cases.

Each Use Case represents a single repeatable interaction that a user or 'actor' experiences when using the system, emphasizing the user's perspective of the system and interactions.


Use Case

Use Case Diagram

The Use Case Model

Domain Model

A Domain model is a high-level conceptual model, defining physical and abstract objects in an area of interest to the Project.

The Domain model can be used to document relationships between and responsibilities of conceptual classes (that is, classes that represent the concept of a group of things rather than Classes that define a programming object).

This model is also useful for defining the terms of a domain.

A Domain model shows:

The physical and organizational units of the domain; for example, Employee and Flight
The relationships between these units; for example, Employee is assigned to Flight
The multiplicity of those relationships; for example, one employee can be assigned to no flights, one flight or many flights (represented by 1* at the ends of the relationship)


Class Model

The Class model is a rigorous, logical model of the software system under construction.

Classes generally have a direct relationship to source code or other software artifacts that can be grouped together into executable components.



Class Diagram

The Logical Model

Database Model

The Database model describes the data that must be stored and retrieved as part of the overall system design.

Typically, this means relational database models that describe the tables and data in detail and enable generation of DDL scripts to create and set up databases.


Data Models

UML Database Modeling

Component Model

The Component model defines how Classes, Artifacts and other low level elements are collected into high level components, and describes the interfaces and connections between them.

Components are compiled software artifacts that work together to provide the required behavior within the operating constraints defined in the Requirements model.



Component Diagram

The Component Model

Deployment Model

The Deployment model describes how and where a system is to be deployed.

Physical machines and processors are represented by Nodes, and the internal construction can be depicted by embedding Nodes or Artifacts.

As Artifacts are allocated to Nodes to model the system's deployment and roll out, the allocation is guided by the use of deployment specifications.



Deployment and Roll Out

Deployment Diagram

Compartments - Tagged Values

The Physical Model


Testing Model

The Testing model describes and maintains a catalogue of tests, test plans and results that are executed against the current model.


Test Case

Show Test Script Compartments

Testing Support in Enterprise Architect


Maintenance Model

The Maintenance model enables visual representation of issues arising during and after development of a software product. The model can be enhanced with the integration of change elements and testing.



Color Code External Requirements

Project Management Model

The Project Management model details the overall project plan, phases, milestones and resource requirements for the current project.

Project Managers can use Enterprise Architect to assign resources to elements, measure risk and effort and to estimate project size. Change control and maintenance are also supported.


Project Management

Project Manager (Online Resource)

User Interface Model

The User Interface Model is a high level, logical mapping of forms, web pages, dialogs and other screens and controls that form part of the proposed system.

The template does not automatically include web interface or WIN32 UI design elements, but you can incorporate these in your subsequent development.


User Interface Models

Web Stereotypes

Win32 UI Technology