I'll extend Frank's message by saying that it's more important to find out what they want to do with the CMDB and what parts of it have operational/business value than the actual technical model of the relationships.
Too often you end up with a CMDB that is technically complete but is less useful because you didn't create it with the end-user's use cases in mind.