Players A, B, C, and D have all stayed in the hand until the end of the betting. Player A shows an A-Q-9-8-8-6 hand. Player B lays down a A-10-10-9-8-6 hand. So far, B is winning because his pair of tens beats A's pair of eights. Player C then lays down a A-10-10-9-8-7. Now, player C is on top since his cards match all of player B's except for the last card - which is higher for him (a seven versus a six). Player D has 6-6-4-3-2, and is not in the running. If player B would have had a 7 instead of a 6, then player's A and C would have tied, and they would have split the pot.
The requirement document is now complete. Notice how it does not define the architecture nor dictate the implementation. The goal of the requirement document is to define the problem and not the solutions. The requirement document should now become the foundation on which all other decisions are based. It should guide the architecture and the implementation plan.