"...
or is it not a good tool for that?
" - As always, you end up with the aphorism "a fool with a tool, is still a fool" :wink: Here the exercise is to learn about, and gain insights, into the value and limitations of 'MBSE and SysML' as tools [that support "Thinking"!].
As an example I would start with the almost ubiquitous SE model example of the car / automobile, and ask 'why is that the preferred example?'. Apparently Henry Ford said that if he'd asked the customer they'd have asked for 'faster horses'. So why don't the examples ask for 'Horseless carriage' models? or Personal transport vehicles (PTVs) [cf hovercraft, helicopter, speedboat, microlight aircraft, spaceship to Mars; are they all PVTs, so what is the top level PTV model?]
You didn't mention the discipline for your Masters, so taking it wide [engineering], reflect on the distinction between electrical bulk component modelling (resistors, capacitors, inductors, and perfect wires that join them) and the continuous distributed model of Maxwell's equations (no partitions, no blocks, etc).
If your Masters is computing related, reflect on the matched use of BNF (Backus Naur format) for programming language specification (C, Fortran, etc), as compared to free format languages such as FORTH (great language!), and which can be 'specified' in MBSE and SysM tools.
I hope I haven't answered the question.. but provided enough thoughts to allow you to investigate SE tools, their uses and abuses. Start by listing all the tools and their lead tutorial example...
PS. never tell 'management' it is a 'model' - its' always simply a diagram - it's all about priorities and communicating ideas [the 'never tell' anecdote is borrowed from Jon Holt who wrote one of the UML books]