Object–role modeling: Difference between revisions

Content deleted Content added
This article is not about Terry Halpin. Terry Halpin has not authored 6 books on Object-Role Modeling.
Filled in 2 bare reference(s) with reFill 2
Line 7:
 
The term "object-role model" was coined in the 1970s and ORM based tools have been used for more than 30 years – principally for [[data modeling]]. More recently ORM has been used to model [[business rules]], XML-Schemas,
[[data warehouse]]s, requirements engineering and web forms.<ref>{{Cite web|url=http://logicbloxsecure.pbworks.com/ferror/Paper+Jarrar+-+automated+reasonning+on+ORMwiki?wiki=logicblox|title=Workspace not found|website=secure.pdfpbworks.com|accessdate=May 31, 2020}}</ref>
 
== History ==
Line 40:
[[Fact-based modelling]] includes procedures for mapping facts to attribute-based structures, such as those of ER or UML.<ref name="orm.net"/>
 
Fact-based textual representations are based on formal subsets of native languages. ORM proponents argue that ORM models are easier to understand by people without a technical education. For example, proponents argue that object-role models are easier to understand than declarative languages such as [[Object Constraint Language]] (OCL) and other graphical languages such as [[Unified Modeling Language|UML]] class models.<ref name="orm.net"/> Fact-based graphical notations are more expressive than those of ER and [[Unified Modeling Language|UML]]. An object-role model can be automatically mapped to relational and deductive databases (such as [[datalog]]).<ref>{{Cite web|url=http://www.ormfoundation.org/files/folders/orm_2010/entry2360.aspx|title=P:11 Mapping ORM To Datalog - an Overview - The ORM Foundation|website=www.ormfoundation.org|accessdate=May 31, 2020}}</ref>
 
=== ORM 2 graphical notation ===