Generalization between use cases is allowed, but generally discouraged by a lot of practitioners. Generalization: You could specialize make a payment with pay by cash and pay by credit card. This would be more appropriate because the main use cases relies in the result of the included use cases and is incomplete without them. Include: You can use an include relation to (conditionally) include the other use cases behavior into your main use case. Use cases should be about the main goals a user should have when using the system. via internet-enabled rubbish collection, bins and fleet management systems. This is probably the best option as your use cases are way too granular anyway. A smart city uses information and communication technology (ICT) to improve. You can create alternate scenarios for the different payment options. There are several alternative solutions to using extensions in this case.Ī single use case: Simply incorporate the extending use cases into the main make a payment use case. This is clearly not the case since you need the extending use cases to have a meaningful and complete behavior. So your use case make a payment should be indedepent from the extending use cases pay by credit card and pay by cash. Hand, the extending UseCase typically defines behavior that may not The extended UseCase is defined independently of the extending UseCaseĪnd is meaningful independently of the extending UseCase. The problem is however that the extensions should not be extensions at all. The identification of the extension points is correct.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |