[Enterprise Extensions only]

Determining where to place a trigger point

Using Use Case Analysis to place trigger points.

Trigger points can be found during analysis by inspecting the use cases or user interaction scenarios that are typically developed as statements of requirement as input to the analysis process. A fragment of a use case is shown below:

The vehicle is entered into the system or chosen. The customer service representative attempts to locate the named driver in the system. If the driver is not found, she/he is added to the system and then picked.

Otherwise the found driver is just picked. If the vehicle is an auto, anyone between the ages of 16 and 75 can be picked as a driver. If the vehicle is a truck, only drivers 16 to 70 years old can be picked. And if the vehicle is a motorcycle, drivers 14 to 65 can be picked.

After the driver has been picked, a rate quote can be performed...

To identify potential trigger locations in use case analyses such as this one, look for certain keywords such as:

Using an Object Interaction Diagram to place trigger points

OIDs that are based on use cases can yield a number of observable patterns that can be used to identify trigger points fairly easy. Below are some of the rules to look for and where the trigger point might be placed: