How it Works

This topic explains how the Visual Execution Analyzer generates Sequence diagrams.




See also


The Visual Execution Analyzer enables you to generate a Sequence Diagram

The diagram creates a visual representation of the execution of an application, outlining what functions are being called, the types of messages being sent, the key data structures used and the relationships between different Classes; that is, how information is moved throughout the system and what values are being passed by various functions

The diagram below illustrates the Sequence Diagram output for a program that calculates the price of books

The first loop structure is executed four times, to add four books to the book database; the arrows indicate information flow and demonstrate the change of states over time

VEA Small Sequence Diagram

Enterprise Architect can record arguments to functions, record calls to external modules or capture state transitions based on any given constraint; this information can be integrated with existing system knowledge and test data to optimize code execution, reduce errors and determine why application failure and system crashes occur

If an application crashes, data corruption such as a stack overflow can prevent you from diagnosing and rectifying the problem; however, the Visual Execution Analyzer enables you to record a given execution sequence to provide a reliable source of information that might further explain why a crash occurred

A Sequence diagram can convey more detail and provide greater understanding than reading unfamiliar code that might have been written by someone else; it also makes it easier to document existing code when the Sequence diagram illustrates functions that are being called and the specific sequence of events that occur to produce a particular type of system behavior


























The Recording History


Diagram Features

Learn more: