The Guard property is defined for the Control Flow, that is created from the Decision node to the Merge node.If the extending Use Case has its own Use Case scenario, this scenario is represented in the Activity diagram - the Activity diagram is created inside the Activity under the extending Use Case.The Activity (the Behavior or the Call Behavior Action) is owned by the extending Use Case.The Call Behavior Action has the Behavior defined - the Activity which name corresponds the name of the extending Use Case.The Call Behavior Action is created for the alternative flow step of the extending Use Case.The Decision node name corresponds the name of the alternative condition.The extending Use Case with the extension point is added as an alternative flow - the Decision and Merge nodes are created.To represent the included Use Case from the Activity diagram to the Use Case scenario, you have to follow all the rules, and in addition in your project you have to connect the including Use Case with the included Use Case with the included relationship.Įxtending use case (with the extension point) If the included Use Case has its own Use Case scenario, this scenario is represented in the activity - the Activity diagram is created inside the Activity and flows are represented.The activity (the Behavior or the Call Behavior Action) is owned by the included Use Case.This Activity name corresponds the name of the included Use Case. The Call Behavior Action has the following behavior defined - the Activity.The Call Behavior Action is connected with the Control Flow relationships.The Call Behavior Action is inserted to the activity basic flow according to the order as it was inserted in the basic flow.The Call Behavior Action is created for the basic flow step of the included Use Case.The Control Flow relationships are created from the Initial Node to the first Call Behavior Action, between each Call Behavior Action, and from the last Behavior Action to the Final Node.The Final Node is created after the last Call Behavior Action.The Initial Node is created before the first Call Behavior Action.The Call Behavior Action is created for each basic flow step. ![]() The Control Flow relationships are created from the Initial Node to the Call Behavior Action and from the Call Behavior Action to the Final Node.The Final Node is created after the Call Behavior Action.The Initial Node is created before the Call Behavior Action.In the Activity diagram, the Call Behavior Action is created for the basic flow step.The name of the created Activity and Activity diagram are the same as the owning Use Case name.The Activity with the Activity diagram is created under the owning Use Case just after the first basic flow step is created.
0 Comments
Leave a Reply. |