This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
In JPwH's Caveat Emptor domain model (Fig 4.1) it uses 2 associations between Bid and Item classes to represent the successful bid must be from the Set of associated Bid instances. I'm not confortable with this design. For one thing, it is difficult to represent in UML that the associated successful Bid instance must be in the Set of all Bid instances associated with this Item.
I just want to know is there any better way to model this?