Some example diagrams for Systems Modeling Language v1 (SysML®) and related technologies for Model-Based Systems Engineering (MBSE) on this Webel IT Australia show extremely fine-grained and "trivial" examples of graphical engineering purely for educational, pedagogical, and capability demonstration purposes. Such diagrams are not always advocacy for or recommendations for use of that exact approach - at the trivial level shown - on real-world projects!
Some diagramming and modelling examples serve primarily also just to record and demonstrate Webel Best Practice policies and conventions:
Most MBSE technologies also support integration with code-based systems, they don't always require graphical modelling. For example, in SysMLv1.x, one can use the 'body' of an OpaqueBehavior or the 'constraint' of a ConstraintBlock to capture mathematics in an opaque language (coding language), and these elements integrate fully with the graphical engineering models, and be computed using Magic Model Analyst® (Cameo Simulation Toolkit®):
Where one of the available opaque languages does not suffice, or where one wishes to delegate a complex or demanding calculation to a more powerful mathematics engine, Magic Model Analyst® (Cameo Simulation Toolkit®) offers integration with external maths engines, including Mathematica and MATLAB:
This strategy also integrates with external function libraries, so that changes in an external code base propagate across usages in a SysML1.x project:
The new SysMLv2 has its own SysMLv2 modeling code, with built-in propagation of calculations across an entire project, and direct integration with quantitative requirements.