External simulation: Languages and tools: SysML vs SysPhS vs Modelica vs Simulink Gallery Tutorial MINI TRAIL: Some recommended tools for getting started with Model-Based Systems Engineering with SysML and simulation with Modelica and/or Simulink Section
MBSE: Languages and tools: NoMagic/Dassault vs SysML Gallery Tutorial MINI TRAIL: Some recommended tools for getting started with Model-Based Systems Engineering with SysML and simulation with Modelica and/or Simulink Section
MINI TRAIL: Some recommended tools for getting started with Model-Based Systems Engineering with SysML and simulation with Modelica and/or Simulink Jump to first slide MBSE: Languages and tools: NoMagic/Dassault vs SysML Sections
SysML: HOWTO Safely incorporate ConstraintBlock equations from a library into a project with local ValueType variants: CASE: SysPhS vs ISO-80000 ModelLibrary
SysPhS-1.1: p.47: 10.12.2 SysML modeling: The states StandBy and On in 'Figure 29: State machine in SysML' should probably use 'entry' not 'doActivity'.
When the computer is in StandBy, y.sigsp [ERROR] is set to 8, and when the computer is On, y.sigsp [ERROR] is set to 3. Source SysPhS-1.1
The transition from On to StandBy has a ChangeEvent with an expression indicating that the transition is triggered when u.sigsp [ERROR] is equal to 0. Source SysPhS-1.1
SysPhS-1.1: p.47: 10.12.2 SysML modeling: References to 'u.sigsp' and 'y.usigsp' should be 'u.rSig' and 'y.rSig'.
The transition from StandBy to On has a ChangeEvent with an expression indicating that the transition is triggered when u.sigsp [ERROR] is equal to 1 (this is a signal as in signal flow simulation, not as in SysML). Source SysPhS-1.1
