uml - Activity diagram of use-case, do I include <<includes>> in it? -
if i'm example making activity diagram (flowchart) of "update component", need include "show available component updates" activity diagram in 1 too? different use-cases, "update component" includes "show available component updates"
thanks.
contrary "one sequence diagram per 1 use case scenario" best practice, there's no rule (as far know) how broad in scope should activity diagram be.
the rule applies here "use level of detail makes things clear enough readers".
i think it's best justified the guru said in interview mark collins-cope objective view magazine on sep 12, 2014
grady booch, creator of unified modelling language (uml):
"the uml should used reason alternatives. put diagrams. throw use cases against it. throw away diagrams write code against best decision. repeat (and refactor)"
for instance activity diagram in
shows more use cases @ same time. each lane belonging 1 actor described 1 separate use case
Comments
Post a Comment