When SysML addresses mainly the architecture definition and the components working principles, how can you then refine the system-level requirements into accurate software requirements that will be the inputs to the software development activities? In other terms, how can you make sure that the software requirements define the right behavior without waiting for the (late) test and validation phases?

And once the software has been develop, how can you automatically verify it complies with its software requirements, without having to develop each and every test case manually?

Check this 10mn Stimulus video that presents DS solution to these two challenges, enabling to extend the use of models until the final validation phase when the integrated system is tested: