Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.
Analyzer
Whilst you are modeling an application, you can generate code from the model and then analyse the way in which it executes, both monitoring and recording the execution behavior using the Execution Analyzer. This facility builds on and processes the structures and operations of the Model Driven Development Environment (MDDE), which provides tools to design, build and debug an application.
Access Analyzer
Analyzer Options
Option |
Action |
Shortcut |
See also |
||||||
|---|---|---|---|---|---|---|---|---|---|
Execution Analyzer |
Manage the Analyzer scripts for your model, using the Execution Analyzer window.
|
Shift+F12 |
|||||||
Debugger |
Control a debugging session and review the output, using the Debug window.
|
Alt+8 |
|||||||
Recorder |
Review the information recorded during a debug session, using the Record & Analyze window.
|
|
|||||||
Simulator |
Simulate the debugging of an application during the design of that application, using the Simulation window.
|
|
|||||||
Simulation Events |
Manage the triggers and sets of events in a simulation, using the Simulation Events window.
|
|
|||||||
Profiler |
Create execution profiles to report on runtime aspects such as:
This information is displayed on the Profiler window.
|
|
|||||||
Testpoint Manager |
Execute test scripts and monitor or control the output, using the Testpoints window.
|
|
|||||||
Analyzer Workbench |
Create your own Class workbench instances and invoke methods on them, using the Analyzer - or Object - Workbench.
|
|
|||||||
Grammar Editor |
Create, edit and debug context-free grammars to define the syntax of programming languages (in Backus-Normal Form / Backus Naur Form), using the Grammar Editor view.
|
|
|||||||
Breakpoints & Events |
Manage breakpoints and markers for debugging and Simulation, using the Breakpoints & Markers window. |
|
Breakpoint and Marker Management
|
||||||
Call Stack |
Review the currently-running threads in a debugging session, using the Call Stack.
|
|
|||||||
Locals |
Review the local variables and their values for the current local thread, using the Locals window.
|
|
|||||||
Watches |
Evaluate data items that are not available as local variables - such as data items with static Class member items, using the Watches window.
|
|
|||||||
Memory Viewer |
Review a process memory debugging session, using the Memory Viewer window.
|
|
|||||||
Modules |
Review details of the loaded modules, using the Modules window.
|
|
|||||||
Debug |
Execute a sequence of debugging commands, initiated through the Debug menu.
|
|
|||||||
Record |
Execute a sequence of commands for recording a debug session; these commands are initiated through the Record menu.
|
|
|||||||
Build |
Execute the Build script for the selected package; the script would have been previously created in the Execution Analyzer dialog. The output from the script is displayed in the Build tab of the System Output window.
|
Ctrl+Shift+F12 |
|||||||
Run |
Execute the Run script for the selected package; the script would have been previously created in the Execution Analyzer dialog. The output from the script is displayed in the Build tab of the System Output window.
|
Ctrl+Alt+N |
|||||||
Test |
Execute the Test script for the selected package; the script would have been previously created in the Execution Analyzer dialog. The output from the script is displayed in the Build tab of the System Output window.
|
Ctrl+Alt+T |
|||||||
Deploy |
Execute the Deploy script for the selected package; the script would have been previously created in Execution Analyzer dialog. The output from the script is displayed in the Build tab of the System Output window.
|
Ctrl+Shift+Alt+F12 |
Learn more
