我处在一个新的工作环境中,我看到分析师用以下方式编写用例
方式1
Use Case 1
basic flow
1. task A
2. task B
3. task C
4. task D
Alternate Flow 1
1. task A
2. task B
3. task E
4. task F
Alternate Flow 2
1. task A
2. task B
3. task G
4. task H
* Certain steps (e.g. 1 and 2) are repeated in alternate flows
方式2
basic flow
1. task A
2. task B
3. task C
4. task D
Alternate Flows
1.Use case 2
2.Use case 3
*Refer to other use cases as alternate flows
看看Cockburn的书,我发现在每个用例中总是只有一个备用流程部分。
所以它会像
Use Case 1
basic flow
1. task A
2. task B
3. task C
4. task D
Alternate Flow
3a. task E
4a. task F
3b. task G
4b. task H
我寻求的澄清是
1. Would you have multiple alternate flow 'sections' for a single use case?
2. Does it make sense to refer to other use cases as alternate flows?
答案 0 :(得分:0)
出于您所描述的目的,请考虑绘制活动图,或绘制BPMN流程图。
您描述的建模目标超出了用例图的范围。