I often hear arguments against SysML that the diagrams are not suitable for the stakeholder concerns. For example it is not a good idea to choose the requirements diagram to show thousands of requirements or a block definition diagram to show the complete mapping of the functional to the physical architecture with allocate relationships.
It can’t be mentioned enough: You must differentiate between the diagram and the repository. Although a modeler sees the model through the diagram, the most important part is the repository. The repository contains all data of the model. The diagrams are only views on the repository. You can delete all your diagrams and still have the information in the repository. You can compare it with a spreadsheet tool like Excel. The important information is in the rows and cells of your spreadsheet. You can create line charts, block charts, and so on, to display the information. The charts show only a cut-out of your information and you don’t loose it when you delete the charts. That doesn’t mean that charts and diagrams have no value.
If the SysML diagrams doesn’t suit your needs than simply choose another view. SysML itself provides two more views: tabular and matrix views. Most modeling tools have implemented them. The following figure shows a matrix in the modeling tool MagicDraw of the relationships between functional groups and activities (see the method for functional architectures for systems (FAS method) details: http://www.fas-method.org).
In addition in most modeling tools it is easy to export model information to Excel to provide table or matrix views on the data. For example the prototype of a variant configurator (see the blog post about variant modeling with SysML for details).
First think about the stakeholder concerns and how to address them with a view. Second check if SysML provides the view. If not try to implement the view with simple tool extensions or tool chains. There are more views for SysML than the 9 nine diagram types.