The Use of Behavioral Diagrams in SysML
Larry Zdanis, Robert Cloutier
Abstract
Larry Zdanis, Robert Cloutier
Abstract
The definition of behavior in systems modeling language (SysML) presents special challenges to systems engineers, as overlapping functionality exists among SysML behavioral diagrams. Through discussion and examples, this paper imparts an understanding of SysML behavioral diagrams that will assist systems engineers in defining the behavior of various systems. The paper discusses the following goals of behavior definition: defining activity flow, tracking system state, defining system control, defining interactions, and allocating responsibility.
OpenAlex reports 5 citations for this work. Citation counts describe recorded attention and do not establish research quality.
A contribution statement is not available in the OpenAlex record.
Method details are not available in the OpenAlex metadata.
Findings are not separately available in the OpenAlex metadata.
Limitations are not available in the OpenAlex metadata.
Application details are not available in the OpenAlex metadata.
The definition of behavior in systems modeling language (SysML) presents special challenges to systems engineers, as overlapping functionality exists among SysML behavioral diagrams. Through discussion and examples, this paper imparts an understanding of SysML behavioral diagrams that will assist systems engineers in defining the behavior of various systems. The paper discusses the following goals of behavior definition: defining activity flow, tracking system state, defining system control, defining interactions, and allocating responsibility.
Key concepts: Systems Modeling Language, Activity diagram, Computer science, Behavioral modeling, Unified Modeling Language, State (computer science), Systems engineering, Human–computer interaction