UML_Lec05_用例_用例图.pptVIP

*/55 * UML Lecture_UC, Author: NK Jiang */55 用例之间的泛化关系 考虑订单管理系统（Order Management System）的部分用例模型 It is useful to separate ordinary Customer from Internet Customer, since they have slightly different properties. However, since Internet Customer does exhibit all properties of a Customer, you can say that Internet Customer is a specialization of Customer, indicated with an actor-generalization. The concrete use cases in this diagram are Phone Order (initiated by the Customer actor) and Internet Order (initiated by Internet Customer). These use cases are both variations of the more general Place Order usecase, which in this example is abstract 6、用例图中的关系 ： 案例 */55 * UML Lecture_UC, Author: NK Jiang */55 6、用例图中的关系：案例 用例之间的泛化关系 */55 * UML Lecture_UC, Author: NK Jiang */55 6、用例图中的关系：包含关系 在分析和整理系统用例的时候，除了使用泛化关系，还可能用到 包含关系 include和 扩展关系 extend。 UML把包含关系和扩展关系表示为”依赖关系“的构造型 包含关系和扩展关系的构造标记分别是 include和extend 千万注意 此时依赖关系的方向！！ 包含关系(include)： 位于两个用例之间的包含关系意味着基用例显式地在其指定位置将另一个用例（子用例）包含进来, 使其成为自己的行为的一部分。 包含关系可用于提取共用的用例。 在具有包含关系的两个用例中， 被包含的那个用例不能单独存在，它只能以实例的形式存在于包含它的用例之中。 */55 * UML Lecture_UC, Author: NK Jiang */55 6、用例图中的关系：包含关系 One step in A calls the use case B A is called including use case, B is called included use case A is “base Usecase”, B is “sub Usecase ” in former versions of UML, you find the stereotype use instead of include include relationship is used to sort out common behavior across multiple use cases an included use case B for just one including Read: B is included in A */55 * UML Lecture_UC, Author: NK Jiang */55 6、用例图中的关系：包含关系 Example : include */55 * UML Lecture_UC, Author: NK Jiang */55 6、用例图中的关系：包含关系 Traps when using 《include》 《 include 》 is more than functional decomposition never introduce an included use case before you have written two or more identical sections in two or more including use cases including use case often becomes a shell without own value keep in mind that each use case should correspond to an actors goal Included use case takes on a lif