是否有必要为每个用例都包含登录名? [英] Is it necessary to include the login for every usecase?
本文介绍了是否有必要为每个用例都包含登录名?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!
问题描述
我打算设计一个具有登录功能的系统.登录后,登录的用户可以做几件事,所以需要在这几个用例中包含登录用例.
iam going to design a system that has a login facility. After login the logged user can do several things so is it needs to include login usecase by that several usecases.
推荐答案
在大多数情况下,它只会使您的图表变得混乱.作为用例,登录既不复杂,也不会给您带来很多附加值.在包含用例和描述的文本文档中,包含需要成功登录的功能列表作为先决条件.更易于跟踪和测试.
In most cases, it will only clutter up your diagrams. Login is neither complex nor does it give you much added value as a use case. In your textual document that includes the use cases with description, include as a prerequisite a list of features that require a successful login. Easier to track and to test.
这篇关于是否有必要为每个用例都包含登录名?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!
查看全文