Getting Started with Enterprise Architect 13

Webinar January 2017
In this webinar, you will learn how to:
  • Convey visual ideas and outline the benefits of modeling in Enterprise Architect
  • Create packages, diagrams and model elements based on ready made patterns
  • Use UML diagrams to illustrate how a customer interacts with a banking system

How do you create a simple model in Enterprise Architect? What are the advantages of modeling in Enterprise Architect over a diagramming tool? This webinar is designed to help customers get started with Enterprise Architect. You will learn how to navigate a model, edit diagrams and create a simple model based on a familiar banking example.

Scott Hebbard Scott Hebbard

Questions from the Audience

Click on a question to see the answer.

Questions from the Audience

Click on a question to see the answer.


 What version and Build of Enterprise Architect are you using?

Enterprise Architect 13. Build 1309.

 Where can I find public pricing information for Enterprise Architect?

Pricing information is available form the Sparx Systems website. All prices are listed in $USD. Please email to arrange a quote.

 How can I discover more about importing data into Enterprise Architect?

Enterprise Architect allows you to import data using XMI and CSV. For more information please refer to the Model Exchange section of the Help. To import information from Visio, please visit this page.

 Where can I find out more about modeling using UML?

The UML tutorial provides a comprehensive introduction to using UML and is an ideal starting point for customers that are just getting started.

 What is the difference between Structural and Behavioral diagrams in UML?

The Class Diagram in the webinar is a Structural diagram, while the Use Case is a behavioral diagram. Structure diagrams define the static architecture of a model. They are used to model the 'things' that make up a model - the classes, objects, interfaces and physical components. In addition, they are used to model the relationships and dependencies between elements. Behavior diagrams capture the varieties of interaction and instantaneous states within a model as it 'executes' over time; tracking how the system will act in a real-world environment, and observing the effects of an operation or event, including its results.