The Use of Behavioral Diagrams in SysML CSER 2007
Larry Zdanis, Robert J. Cloutier · 2007
The definition of behavior in Systems Modeling Language (SysML) presents special challenges to systems engineers, as overlapping functionality exists among SysML behavioral diagrams. This paper aims to guide the System Engineer (SE) through the challenges faced in defining a system's behavior via SysML by (1) identifying a set of purposes for behavior definition, (2) identifying criteria to help the SE decide which diagrams to use to satisfy these purposes, and (3) demonstrating realization of these purposes for a sample use case. The proposed purposes are as follows: defining activity flow, tracking system state, defining system control, defining interactions, and allocating responsibility.