| Prev | Next |
Modeling Fundamentals
Modeling is the practice of constructing a graphical representation of something real for the purpose of studying, documenting, reasoning, testing or communicating it to others. The resulting models can be compared to machines that do work and often provide deep insights into the way things in the real world are structured or behave. Enterprise Architect is typically used to model complex enterprise, business, engineering, real-time and software systems, and is a multi-disciplinary platform that facilitates teams of people working together to describe, visualize, construct and test complex systems through the use of modeling. Enterprise Architect's modeling platform is based on the Unified Modeling Language (UML), a standard that defines rules and notation for software-centric systems but that can be extended to allow any type of system to be modeled.
Modeling Features
Feature |
Description |
|---|---|
|
Models 
|
Models are the top level of an Enterprise Architect Project. A Project can have one or many models contained within it. |
|
Views 
|
Views provide unique windows and dialogs to explore the relationships of the elements in your model. |
|
Packages 
|
Packages are the containers for your elements and your diagrams. Their contents can be viewed in many different ways dependant on your needs. |
|
Diagrams 
|
Diagrams are used to define specific relationships between a select number of elements in a visual manner. |
|
Elements 
|
Elements are the building blocks of your model; create and reuse elements to build up your systems. |
|
Connectors 
|
Connectors define the relationships between modeled elements. |
|
Tagged Values 
|
Extend the default properties of modeled elements, connectors and features with custom properties called Tags that can be given values. |
|
Notes 
|
Provide a text-based description of modeled: elements, connectors features, diagrams and more. Notes can be shown on the diagram, in the element or from the Notes View. |
|
Hyperlinks 
|
Hyperlinks add an incredible versatility to both navigation of your model and the provision of information through the various methods of communication within your project. In developing your model, you inevitably have to store information and structures in different places for different purposes and in different formats. Creating hyperlinks helps you to draw separate objects and documents together wherever appropriate to define or support a given context. |
|
Templates and Wizards 
|
Use patterns, templates and wizards to rapidly build your models. Use pre-existing ones, or create your own! |
|
Automation 
|
Extend the power of Enterprise Architect to create your own domain-specific Add-Ins, scripts and functionality. |
Structural Components
Using Enterprise Architect, you can quickly build a model using a hierarchy of Packages to represent the structure and organization of the model.
Component |
Description |
See also |
|---|---|---|
|
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. |
Building Models Model Domains Model Wizard |
|
Views |
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 |
The basic containers that create the overall model structure. Packages hold other Packages, elements, diagrams and similar model constructs. |
Packages Open Package in the Browser window |
|
Diagrams |
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 Working In Diagrams Layout Diagrams |
|
Elements |
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 |
Connectors represent the various kinds of relationship between elements within a model - including behavioral relationships, associations, taxonomic relations and similar. |
Connectors Connector Management Options Connector Tasks Connector Properties |
|
Tagged Values |
Tagged Values are customizable, profile- or user-defined properties that 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 |
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 of information that is used across a particular model - for example, Stereotypes or Tagged Values. |
Reference Data UML Types |
Learn more
- For information on UML, see the Unified Modeling Language (UML) Help topic
- The A Tutorial Modeling Session Help 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)