Is it acceptable to include a larger use case when a single feature of this case is used?

0

I've created a use case diagram, however, I'm not sure how to use the UML elements and the coherence of the diagram itself. See diagram:

My question is focused on inclusion relationship between Generate Statistics and Keep Tasks . The keep task use case is responsible for listing the assigned tasks, so I figured it would be correct to indicate that Generate Statistics includes the / strong> since it would need to access the task listing functionality in order to consolidate statistical data. Is this view correct / consistent within the proposed use case diagram?

    
asked by anonymous 01.12.2018 / 03:26

0 answers