<extend> dependency in UML -
Except the context of UML, if AB extends, then there is a subset of BA.
But in UML, this is the opposite, say, if ABC extends, there is a subset of A,
Why is it strange?
Nothing is done with its generalization / expertise. The use case is a document, not the diagram. For example, the image shown above may be from the case text using the following: Extension: In a more detailed model, the "View Account Details" on the "detail point" image will be listed on the case element. But this grating has given a very diagram in my opinion. I learned UML by first reading actually "UML distilled" by Martin Fowler. I checked that book before posting this reply and found that foulter & lt; & Lt; Expansion & gt; & Gt; Dependency is only used for usage cases, it means that the use of a case is spread to other under certain circumstances. In the following:
< P> Customer accounts look at account details Under some circumstances, the client may also be "see open order" as part of "View account details". It is also possible that customers will see "see history" as part of "view account".
& lt; & Lt; Expansion & gt; & Gt;
The use case is confused in the figure. The smallest part of the illusion is that case diagrams are not used for cases!
1A if the client clicks on the "Open Order" link - Client View Open Orders - 1B if the client clicks on the "View History" link - Consumer idea history & lt; & Lt; Expansion & gt; & Gt;
.
Comments
Post a Comment