Defining Dependencies

For the dependencies, you can record:

Name
The dependency name is optional. If specified, it reflect the post and preconditions it matches.
In Selecting Processes for Dependency Analysis, "order is created" is a suitable name for the dependency.
Where entity states have been analyzed and identified, use entity state names. These names refer to entity subtypes in a life-cycle partitioning. See the chapter "Analyzing Data." In turn, the conditions suggest more state names.
Description
Specify the post and preconditions represented by a dependency in its description and the reason for the dependency. Avoid referencing the processes that are involved because they can be added or deleted from a dependency without actually affecting the post or precondition.
In Selecting Processes for Dependency Analysis, this description would be too wordy: "An order is created by Take Order that after can be either canceled by Cancel Order or changed by Amend Order."
It also happens to be a verbal restatement of the Dependency Diagram with the condition included. If you later discover extra elementary process that is named Verify Order that depends on Take Order and is a prerequisite to Amend Order, the post and preconditions for the dependency would remain the same: An order is created. See the following illustration.
Had the names of the processes that are involved in the description of the dependency been included, it would require modification. Instead, the condition simply be stated as "an order is created."
Type of dependency