Topic
Prev Next

Using the Analyze Panel

The 'Analyze' panel brings together a collection of powerful tools for analyzing the execution of an application. The tools available are a fully featured Debugger, an execution Profiler and a stack trace Recorder. There are also facilities for running the application and recording Test Point output, for subsequent analysis. The active Analyzer Script will determine the behavior of these tools, by specifying the commands that are executed as well as the settings and parameters for those commands.

Available Facilities

Facility

Description

See also

Analyzer Scripts

Display the Execution Analyzer window, which lists - by Package - all Analyzer Scripts defined in the model. From this window, you can create, edit and manage scripts that specify the commands and parameters required to build, test, run, debug, deploy and simulate your applications. The window's toolbar buttons provide for control of script tasks, such as build, run, test and deploy and also provide access to a range of debugging facilities.

Managing Analyzer Scripts

Search Files

Open the Find in Files window to search the local file system for source files that contain particular text.

Search in Files

Open File

Display a browser dialog from which you can select a file to be opened in the internal code editor.

Debugger

Click on the drop-down arrow to display a list of options for starting and using the Debugger.

  • Open Debugger - open the Debug window; this window provides a toolbar for controlling Debugger operations such as run, step-into, step-over, pause and also displays debug output messages
  • Start Debugging - start the application, according to the debug options of the active analyzer script
  • Attach to Process - display a list of executing processes - select and attach to a process for debugging purposes
  • Apply Debug Layout - apply a workspace layout containing windows useful for debugging, set out in a convenient arrangement
  • Create Stack Diagram - create an Interaction diagram based on the current execution stack; available only when execution is halted at a breakpoint
  • Set as JIT Debugger - set Enterprise Architect as the default Just In Time debugger; for Windows systems only
  • Process First Chance Exceptions - enable processing of First Chance Exceptions
  • Switch to Profiler - switch dynamically from the Debugger to the Profiler, allowing performance monitoring and execution tracing
Debugging

Profiler

The Profiler is used to record stack trace information for an application that is being analyzed, at pre-determined sampling intervals.

Click on the drop-down arrow to display a list of commands for starting and working with the application Profiler.

  • Open Profiler - open the Profiler window; this window provides a toolbar for controlling Profiler operations and displays a summary of the collected sample data
  • Attach to Process - display a list of executing processes - select and attach to a process to enable execution profiling and activity monitoring of that process
  • Apply Profiler Layout - apply a workspace layout containing windows useful for application profiling, set out in a convenient arrangement
  • Start - reattach the Profiler to the last profiled application process (where available), otherwise start the application specified the debug options of the active analyzer script and attach the Profiler to that application process
  • Resume - begin or resume collection of profiling data.
  • Stop - detach the Profiler from the application process; the application process will continue to run - click on the Start button to re-attach to that process
  • Create Report from Current Data - create a detailed execution call graph and overall summary, showing functions called and number of times a function was active when the profiler inspected execution
  • Load Report from File - load a profiler report from a saved file
  • Save Report to File - save the collected profile data to a file
  • Stop Process on Exit - an option to stop the application process when the Profiler is detached from that process
  • Show Debug Output - optionally show debug output as the Profiler executes
  • Discard Current Data - discard all collected sample data in preparation for a new run
  • Switch to Debugger - dynamically switch from Profiling to Debugging to allow finer grained inspection of application behavior
Profiling

Recorder

The Recorder is used to record information about function calls made by an application that is being analyzed.

Click on the drop-down arrow to display a list of commands for starting and working with the Recorder.

  • Open Recorder - open the Record & Analyze window; this window provides a toolbar for controlling Recorder operations, such as run (the application), manual record, auto record, stop recording and also displays the recorded function call information
  • Apply Recording Layout - apply a workspace layout optimized for use of the Recorder
  • Synchronize Model to Source Code - synchronize the source code of the current application with the model, to ensure correct recording and creation of diagrams
  • Attach to Process - attach the Recorder to an executing process
  • Start Recorder - start the application specified the debug options of the active analyzer script and attach the Recorder to that application process; recording will begin when execution hits a recording marker that has been set in the source code
  • Manual Record - use the manual record functions to start and stop recording while stepping through source code in the Debugger
  • Auto Record - automatically begin recording an execution trace, without manual intervention, once execution hits a recording marker that has been set in the source code
  • Step Thru - step through executing code while recording an execution trace
  • Stop Recording - stop recording the execution trace of the application process; the application process will continue to run
  • Save Recording to Model (Artifact) - save the recorded execution trace to a model artifact
  • Save Recording to File - save the recorded execution trace to a file in the local file system
  • Load Recording - load a recorded execution trace from a previously saved file
  • Clear Recording Data - discard any recorded execution trace in preparation for recording a new trace
  • Create Sequence Diagrams - create a Sequence (Interaction) diagram from the current execution trace; requires that model and code are synchronized
  • Create Call Graph - create a Call Graph from the current execution trace; requires that model and code are synchronized
  • Create Class Diagram - create a Class diagram using the elements that are instantiated and accessed in the current recording
  • Create Test Point Diagram - create a Test Point diagram and Test Sets based on the elements and their active members that were hit during the recorded session
  • Show/Hide Execution Point - show or hide the current execution point during the recording process; hiding this results in a faster recording time
The Recording History

Testing

Test Points are a scheme by which rules and constraints governing the behavior of objects can be taken from the model to create test cases to verify the application.

Click on the drop-down arrow to display a list of options for working with Test Points and Test Cases.

  • Show Testpoints Window - open the Test Points window to manage, configure and run Test Points and associated Test Cases, Sets and Suites
  • Find Test Suites and Test Sets - search the current model for Test Suites, Test Sets and related elements used in managing Test Point based verification
  • Open Object Workbench - open a simple Object testing environment for Java and .Net; instantiate objects and dynamically call their methods
The Testpoints Window