Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • Obviously one benefit of an ORM is that you can traverse across different objects e.g. from 'customer' to 'item bought' to 'seller'. Is there a good way of delineating where one composite object ends and the next begins? Commented Oct 9, 2014 at 15:47
  • 1
    Your functional software requirements and resulting design dictate that. Think about the information that an Invoice contains. If you were to construct a single ViewModel object to hand to a web page for display, what data would that ViewModel object have to contain? Commented Oct 9, 2014 at 15:48