Are you sure that (for example) contactInfo ---> address is
really a composition (or even the slightly weaker aggregation) relationship rather than just an association?
You are implying that the address is somehow
part of the contact details, but this says to me that (for example) if you have more than one customer with the same address details, your system will be forced to contain more than one copy of those address details.
Perhaps a better system would decouple the idea of an address from the idea of a customer (much as they are in the 'real world' - I don't carry my home around with me, and neither does my wife
), linked by a more general association ("lives at" "delivery address", "invoice address" etc.).
I realise that this has not actually answered your question, but because of this knd of issue I am always wary of leaping to soon to details such as whether a particular association is composition, aggregation, or something else. I tend to leave such information off my diagrams unless it's really necessary to convey a particular point.