Use case diagrams (include) contained in the second usage "function of a use case is overmuch, can be broken down into smaller case" with "must call every time, when performing a basic use cases included use cases" conflict?
Like the courseware example, can choose to "add student record" instead of "delete student record" and "modify student record
"
good lost, a little don't understand 