Creating data model

Designing suitable application object model (bussiness objects) is the most critical step. The model is directly affected by all application requirements, and in the end it dictates the application behaviour and shortcomings.

Possible questions about the model (application specific):

• whether a Person has one or more addresses (shipping, billing)
• whether articles are contained in article sets (multi-level hierarchy)
• whether "category" is a property of Product or its container object, or maybe an object by itself
• whether front_articles are just pointers to actual articles contained somewhere in the object tree

Possible issues about accessing objects (CMS specific):

• given the head of the object tree, how to reach certain object
• given one object, how to reach its relatives (children, parents)
• accessing objects using free search on its properties