Interested to Buy Any Domain ? << Click Here >> for more details...
Difference: 'uses', 'extends', 'includes'
- 7 Answers
- 41040 Views
- Cognizant, Protech, TY, University, I also Faced
- E-Mail Answers
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
Does java support multiple inheritance? if not, what is the solution?
Can a class implement two interfaces having default method with same name and signature?
What is the difference between public, private and protected access modifiers?
How to define an interface?
What is virtual?
How do I make sure that an object is released in code such as a connection or file object?
What are the types of polymorphism?
Difference between abstraction and implementation hiding ?
Define Initialisation Purpose.
What is the benefit of Composition over Inheritance?
What is an abstract property. Give an example?
Can an interface have an inner class?
Classes and structs support inheritance. Is this statement true or false?
Explain about realistic modeling?
Can we override static methods? Why?
