>It's a good question, assuming you properly spell out what you're looking for. In other posts, you mentioned Shuffle() and Deal() as methods, which I would never think of as methods attributed to a deck of cards. Cards don't shuffle or deal themselves. Those methods belong to the dealer object. ;-)

And if the dealer object is doing a weird shuffle, he may become an object of torture, performed by player objects :).

>This kind of questioning is along the right line, but be prepared for answers all over the map. When you start modeling objects, there is never a single right answer -- only variants of less wrong.

And the scope of the imaginary app is left to one's imagination. Is this a deck of cards to be operated by a physical robot dealer, or just an abstract set of cards (where the representation layer would be left to a subclass - do we have actual bitmaps for each card, or do we have 4+13 bitmaps and combine them, does the game require backside of the card to be visible at times etc etc), or do we have a real game in mind somewhere down the road.

I prefer the chicken example :).