[Valmont]

Nonono, that is not a concept.
These are details. We are not interested in details. I am not interested in rules. We want to work towards a design. A design is a simple protype from wich we can build up code.
But before we can make a design, we need a concept. After the concpept I do an analysis. After the analysis, we are ready for the design. Then after that we will code. Then when we code, we refine our analysis and design along the way. We can't be perfect. Happens on multi-billion dollar bridge engineering projects as well.

Later more on that!

So answer these questions first:
1) Who are or what is involved.
Example: cards are involved. The Black Jack game is involved. Players are involved. Any Card Game could be involved.
2) What are these things?
Example: Black Jack game is a special Card Game. It's speciality is recognized by its typical rules basically. Players have a name and have Cards and Play Card Games. Could be Black jack.
3) How do they interact?
Example: Players receive card(s). The deck of cards needs to be shuffled. Cards don't want to know anything about wich game they are involved with. Players don't have to know what game exactly they are playing (believe it, it is true!).

Etcetera. Think like this. Pretend you playing games with me and your buds. What happens over there on an abstract level (in general). Write it down. No pictures, no code, no heavy details. Your best but simple english.

Can you think of more relevant questions?

Have you figured out what we are doing? We are communicating closely. That's how we setup a concept. Together. But you have the ideas. Communicating is the very first step, and a "must" to build up the concept.

NOTE: From now on we both need to work hard. I'll be there, but make sure are there too.