J. Ambrose Little has posted a great article over on CoDe Magazine's website about why using Dataset and data driven designs are a bad idea.

To expand on his article a little bit try this exercise. Go to any one of your customers and ask them to describe any business process that they currently use, now take note of how your customer describes the process. They will describe behaviours, responsibilities, and even the actual objects themselves to you.

If the customer sounds something like this then the solution that you design and model for them may be a great candidate for data driven design:

"We take all of our documents that need to be shipped to headquarters, and staple the related documents together (because we need to maintain the relationships between them), next we put them into a generic box and write "documents" on it with a marker (because the box needs a name silly). 

After they are in the box we send them using ground mail (because air mail is too fast and expensive) to corporate headquarters. Someone at corporate headquarters then takes the documents and does something with them, we hope that they make it to the right department and that they are used correctly."