Object Role Modeling
|
Designing a database involves building a formal model of the application area or universe of discourse (UoD). To do this properly 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.
Early versions of object role modeling were developed in Europe in the mid-1970s (for example, binary relationship modeling and Nijssen's Information Analysis Method (NIAM)).
External links
- Object Role Modeling: An Overview (msdn.microsoft.com) (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dv_vstechart/html/vstchvsea_ormoverview.asp)
- orm.net (http://www.orm.net)
- ormcentral.com (http://www.ormcentral.com)
- objectrolemodeling.com (http://www.objectrolemodeling.com)
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.
- Fully Communication Oriented Information Modeling (http://www.fco-im.com/Literature_Article_FCO.html)
- FCO-IM Home Page (http://www.fco-im.com)
- CaseTalk, The FCO-IM casetool (http://www.casetalk.com)