For my homework, I have to write functional requirement of a game called downfall (see Wikipedia). We have to make this game, but with not two sides but n (any number of) sides.
In an example solution (another game), the teacher writes the functional requirements, then writes what use case they belong to.
I have created a use case diagram in which I have the player as an actor, and ChooseDial
, RotateDial
and EndTurn
as use cases:
What I dont understand are the following: Is the number of players functional requirement? Is the table having two sides a functional requirement? Is the goal of the game (getting coins from top to bottom) a functional requirement? Is a rule like coins must reach bottom in order a functional requirement?
If they are, what use case could they belong to? Is my use case diagram wrong?
I have no idea where to put these functional requirements, because I feel like they arent part of any of my use cases.