No experience in SysML, tasked with identifying how we can use SysML diagrams in our work - Advice?
Hi,
I work for the Human Factors team in a large engineering company.
We've been working on trying to identify the specific steps involved in various large scale operational scenarios (e.g. initiation of and response to a fire in a control room, or simply manoeuvring a vehicle) so that we can apply detailed HF analysis to each of the steps. The purpose of this is to draw out design requirements for the systems (and/or physical environments) that will increase the likelihood of task success, particularly in safety-critical scenarios.
We have been capturing these scenarios in custom flowcharts which very closely resemble a hybrid between Activity Diagrams and Sequence Diagrams, and we will continue to use those due to their value in representing task and process flows etc.
However, I've now been tasked with looking into the potential for using actual SysML more broadly in the work, and what I'm struggling most with is how the diagrams relate to each other in terms of how they fit together in a sort of jigsaw?
Like, are there any diagram types that have to be developed before you develop the next type of diagram (e.g. you have to develop a Block Definition Diagram before you develop an Internal Block Diagram)?
Can I apply the systems engineering approach and 'Human Factorise' it? E.g. do a State Machine diagram but instead of system states it could be states of different individuals or teams?
I am totally new to SysEng and SysML and so don't really know if what I'm asking makes sense...
I guess what I'm asking is, if you were doing the job I described above, how would you approach using SysML to capture task procedures and track / manage the various information that could be collected throughout?