Hi I hope I'm posting this in the right section, if not, I apologize.
I have to make a Use Case Diagram for a game proposal I made ages ago, the only thing is I don't really understand them, like at all.
My game is just a Legend of Zelda 1 clone with grid based movement similar to Startropics and Pokemon Red.
I am required to do:
1. A list of functional Requirements with descriptions.
2. A Use Case diagram
3. A Use Case description for each Use Case on your diagram.
I don't really understand use case diagrams, I sort of get the ATM one but I don't think they work well for games. DO I need to make a different diagram for every aspect of the game or do I need to make one big one?
Also do I have the actor be the player and have all the conditions be button inputs. Or do I have the actor be the player character and have all the conditions be actions like "jump"?
I don't expect ye to do the whole thing for me, I want to learn but I don't understand examples because very few cover games.
If you could just do a small example based off my proposal to help me understand it, I would really appreciate it, thanks.