Either you go with Geert's suggestion and use just a See events
use case or you should stay with your first one. Whether you split the See events
into private/public heavily depends on the system you are designing. So, taken that there is a need for a split (since both events will be looked at very differently) you should go with your first sketch. Here it's clear who can deal with which UC. With just a single UC you could attach a constraint like {only registered user can see private events}
.
Your 2nd one does not seem to make sense. The «extend»
is superfluous as the actor already has direct relation to the use case. The relation would mean that the extending use case is optinally performed in the course of events. So somewhere while seeing private events there's a path to also seeing public events.
最后的建议只是功能分解。与参与者没有关系的用例不是用例,因为它不会带来附加值。您可以使用通用的用例(专用/公共是的专用See event
),但我始终建议不要使用该构造。UC的泛化有些矛盾。UC必须显示给正在考虑的系统的参与者带来的独特增值。但是,如果您可以概括一下,那么它并不是唯一的。而且,与类别归纳法(其中明确定义了属性/操作替代)不同,UC缺乏此类描述,并且需要做很多解释。
本文收集自互联网,转载请注明来源。
如有侵权,请联系[email protected] 删除。
我来说两句