So far, I'm getting best value from Q's response.
I realize that 'it depends' is the most logical answer, but, like most clients, they haven't decided exactly how they are going to do their process modelling.
And I think this is a reasonable approach.
But before you scream 'that's no way to choose a modelling tool', given that they have realized they WILL need a tool, then surely the smart thing is to tailor their approach to (1) their own requirements, but also (2) the capabilities of a tool.
It seems like a solution -> Requirement approach, but don't we need some measure of this? No point crafting a wonderful modelling approach, then finding there is no tool to which can do it without huge modification. And when maybe a small change to the modelling approach would make it fit disproportionately better with one or other tool.
As an example, just look how us EA users have adapted our modelling approach to the lack of any usable time-based modelling - we just skip around the idea of roadmap planning which lots of people say they need. (yes, I do know there is some time-based function in EA, and no, it doesn't come close to what most customers SAY they need). But we get around it with some baselines, a bit or branching and merging, and some fast talking.
So, Aris users: what's it good at?