While a carefully designed modelling language should facilitate the development of useful object models, it is certainly not sufficient: The language does not tell much about how to find proper abstractions and how to decide between design alternatives. There are only a few general principles that help with the design of an object model. Design patterns that outline strategies for good design to meet certain requirements are certainly useful. However, they usually stress a high level of abstraction. In other words: They are only of limited help when it comes to analyse and model a particular domain. In the end, the development of object models remains a remarkable intellectual challenge. A great deal of the corresponding expertise can only be required by developing models - and by studying examples. This report presents a number of example object models which render domains typical for corporate information systems. The examples are designed using MEMO-OML (MEMO Object Modelling Language). Therefore, they also serve to illustrate the use of MEMO-OML which contains a few concepts that are not provided by other object-oriented modelling languages.