Re: Understanding Agrregates

I was referring to your article for the definition of "multiple composition". If I would name such a concept I would use something along "shared". I'm yet to encounter when you can specify all the requirements before doing the design. Usually it's a repeating process (requirements -> design -> deeper insights -> requirements) or as you said, a vicious circle ;)
 

 Of course, this doesn't have to do anything with the original question which don't have enough context to give an accurate answer. I was just trying to understand your thoughts better.
 

 Regards,
 Rikard