Finding the right level of process-rules is challenging.
Too few processes and product quality is at risk,
Too many processes and you slow down #softwaredevelopment.

Does it make sense to use constraint blocks in #SysML parametric diagrams to show error probabilities? How would you connect such an error probability to a block that causes errors at the specified rate?

How would you model error cases in #SysML ? Most SW and HW parts that exist in a complex system can cause errors.
My spontenous idea would be to either not model these at all or to show these as regular control flows in e.g. activity diagrams. Is there a nicer way to do this?

How would you model system parts in #SysML that you do not fully understand and that come with more features than you need? E.g. you integrate an "Android 14" software system as guest onto a hypervisor partition and update this every couple of months.
My spontaneous idea would be to model it as a black box, allocate my requirements (Expectations) onto it and require test cases to ensure that needed functions are working...?

@msys2org Thank you for creating msys2 which i just installed an hour ago. It looks very promising.
Maybe I oversaw it: in the getting startet page a hint to run pacman -Syu may help beginners to find packages.
All the best and keep going,
Andreas.