Modeling Basics

work_with_enterprise_architect

 

 

clip0035

 

Models

 

clip0036

 

Elements

 

 

clip0073

 

Diagrams

 

clip0062

 

Packages

 

clip0045

 

Views

Models are the top level of an Enterprise Architect Project. A Project can have one or many models contained within it.

 

Elements are the building blocks of your model, create and reuse elements to build up your systems.

Diagrams are used to define  specific relationships between a select number elements in a visual manner.

Packages are the containers for your elements and your diagrams. Their contents can be viewed in many different ways dependant on your needs.

Views provide unique windows and dialog to explore the relationships of your elements in your model.



 


 

 

clip0049

 

Templates and Wizards

 

clip0037

 

Connectors

 

clip0063

 

Tagged Values

 

clip0059

 

Notes

 

clip0046

 

Reference Data

 

Utilize patterns, templates and wizards to rapidly build your models. Use pre existing ones, or create your own!

Connectors define the relationships between your elements.

Extend the default properties of your elements with custom Tagged Values.

Provide a textual based description of a specific elements. Notes can be shown on the diagram, in the element or from the Notes View.

Extend the power of Enterprise Architect to create your own domain specific add-ins, scripts and functionality.

 

 

 

 

 

 

 

 

Modeling can be described as graphically representing a business process or software system. The resulting model can be used to emphasize a certain aspect of the system being represented, and to record, document and communicate its detail. A study of such a model can enable insight or understanding of the system. Enterprise Architect's modeling platform is based on the Unified Modeling Language (UML), a standard that defines rules and notations for specifying business and software systems.

Using Enterprise Architect, you can quickly build a model using a hierarchy of Packages to represent the structure and organization of the model.

Structural Components

Component

Link

Models - a model is the highest conceptual level, representing a distinct and complete representation of all or some part of a modeled system.

A Project can contain multiple models.

 

Models

Modeling

Model Wizard

 

Views are the second level within a model and define a specific viewpoint of the system being modeled - for example a Use Case view, a Requirements View or a Dynamic (behavioral) View.

Views are simply Packages that have an additional conceptual meaning.

 

Views

Add Views

Packages are the basic containers that create the overall model structure. Packages hold other Packages, elements, diagrams and similar model constructs.

Packages

Open Package in the Project Browser

 

Diagrams are visual representations of how model elements are connected or behaviorally related. They can also display the characteristics of an element, such as attributes, methods, notes and Tagged Values in a convenient visual style.

Diagrams

Diagram Toolbox

The Quick Linker

Diagram Context Menu

Diagram Tabs

Diagram Facilities

Layout Diagrams

 

Elements are the basic building blocks of models. They represent both structural constructs such as Classes and Interfaces, as well as behavioral constructs such as Activities, Actions and States.

Elements

Element Context Menu Operations

Visual Representation

 

Connectors are the various kinds of relationships between elements within a model - including behavioral relationships, associations, taxonomic relations and similar.

Connectors

Connector Management Options

Connector Tasks

Connector Properties

 

Tagged Values are customizable, profile- or user-defined properties which are generally related to a Stereotype and define additional attributes and characteristics of an element. They are one of the fundamental means of extending UML into more domain-specific areas.

Tagged Values

Quick Start - Add Tagged Value To Elements

Modify Tagged Values

 

Notes are the standard common language based descriptions of what an element, diagram, feature or relationship is for and how it is used within the model. Notes are  often used as a first step to eliciting the meaning and use of an element - which is later refined into something more concrete and precisely specified.

 

Notes

Notes Toolbar

Reference Information - a variety of basic types and information that is used across a particular model - for example, Stereotypes, Tagged Values and similar.

Reference Data

UML Types

 

Learn more

·For information on UML, see the Standard UML Models topic
·The Quick Start Tutorial topic briefly shows you how to create a diagram within a Package, containing elements and connectors
·Sparx Systems also provide a Demonstration of quickly developing a Use Case model (Online Resource)