Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.
Modeling Basics
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.
Topics:
Topic |
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. |
|
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 which have an additional conceptual meaning. |
|
Packages are the basic containers that create the overall model structure. Packages hold other packages, elements, diagrams and similar model constructs. |
|
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. |
|
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. |
|
Connectors are the various kinds of relationships between elements within a model - including behavioral relationships, associations, taxonomic relations and similar. |
|
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. |
|
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. |
|
Reference Information - a variety of basic types and information that is used across a particular model - for example, Stereotypes, Tagged Values and similar. |
Learn More:
- For information on UML, see the Standard UML Models topic
- For examples of the UML models that Enterprise Architect can help you build, see the Model Templates 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)
