Design Challenge #2 - Create a logical data model?

You are a data modeler creating the design for a non-relational database. “Non-relational” means the underlying database does not follow relational database theory - for instance the database could be hierarchical or object oriented. It is even possible that the underlying structure will be a set of files such as XML files.  You are deciding whether you should create a normalized logical data model or just jump straight into a physical design? What would you do and why? Is there value to you and your organization in creating a logical normalized design even though it will be implemented as a very different set of structures?

Feel free in your response to include any types of assumptions you feel are important around architecture and design. Thanks to Sue Hannigan for providing the idea behind this scenario.

To read the response to this design challenge, please click here