何时应将系统作为参与者包含在用例图中? [英] When a system should be included as an actor in use case diagram?

问题描述

我正在为新系统制作用例图.我想知道何时应该将系统作为参与者包含在用例图中?

I'm making a use case diagram for a new system. I'm wondering when a system should be included as an actor in use case diagram?

谢谢.

推荐答案

如另一个答案所述，参与者是与正在开发的系统交互的系统或角色.如果某个系统在您正在开发的系统之外，并且它直接与您正在开发的系统交互，则您应该在用例中包含该系统作为参与者.

As stated in another answer, an actor is a system or role interacting with the system under development. You should include a system as an actor in a use case if it is outside the system you are developing, and if it directly interacts with the system you are developing.

这很重要，因为您需要定义系统的边界，即它的范围和接口.将系统包含为参与者将清楚地说明正在开发的系统的要求，以便为该参与者系统提供合适的接口.

This is important because you need to define the boundary of your system, which means its scope and interfaces. Including a system as an actor will clearly state the requirement for your system under development to provide a suitable interface for that actor system.

这篇关于何时应将系统作为参与者包含在用例图中?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！