Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.
Code Generation - Interaction Diagrams
During code generation from Interaction (Sequence) diagrams in a Class, Enterprise Architect applies its system engineering graph optimizer to transform the Class constructs into programmatic paradigms. Messages and Fragments are identified as one of the several action types based on their functionality, and Enterprise Architect uses the code generation templates to render their behavior accordingly.
Topics
Topic |
Detail |
See also |
Action Call |
A Message that invokes an operation. |
|
Action Create |
A Message with Lifecycle = New. |
|
Action Destroy |
A Message with Lifecycle = Delete. |
|
Action Loop |
A Combined Fragment with Type = Alt. |
|
Action If |
A Combined Fragment with Type = loop. |
|
Assign To |
A call message with a valid target attribute set using the Assign To field is rendered in the code as the target attribute of a call action. |
|
Notes
· | To be able to generate code from behavioral models, all behavioral constructs should be contained within a Class |
· | For an Interaction (Sequence) diagram, the behavioral code generation engine expects the Sequence diagram and all its associated messages and interaction fragments to be encapsulated within an interaction element |
Learn more
Learning Center topics
· | (Alt+F1) | Enterprise Architect | Software Engineering | Behavioral Code Generation | Interaction Diagrams |