Hi,
SysML v2 language is flexible and supports modelling at different fidelity levels. Therefore there is no one criteria that defines what is a complete use case model, it all depends on your project context, company or team modeling and style guidelines, and how you plan to use the model.
You could consider the model is good enough if the model does not have syntax errors (Syside here is extremely useful), model makes sense from semantics point of view and it captures the design details sufficiently accurately so that you are able to perform all the tasks you need to perform. You can initially capture a minimum set of information in your use case and then add additional detail gradually as you develop the model in future.
Useful resources from SysMLv2 release GitHub:
- 2a-OMG_Systems_Modeling_Language.pdf (Section 7.25)
- Intro to the SysML v2 Language-Textual Notation.pdf (slide 100-101
- Intro to the SysML v2 Language-Graphical Notation.pdf (slide 97)
- Example training examples: sysml/src/training/35. Use Cases
Also, I strongly recommend getting a hold of The SysML v2 Book and studying the Chapter 33 which discusses all SysMLv2 Cases, including Use Cases. It provides good guidance to make fidelity related decisions for your SysML models.
Finally, feel free to refer to other resources as listed in this forum post: Useful SysML v2 Resources
Kind regards,
Kestutis