12:56 your use cases are not correct. To have an <<includes>> here, this will result in a requirement when a person would make a payment, so basically you are saying that the costumer has to pay in all of these methods, when you wanted to use an <<extends> instead (which makes them all optional). Also you can't connect use cases oneanother, you can only make a relationship from a use case to an actor. If you want to connect a use case to another use case, you can only add it as <<includes>> or <<extends>> cases.
@invensislearning9099