uml - Why is it said "Collaboration" realizes "Use case" rather than vice versa? -
i studying uml. have confusion realization , collaboration.
consider diagram (i hope diagram correct)
"make call" collaboration. "connect destination" use case.
according book , various resources, read "make call" realizes "connect destination".
but far understand, collaboration logical concept use group repetitive pattern(as in design patterns). use cases(which have own diagrams) ones implement them (indirectly, use cases have related class diagram. classes must implementing them).
so shouldn't "use cases" realize "collaboration"?
what getting wrong here?
the source of confusion java, have interfaces, , classes implement them. class implements interface. isn't realization same implementation?
what adds confusion collaboration diagram, seems have nothing collaboration.
because first have use case. tells added value of system is. , there's story how value achieved. start thinking how system under consideration (suc) realize (hence name) use case. construct collaborations show how class design working towards fulfillment of single goals in use cases. can have multiple collaborations either show different aspects or variants of suc.
regarding diagram: have dependencies connect destination
2 other use cases. that's not correct. use cases represent individual added value suc brings actors. can not depend on each other. use cases of suc represent total added value. people try functional decomposition use cases , add lot of include/extend dependencies. not lead meaningful use cases , loose focus. is, don't show added values stray around technical possibilities.
Comments
Post a Comment