If you're just getting started with modeling for analysis and design, this session is for you! We'll step you through how to create your first modeling project in Enterprise Architect.
We'll also explain some basic modeling concepts along the way, such as how elements in the model hierarchy relate to the diagrams you draw.
In this webinar you'll learn:
Don't miss this opportunity to learn more about Enterprise Architect
Enterprise Architect 13.5, Build 1351. I used a trial installation of Enterprise Architect for this demonstration.
You might like to browse the various models contained in the EA Example project. You can access the EA Example project via the ribbon Start | Help | Open the Example Model. You can also find sample models posted with some of our previous webinars - see our Webinar Library.
We will consider holding future webinars on team collaboration. We held some of these recently, featuring Enterprise Architect's Pro Cloud Server:
Yes. For example, our next webinar will discuss the basics of UML Class modeling. You can register for that via the webinar registration page.
Yes. Our webinars cover a range of modeling skill levels. You might be interested in some of the specialized topics we've covered previously, as listed in our Webinar Library.
Digesting this and other introductory webinars is a good start. You can view the other beginner-level presentations in our Webinar Library. Additional free online learning resources are available from our Resources & Tutorials page. These resources are most effective if you use them with your own installation of Enterprise Architect - so download and install the Trial edition as well. Our many partner organizations also provide training programs for beginner levels and beyond.
You can locate these resources via:
Yes. Please see our Webinar Library.
Yes. Please see our Case Studies page.
You can run Enterprise Architect on macOS using WINE. For details, see our instructions page Installing Enterprise Architect inside Wine or CrossOver.
Currently, there no plans for a native installer for macOS.
I double-clicked that diagram node in the Project Browser. That opens the diagram tab in the main view. See the video at 12:55. For a more general explanation about opening diagrams, see the video at 5:48.
The Find Command control positioned next to the ribbon categories is only available in the later Microsoft Office Themes. It is a known limitation. For all themes, however, you can access equivalent functionality inside the main application menu (top left icon) using the Search control at the bottom.
See the presentation video at 19:02. There is an Options tab in the Generate Documentation dialog.
Enterprise Architect 10 uses a menu system instead of the newer ribbon, so it does not have a Publish ribbon option. To generate a Rich-Text Format document, use the menu: Project | Documentation | Rich Text Format (RTF) Report. To export a diagram as an image file, use the menu: Diagram | Save as Image.
If you have Enterprise Architect's Status Bar visible, the tool tips will be displayed there. The option to show/hide the Status Bar was shown in the presentation video at 4:45.
To display tool tips as in earlier versions of Enterprise Architect, you can disable the option to display tool tips in the Status Bar. You do this via the ribbon Start | Workspace | Visual Style | Show Tips in Status Bar. (This approach only works when running Enterprise Architect under Microsoft Windows.)
You can achieve this by setting a default appearance for a given element. For details, see the Help topic Set an Element's Default Appearance.
Yes. You can use tools in the Layout Ribbon to help align and size diagram elements quickly. For an example, see the presentation video at 16:30.
Alternatively, you can select multiple elements on the diagram by pressing control while you left-click an element. One of the selected elements will be your reference element, against which you want to size all the others. Left-click that reference element and use the in-place formatting tools that appear beside it. You can see an example of this in the presentation video at 16:43.
There are several paste options available when you drop an item from the Project Browser onto a diagram - depending on what kind of item you drop and the type of diagram you target. The ones that were shown in this webinar were Link, Instance (Object) and Child (Generalization).
As mentioned in the presentation, choosing Link, results in a reference to the original model element being drawn on the diagram. The Instance (Object) option will instantiate the element you are dropping and draw that instance for you on the diagram. The instance is a new element in the model hierarchy. The Child (Generalization) option, creates a new element that is derived from the element you are dropping. The derivation is modeled as a Generalization relationship between the parent and child elements. The new child element will be drawn on the diagram, and if the parent is already present on the diagram - the Generalization connector will be drawn as well.
For more details on the paste options, see the Help topic Drop Elements from Project Browser.
If you're trying to draw a reference to the original model element, choose Link, regardless of whether the element occurs in one diagram or many.
Yes. You can add more top-level Packages for these in the Project Browser either via the Model Wizard, or creating new Packages via the context menu. You can also use a mixture of model types under any given Package as needed.
Yes. Enterprise Architect supports specification of formal project requirements. You might be interested in previous webinars we have held on this topic:
Yes. Enterprise Architect has a built-in set of tools for designing User Interfaces. User Interface design elements can be linked to Use Case elements using a Dependency or Trace connector, or they can be modeled as nested elements under a Use Case. For details on Enterprise Architect's User Interface tools see the Help topics User Interface Diagrams and Example User Interface Diagram.
You can use Root Nodes in the Project Browser to contain separate projects. This can make a clearer distinction between projects in the model hierarchy, than if you used Packages to do the same.
One advantage of having multiple Projects in the same model repository is that you can share Reference Data, such as Model Authors, between them. This is still the case regardless of whether you use Root Nodes or Packages.
There are several ways to import objects from another project. The best method depends partly on whether you are importing from an Enterprise Architect project or another source. One common way to import model data into Enterprise Architect is to use XMI. This can work with data coming from another modeling tool, if that tool supports the XMI specification. For details, see the Help topic Import from XMI.
Between Enterprise Architect projects you can simply copy and paste elements via the Project Browser. Because this uses the Clipboard, you can perform the copy/paste operation between two instances of Enterprise Architect. This approach can also be used to copy an entire Package or multiple sibling elements selected in the Project Browser. For details, see the Help topic Element Copy/Paste Submenu.
You can create instances of elements as you drag and drop them from the Project Browser. When prompted as to how to paste the element, instead of selecting Drop as | Link as I did, you can choose Drop as | Instance (Object). You can do this multiple times to create multiple instances of an object, as illustrated in this image.
Note: You cannot use the same instance of an element or multiple links to the same element on the same diagram.
The answer depends on whether you want to create a new element for a particular type of model, or you want to locate an existing element of a particular type in the model hierarchy.
To create a new element of a particular type directly in your model hierarchy:
You can create new elements diagrammatically by using the Diagram Toolbox:
If you need to use an existing element of a particular type, you can create a search definition to search the model by element type. For details, see the Help topics Model Search and Create Search Definitions.
Both of these are what we refer to as file-based model repositories. In each case, the file is actually a database that stores Enterprise Architect's model data. By convention, we use the .eap extension to refer to Enterprise Architect projects that use a Microsoft JET database as the underlying file type, and the .feap extension to refer to projects that use Firebird instead. Although the differences in the implementation of the two database products may be vast, the functional differences when used with Enterprise Architect are few and minor.
One difference, as noted in the presentation video, is that a Firebird repository (.feap file) supports Unicode characters, whereas you need to do some configuration to enable Unicode support with a JET database (.eap file). For details, see the Help topic Startup and the related topic General Options.
Please refer to the Help topic Create a Project in a SQL Server Database.
Yes. Use the ribbon: Configure | Model | Transfer | Project Transfer. For details, see the Help topic Project Data Transfer.
Yes. There are various ways to share Enterprise Architect projects. Typically, team-based projects use a remote DBMS repository, such as MySQL, Oracle or Microsoft SQL Server. Recently, Sparx Systems released a dedicated platform, the ProCloud Server, for managing team-based model repositories and facilitating web and mobile access to models. You might like to see our previous webinars on this topic:
For more information on these aspects of model repositories, see these Help topics:
For instructions, see the Help topic Version Control.
You can use Enterprise Architect's Document Artifact elements to contain sections of text. You can also attach Linked Documents to elements and Packages, such as the Package containing your Use Case diagram. You can include these documentation elements in generated reports. For details, see the Help topic Reporting Linked Documents.
It's very likely we will hold further sessions on document generation. Previous webinars on this topic include:
There is no automated way to do this out-of-the-box. Because Enterprise Architect supports a rich set of model data for elements and relationships, any export to Visio drawings would likely result in data loss.
Not specifically in this webinar. The ability to export diagrams as images from Enterprise Architect, as shown in this webinar, can be useful when using PowerPoint. See the presentation video at 17:00. We do provide an extension that integrates Enterprise Architect with Microsoft Office. For more information see: