Reuse in Use-Case Models: >, >, and Inheritance
In UML modeling, you can use an extend relationship to specify that one use case (extension) extends the behavior of another use case (base). This type of. According to your diagram your subusers can use login usecase but this Just a little remark: the display of yours include and generalization. PSD3 5. Object Notation in UML . to the second object.» A dependency, part of or inheritance relationship. Convert use case details to a sequence diagram. ▻ Objects and . Extending the Notation. ○ What we.
The registrar helps the student to enroll in seminars via the use case UC 17 Enroll in Seminar. The student pays the initial fee. The system prints a receipt.
- UML Use Case Extend
- Extend relationships
The registrar hands the student the receipt. The use case ends. Include Dependencies Between Use Cases A second way to indicate potential reuse within use-case models exists in the form of include dependencies.
An include dependency, formerly known as a uses relationship in UML v1. The best way to think of an include dependency is that it is the invocation of a use case by another one.
The blue test in Figure 2 presents an example of how you would indicate where the use case is included in the logic of the including use case. Similar to calling a function or invoking an operation within source code, isn't it? You use include dependencies whenever one use case needs the behavior of another.
Extend relationships in use-case diagrams
Introducing a new use case that encapsulates similar logic that occurs in several use cases is quite common. For example, you may discover several use cases need the behavior to search for and then update information about students, indicating the potential need for an "Update Student Record" use case included by the other use cases. Why should you bother maintaining an "Includes" and an "Extends" list in your use cases?
The answer is simple: Yes, it would be nice if everyone has access to the use-case diagram because it also contains this information, but the reality is that sometimes you use different tools to document each part of your model.
uml - Use case diagram hierarchy and associations - Stack Overflow
For example, your diagrams could be drawn using a drawing package and your use cases documented in a word processor. Some of your project stakeholders may have access to the word processor you are using, but not the drawing package.
The main disadvantage of this approach is you need to maintain these two lists in parallel with the diagram, the danger being they may become unsynchronized. Inheritance Between Use Cases Use cases can inherit from other use cases, offering a third opportunity to indicate potential reuse. Figure 1 depicts an example of this, showing that "Enroll Family Member in University" inherits from the "Enroll In University" use case.
Inheritance between use cases is not as common as either the use of extend or include dependencies, but it is still possible.
The inheriting use case would completely replace one or more of the courses of action of the inherited use case.
In this case, the basic course of action is completely rewritten to reflect that new business rules are applied when the family member of a professor is enrolling at the university.
UML Use Case "extend" and "include" relationships
Family members are allowed to enroll in the school, regardless of the marks they earned in high school, they don't have to pay any enrollment fees, and they are given top priority for enrollment in the university. Inheritance between use cases should be applied whenever a single condition, in this case, the student is a family member of a professor, would result in the definition of several alternate courses.
Without the option to define an inheriting use case, you need to introduce an alternate course to rework the check of the student's high-school marks, the charging of enrollment feeds, and for prioritization of who is allowed to enroll in the given semester.
The inheriting use case is much simpler than the use case from which it inherits. It should have a name, description, and identifier, and it should also indicate from which use case it inherits in the "Inherits From" section.
This includes any section that is replaced, particularly the pre-conditions and post-conditions as well as any courses of action.
If something is not replaced, then leave that section blank, assuming it is inherited from the parent use case you might want to put text, such as "see parent use case," in the section. The "extend" relationship is explained as follows: You are developing an e-commerce system in which you have a base use case called Place Online Order that has an extending use case called Specify Shipping Instructions.
An extend relationship points from the Specify Shipping Instructions use case to the Place Online Order use case to indicate that the behaviors in the Specify Shipping Instructions use case are optional and only occur in certain circumstances.
So the key point in the extends relationship is "optional"!
UML Use Case Include
It adds further functionality to the base use case which may be restricted by constraints. The following diagram shows this: Consider the "Order Wine" and "Serve Wine" use cases. The "Order Wine" extends the "Order Food", meaning that wine may be ordered by the customer, but not necessarily optional. Therefore the use case "Server Wine" has a condition on its extend relationship: The notation is a arrow with a white triangle at the end, basically the same that is used for defining the inheritance extends relationship in the UML class diagrams.
The figure below taken from Wikipedia shows an example: