“时间”用例 作为演员

发布于 2024-07-26 15:55:57 字数 128 浏览 6 评论 0原文

使用用例对根据计划定期执行(而不是作为显式用户交互的直接结果执行)的系统行为进行建模的最佳实践是什么?

如果“时间”被建模为参与者,那么描述如何使用时间来触发用例的可接受的方法是什么(例如,时间段是否可配置、有效范围等)?

What are the best practices for using use cases to model system behavior that is executed periodically based on a schedule (rather than executed as a direct result of an explicit user interaction)?

If 'time' is modeled as an actor, what are accepted approaches to describing how time is used to trigger the use case (e.g. whether the period is configurable, valid ranges, etc.)?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(3

与他有关 2024-08-02 15:55:58

最好将导致计划特定任务的参与者视为在任务实际开始时仍然是参与者:

  1. 库存文员提交拾取的零件列表
  2. 系统处理拾取的零件列表以更新库存

并添加注释,表明该任务后者发生在一夜之间。

既然我写了这篇文章,我认为时间在用例中不是问题。 在这个层面上,重要的是发生了什么以及涉及哪些参与者。 在这个阶段,何时发生并不比如何发生更重要。

It might be better to consider the actor who caused a particular task to be scheduled as still being the actor when the task actually starts:

  1. Stock Clerk submits list of parts picked
  2. System processes list of parts picked to update inventory

and add a note indicating that the latter occurs overnight.

Now that I write this, I don't think time is an issue in the use case. At this level, what's important is what happens and which actors are involved. When it happens is no more important at this stage than how.

愿得七秒忆 2024-08-02 15:55:58

时间从来都不是主要参与者,毕竟,在实例化用例时,时间不会从系统接收到有价值的东西?

我认为您将您的实施决策与您选择实现的实施决策的业务需求混淆了。

如果您可以提供定期执行的操作及其原因的高级描述,我可以详细说明。

Time is never a primary actor, after all, time doesn't receive something of value from the system when a use case is instantiated?

I think you are confusing your implementation decision with the business requirement that your implementation decision was chosen realize.

If you could provide an high-level description of what is being done periodically and why, I could elaborate.

败给现实 2024-08-02 15:55:57

调度是系统的一部分还是外部的?

如果日程是外部的,那么我就把它当作演员。 然后我们就看不到时间了。

如果调度是系统的责任,那么我认为将时间视为“敲钟”的演员(或者换句话说提供输入)可能会有所帮助。 列举时间的职责有助于时间表的设计。 然而,也会有其他演员实际制定时间表。 时间与日程安排分开。

Is the scheduling part of your system or external to it?

If the schedule is external, then I treat it as the actor. We then don't see time.

If scheduling is the system's responsibility, then I think it's may be helpful to think of time as an actor "tolling the bell", or in other words providing input. Enumerating time's responsibilities helps in the design of the schedule. However there will also be other actors who actually set the schedule. Separate time, from schedule.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文