Published by Christian on Mon, 10/27/2014 - 13:45
I wrote prior to the release of GraphWalker 3. So keep in mind the not all information in this article is valid for GW3. I'll make an updated version soon.
When modeling for a GUI of a system. It can be hard to find the best way for representing the modeled behavior on the system.
One have to think about haw to model what the tests interacts with. For bigger structures there are several approaches. Here are two approached, which are
The Start approach for modeling is exactly what the name states. The structure for modeling is represented by making the model take a star like shape.
This could example be a model of navigation of Menu and a main screen in an application.
A model for getting to all the menu entries, verifying the transition and back to main screen. Could be modeled like below.
And applied in a bigger scope, where there can be several levels of structures.
Here the example could be the menu from before and then going further from the main screen, into a similar structure.
And on to the next.
This could be represented like this.
Another approach for solving the issues with supplying overview of a model can be use of a hieratical approach for modeling.
Here the same examples as before are solved.
First example 1:
Then example 2:
These models are completely identical, except from the layout design. And it is clear that one approach is more suitable that another for a specific visual
challenge when modeling.
Here are two other examples, where the picture of what approach is the most communicate able, may shift a bit.
Here it is quite clear that sometimes the best way to create an overview on the model, is to enable to model being viewed in one screen, with out panning
or zooming to much.
The Circular approach is in this case easier to make fit in one screen compared to the hieratical approach, which in this case, is quite impossible to make
fit for easy communication.