Building Models

Search Knowledge Base by Keyword

< Back

A model must have at least one Start point, and one End point. Each block must be in a path that begins and ends with a Start and End point.

All actions except for Pools must be connected to another action by arrows or “edges. Together, these actions must form paths between Start and End points.

To connect actions other than Pools, click inside the block and drag the mouse to the following block:

VIP Test Modeller_Overview of the Modeller_7

Arrows are directional. Two Tasks connected by an arrow denote a linear step in a system’s logic, either activities performed by a user or internal to the logic of the system itself.

Tasks can have multiple Edges. This denotes the different routes through a system’s logic, determined for instance by data entered or by processes for error handling.

A “Condition” block functions like an “IF” statement, posing a condition that Tasks performed by a user or the system can fulfil. These Tasks might lead to further Tasks being performed by the system, or actions expected of the user. Alternatively, a condition can lead to further conditions.

In the abstract, a model of a system under test might reflect the linear, cause-and-effect logic of a system as follows:

VIP Test Modeller_Overview of the Modeller_8

The completed models should be directional graphs through a system’s logic, from Start events to End events. Logical processes or Tasks are ordered sequentially as steps between the start and end-point, including decisions. The “paths” from start to end points are equivalent to possible tests, with each “Task” block a test step. These tests are routes through the system’s logic in the form “IF this, THEN that, THEN that…”.

Note: Looping is not possible in the Model Editor itself. This means that a block cannot be connected back to a preceding block in its path.