title: Use Case diagram for board game
body: <p>I'm creating a use case diagram for a checkers game that I programmed. How in-depth are you really supposed to go when making these? I read that they are supposed to be simple, but that is kind of vague. Do I need to create more arrows, for example between "move regular" (which means move a regular piece, as oppose to a king) and "jump"? Or is it fine not having a connection there? I just don't want to make too many arrows because it will begin to look pretty messy. Any input will be appreciated.</p>
  
  <p><img src="https://i.stack.imgur.com/cQsa5.jpg" alt="enter image description here"></p>