Thanks for your answer, I send you more information about my problem.
My system is composed with several subsystem, each component have a state engine, that’s why I need to define ‘gradually’ the global state diagram to avoid the complexity.
I can illustrate my problem with the state of an andrdoid application :
- I use several diagram view as suggested stephane.
1- “Hide or not internal state”
I want to define a global view of android application, then I provide three state:
Now I want to refine the "visible Lifettime state " and I create a new state diagram with three internal state (OnStart, Foreground Lifetime,OnStop), and Of course in the “OnStart” state , I define the state of my android application in the nominal case… now I re-open the first diagram:
As you see the first simple diagram, is not very simple !!
2- The second point concerns the available trigger for a entry point , as you see I have define a trigger for the entrypoint “onstart” in the first diagram, when I create the second
the tools provides all available trigger… but In my case , only one trigger must be available. The tools doesn’t guaranty the consistency between state and internal state.
thanks for your recommendation.