Though I have not worked with SysML yet but I think it will give an excellent dimension of work to the Business/System Analysts as it covers a bit more than UML 2.0.
1. SysML stands for System Modeling Language and it is a “customization” of UML 2.0 for system engineering.
2. SysML is a generic language to model Systems and Products, it is not a process.
3. Because of their separate development, process and language are loosely connected.
4. UML and SysML are the same language different dialects.
5. SysML is specified as a UML2.0 profile.
There is few completely new diagram types in SysML and one of them is Requirements diagram. The benefits of Requirements diagram are;
1. You can show relationship between requirements and hence you can have a complete sense about which sub requirements are forming a main requirement.How the requirements are communication each other to form a complete system.
2. From the requirement diagram your prioritizing job will be easy and perfect.
3. Customer/user will be able to see their system more clearly.
4. You can use dependencies with stereotypes.
Finally i would like to say that a diagram says more clearly that thousands of word can not. So don't write pages after pages, use diagrams. You would be benefited and so your customers.
The diagram above shows how different SysML is from UML.
