July 2001
Intermediate to advanced
656 pages
15h 51m
English
Suppose a use case's text should not be modified (at least not significantly) for some reason. Perhaps continually modifying the use case with myriad new extensions and conditional steps is a maintenance headache, or the use case has been baselined as a stable artifact, and can't be touched. How to append to the use case without modifying its original text?
The extend relationship provides an answer. The idea is to create an extending or addition use case, and within it, describe where and under what condition it extends the behavior of some base use case. For example:
UC1: Process Sale (the base use case)... Extension Points: VIP Customer, step 1. Payment, step 7. Main Success Scenario:
|
Read now
Unlock full access