Hi Bruce
How are you doing.
I have a question on SysML Activity diagrams.
For a System S, there is a Product P, which contains Process P1 and Process P2.
Process X takes input and processes it and keeps the results internally.
Later on in the System processing cycle, Process P2 reads P1's stored results and it (P2) outputs them.
What is the SysML philosophy for presenting this? FYi, I have to try to keep my diagrams/model simple bc my corporation is still at the outset of using MBSE.
Can I present the above in one activity diagram? I.e. , show two time event elements T1 and T2, where T2 fires and reads the stored results and then outputs them? And maybe each of P1 and P2 should be after its own 'Activity Start' , because really each of process P1 and process P2 are separate activities / threads.
Further, in general, is what I have described - P1 and P2 - really two activities? Maybe they are really just two threads in one activity?
Thanks
Avi

Great insights on modeling concurrency in SysML activity diagrams!
Your explanation about using active classes with double vertical line borders to represent threads is particularly helpful. For those working with complex systems, it's crucial to maintain a balance between diagram simplicity and the accurate representation of concurrent processes. If you're in the Athens, GA area and seeking support in managing complex workflows or understanding behavioral dynamics, consider exploring Relationship Counseling Athens. Additionally, for individuals needing ADHD testing in Athens, GA, ADHD Testing Athens GA offers valuable resources. Best regards, and thank you for sharing your expertise!