Enterprise Architect version 15.1



My Profile

Social Media Channels

facebook  twitter  youtube   linkedin


Tutorials (150)

Tutorials can be used to become more productive and efficient in the use of Enterprise Architect. Tutorials, getting started guides, videos and workbooks can all be used to explain concepts and assist others in realizing the power and flexibility of using Enterprise Architect. Use this link to submit tutorials, training material, example workbooks and quick start guides.

Monday, 30 November 2009 00:44

DoxyGen Code Templates for Enterprise Architect

Written by
Enterprise Architect provides a number of code templates that specify the transformation from UML elements to the various parts of a given programming language. The following tutorial demonstrates how to modify a base code template to add support for generating DoxyGen comments.
Scenario:"Your organisation has standardised on the Unified Modeling Language (UML) and you are using an iterative software development process. You’re planning the first production iteration of your software development project and now it’s time to publish a firm delivery date." This tutorial provides a simple step by step guide to the estimation process, starting with a UML model in the Enterprise Architect CASE tool and resulting with a detailed project schedule in Circa. There are 7 easy steps: 1. Import UML software artifacts from Enterprise Architect 2. Assess their size and complexity 3. Apply technology metrics 4. Account for any…
Sunday, 08 November 2009 13:32

Creating marvelous EA documentation using LaTeX

Written by
Monday, 12 October 2009 00:56

RTF Documentation

Written by
Rich Text Format Documentation Rich text reports are documents produced by Enterprise Architect in Rich Text Format (RTF), a format common to many word processors. In particular it is targeted at Microsoft Word™, which provides the ability to link together a number of rich text documents into a single master document. Typically you will create a Word master document, then some Enterprise Architect RTF reports. These are linked back into sub-sections of the master document and refreshed as required during project development. In this way the project document becomes an easy to manage and feature-rich work product. By adding tables…
Sunday, 11 October 2009 23:21

The Physical Model

Written by
The Physical/Deployment Model provides a detailed model of the way components will be deployed across the system infrastructure. It details network capabilities, server specifications, hardware requirements and other information related to deploying the proposed system. Deployment View PM01: Physical Model The physical model shows where and how system components will be deployed. It is a specific map of the physical layout of the system. A deployment diagram illustrates the physical deployment of the system into a production (or test) environment. It shows where components will be located, on what servers, machines or hardware. It may illustrate network links, LAN bandwidth…
Sunday, 11 October 2009 23:04

The Logical Model

Written by
A logical model is a static view of the objects and classes that make up the design/analysis space. Typically, a Domain Model is a looser, high level view of Business Objects and entities, while the Class Model is a more rigorous and design focused model. This discussion relates mainly to the Class Model   The Class Model A Class is a standard UML construct used to detail the pattern from which objects will be produced at run-time. A class is a specification - an object an instance of a class. Classes may be inherited from other classes (that is they…
Sunday, 11 October 2009 22:55

The Dynamic Model

Written by
The dynamic model is used to express and model the behaviour of the system over time. It includes support for activity diagrams, state diagrams, sequence diagrams and extensions including business process modelling.   Sequence Diagrams Sequence diagrams are used to display the interaction between users, screens, objects and entities within the system. It provides a sequential map of message passing between objects over time. Frequently these diagrams are placed under Use Cases in the model to illustrate the use case scenario - how a user will interact with the system and what happens internally to get the work done. Often,…
Sunday, 11 October 2009 22:37

The Component Model

Written by
The component model illustrates the software components that will be used to build the system. These may be built up from the class model and written from scratch for the new system, or may be brought in from other projects and 3rd party vendors. Components are high level aggregations of smaller software pieces, and provide a 'black box' building block approach to software construction. Component Notation A component may be something like an ActiveX control - either a user interface control or a business rules server. Components are drawn as the following diagram shows: The Component Diagram The component diagram…
Sunday, 11 October 2009 22:19

Business Process Modeling

Written by
Page 11 of 11