Sometimes the Model-Based (MB) - and Single Source Of Truth - aspect of Model-Based Systems Engineering (MBSE) is more immediately useful and accessible than the Systems Engineering (SE) aspect for many small-to-mid sized technical organisations and companies that do not have the organisational capability to embrace full on "military grade" Systems Engineering (SE).
If you are a member of such a small-to-mid sized technical organisation, you should not be scared that embracing MBSE with SysMLv1 or SysMLv2 and a good SysML tool implies suddenly completely over-hauling large parts of your existing projects and process (which is not to imply that formal SE can't be incrementally introduced with benefit too, but it's not always what is needed most first).
There is a huge amount that can be done with lower impact using mostly just the Model-Based (MB) part, and then incrementally introducing selected aspects of a formal Systems Engineering (SE) - such as (if even basic) Requirements tracking integrated with a SysML model.
Who knows, you may even benefit mostly initially just from some SysMLv1 Block (SysMLv2 Part/PartDef) and Value modelling, or maybe some freestyle Activity modelling and/or simple StateMachine modelling. Or you might be most interested in Trade Off studies using SysMLv1 Parametrics, perhaps integrated with MATLAB or Mathematica as maths engine. Or maybe just some black box interface definitions and communications models are what you need.
And good for you if that is what helps you!
Not everyone needs full on formal Systems Engineering (SE) to benefit from SysML and MBSE, and full on formal Systems Engineering (SE) is not all that SysML and MBSE are useful for and can offer you.
Yes, I said it out loud. Because I'm into promoting SysML and MBSE for everyone, big or small. And because people should not be made feel inadequate if they are not yet "military grade" model-based systems engineers.
Dr Darren (flame 🔥 proof)