Systems engineering modeling languages must be capable of handling the complexity of the systems they describe, while also supporting the practical needs of the engineers and stakeholders who use them throughout the development lifecycle.   SysML has played a pivotal role in advancing systems engineering by providing a widely adopted, domain-specific …

The quest for a “single source of truth” and a model-based systems engineering (MBSE) practice grounded in integrated data is underway across the systems engineering world. The goals are laudable and the work being done is important, but there are some pitfalls along the way. It is critical that, in …

In the past few months I’ve been writing about how to model basic SysML concepts of behavior using GENESYS. SysML has three largely separate approaches for modeling behavior: activities, interactions, and states. I’ve covered the modeling of behavior using activities and interactions in August (Modeling SysML Activities in GENESYS) and …

In last month’s blog, Modeling SysML Activities in GENESYS, I discussed how to model behavior using activity diagrams. What, though, are interactions? Interactions are a UML concept brought over into SysML that can be used as an alternative approach for modeling behavior in SysML. Interactions are distinct from activities and …