Simulation & Prototyping
in Enterprise Architect
Webinar June 2013
Mr Scott Hebbard Communications Manager at Sparx Systems, shows how to bring your behavioral models to life using wire frames, prototyping and model simulation. Learn how to:
- Create user interface designs (wireframes) in Enterprise Architect
- Link requirements, use cases and structured scenarios to UI prototypes
- Leverage the model to conduct A | B testing of user interfaces
- Combine process model simulations with UI designs for powerful system prototyping
|Simulation & Prototyping
Click to view demonstration
Click to view demonstration
Explore the Model
We have provided a copy of the Enterprise Architect model that was used in the webinar.
Questions & Answers
1: What version of Enterprise Architect did you use in this presentation?A: Enterprise Architect 10, Build 1007
3: Can we have a copy of the model used for this presentation?A: Yes. Here it is
4: What additional tools were used beyond EA?A: None. Enterprise Architect was used to design the model and simulate it.
5: Where are these simulation capabilities documented?A: See the Enterprise Architect User Guide, which contains the top-level topic Model Simulation.
6: Do you have any kind of tutorial on how create simulations and what type of artifacts support simulations?A: Apart from this webinar, you may interested the following videos and related resources:
- Demonstration of simulating Sequence Diagrams
- Demonstration of simulating a State Machine
- An introductory video on model simulation in Enterprise Architect
Also note that BPMN 2.0 models can be simulated.
7: How were the user interfaces (screens) built?A: These were modeled using Enterprise Architect's Win32 profile for UI Design. The Win32 modeling toolbox is built into all editions of Enterprise Architect.
You can learn more about this capability:
8: Can processes (activity models) also be simulated?A: Yes.
9: How do you access the Learning Center?A: Select the View Menu, followed by Learning Center. Alternatively, you may use Alt + F1. Select Simulation from the drop down list, as outlined in the Supplementary Questions video.
10: Are you going to demonstrate code generation?A: Though not part of this webinar, we may feature code generation capabilities in a future session.
For a more detailed step by step overview, please review the Supplementary video above.
13: Is there any mechanism to go back to a previous step when your are in between any simulation of an activity diagram?A: No. However, it is possible to use a breakpoint, allowing you to interrupt and inspect the simulation process. Simulation halts when it reaches an element defined as a breakpoint. The UML elements that can be defined as breakpoints include: Actions, Activities, States and most other behavioral nodes (decision, initial, final etc.).
For more information on simulation breakpoints view the Enterprise
15: How does that login window work? Is that code written in Enterprise Architect? Or must the user write the code for that?A: The Login window was modeled in Enterprise Architect using the Win32 UI profile. The Login button on the Dialog is functional and uses an onClick event to broadcast the Username and Password to the State Machine.
For a more detailed overview, please review the Supplementary video above.
16: Where do I put the new "password reset" process/state flow implied by the new button?A: The "Password Reset" button may require a separate process and State Flow altogether and could be contained within a composite diagram.
17: In the execution analyzer window, it looked like there were a number of C# scripts. How were these created? Were they also used in the simulation? If so, how?A: The Execution Analyzer window contains a number of Scripts, including some that are used for simulation. The C# examples are used to set up the compiler and default directory for code engineering examples. The Execution Analyzer window enables you to manage all Analyzer scripts in the model. You use the Execution Analyzer window toolbar buttons or script context menu options to control script tasks. Scripts are listed by package; the list only shows packages that have Analyzer scripts defined against them.
For a detailed, step by step overview, please review the Supplementary video above.