The designer of a database builds a formal model of the application area or universe of discourse (UoD). The model requires a good understanding of the UoD and a means of specifying this understanding in a clear, unambiguous way. object role modeling (ORM) simplifies the design process by using natural language, as well as intuitive diagrams which can be populated with examples, and by examining the information in terms of simple or elementary facts. By expressing the model in terms of natural concepts, like objects and roles, it provides a conceptual approach to modeling.
ORM evolved from Nijssen's Information Analysis Method (NIAM) and binary relationship modeling, which were developed in Europe in the mid-1970s. Terry Halpin formalized the object role modeling notation.
External links
- Object Role Modeling: An Overview (msdn.microsoft.com)
- orm.net
- ormcentral.com
- objectrolemodeling.com
- NIAM/ORM
The Dutch successor of NIAM is continuously researched and developed and is called FCO-IM. The case tool of choice implementing this is called Casetalk. FCO-IM has some advantages for it considers only facts.
References
"Information Modeling and Relational Databases" written by Terry Halpin.
 | This computer science article is a stub. You can help Wikipedia by expanding it. |