Difference: 'uses', 'extends', 'includes'
Answer Posted / julian c
Include vs extends is nothing to do with 'always' or 'sometimes'. In UML 2.x these are dependency arrow stereotypes.
If the base use case is incomplete... i.e. we can not write, build, test and use it without the linked use case then it is MANDATORY that the other use case exists; this requires and <<include>>. Getting hung up on the always/sometimes issue is counter-productive.
If we can write, build, test and use the base use case without the linked use case existing at all then it is NOT dependent on it; the linked use case however describes how it may add functionality to the base use case - THAT'S WHY THE ARROW IS THE OTHER WAY and is stereotyped <<extend>>. The extending use case is OPTIONAL in that we may or may not provide that functionality at all.
The included use case is like a sub function that is called.
An extend use case can change any aspect of the base use case and in several places. Look at it this way; if I use MSWord to open the base use case, turn on track-changes and then edit it to represent changes I want to make (usually but not limited to additional functionality) the extending use case represents those tracked changes.
<<uses>> is UML 1.x and although still prominent in Visio Use Case stencils (finally fixed in Visio 2013) is deprecated.
| Is This Answer Correct ? | 2 Yes | 0 No |
Post New Answer View All Answers
What is a functional interface? What is sam interface?
Can you create an instance of an interface?
What is the practical implementation of inner classes?
How many methods are there in the serializable interface?
Explain about inheritance in oops?
explain dynamic binding
Write about abstract base classes?
What is difference between polymorphism and normalization?
Explain serialization and overriding?
Can you use virtual, override or abstract keywords on an accessor of a static property?
What is the main difference between overloading and overriding?
What is method overriding?
What is inheritance in java?
Explain about the analysis phase?
How many instances can be created for an abstract class?