This glossary lists key terms and symbols used in Object-Role Modeling (ORM), and briefly explains their meaning. A concise explanation of other technical terms may be found in the chapter summaries. Further details on technical terms may be accessed by using the Index.
Constraint that holds necessarily for all states of the model.
Number of roles in a relationship (unary = 1, binary = 2, ternary = 3, etc.).
Fact that is simply asserted, rather than being derived from others; also called a primitive fact or base fact.
Subtype that is simply asserted (not defined by a subtype definition).
Relationship type, usually involving at least two roles.
Either an elementary fact or an existential fact.
Fact that is primitive (not derived from others). Also called an asserted fact.
Fact type that is equivalent to a conjunction of smaller fact types
Conceptual model of the UoD structure; design that specifies what states and transitions are possible; declaration of fact types, constraints, and derivation rules
0 Divide the UoD into manageable sub-sections
1 Transform familiar examples into elementary facts, and apply quality checks
2 Draw the fact types, and apply a population check
3 Check for entity types that should be combined, and note arithmetic derivations
4 Add uniqueness constraints, and check arity of fact types
5 Add mandatory role constraints, and check for logical derivations
6 Add value, set comparison (subset, equality, exclusion) and subtype constraints
7 Add other constraints and perform final checks
8 Integrate the subschemas into a global conceptual schema
Restriction on possible or permissible states (static constraint) or transitions (dynamic constraint).
Either a coreferenced or a nested object type.
Object that is identified by means of two or more reference types in combination; hence its identification scheme involves an external uniqueness constraint.
Variable set of related fact instances.
An obligation, i.e. a rule that ought to be obeyed (but possibly may be violated).
Rule that declares how one fact type may be derived from others.
Fact that is derived from other fact types using a derivation rule
Subtype that is derived from other object types using a subtype definition.
Assertion that an object has a property, or that one or more objects participate in a relationship, where the fact cannot be split into simpler facts with the same object types without information loss. Application of an atomic predicate to a sequence of objects.
Object that is referenced by relating it to other objects (e.g., the Country that has CountryCode ‘AU’); not a value; typically, an entity may undergo changes over time; an entity is either atomic or nested (i.e. an objectified relationship); at the top level, entities are partitioned into primitive entity types, from which subtypes may be defined.
Assertion that an object exists (e.g., there is a Country that has CountryCode ‘AU’); also called a reference.
Proposition that is taken to be true by the relevant business community, where the proposition is elementary or existential (rather than being a constraint or derivation rule).
Role in an elementary fact type.
Kind of fact, including object terms and either a predicate or existential quantifier.
Restate without nesting.
Fact type with a functional role.
Role with a simple uniqueness constraint.
Forming a more general case from one or more specific cases; the inverse of specialization.
Object that may exist without participating in any elementary fact; the disjunction of fact roles played by an independent object type is optional.
An individual occurrence (one specific member of a type).
Role that must be played by all instances in the population of the object type playing the role; also called a total role.
Mode in which a proposition is expressed. In ORM 2, modalities are either alethic (expressing necessities or possibilites) or deontic (expressing obligations or permissions).
Relationship that plays some role (also called an objectified relationship).
Thing of interest; an object may be an entity or a value.
Treating a relationship as an object; also called nesting. Strictly speaking, objectification in ORM 2 distinguishes the object formed by the objectification from the original relationship, and hence involves situational rather than propositional nominalization.
Conceptual modeling method that pictures a business domain in terms of objects playing roles; it provides graphical and textual languages for verbalizing and querying information as well as various design and transformation procedures.
Set of instances present in a particular state of the database.
Proposition with object-holes in it, e.g. “... works for ...”.
Relationship used as the preferred way to reference or identify an object (or to provide part of the identification).
Mode or manner in which a single value references an entity; used to abbreviate simple reference schemes, e.g. (.code), (kg:).
Role in a reference (existential fact).
Property or association involving one or more objects.
Subtype whose instances must remain in that type for their whole lifetime (e.g, Person).
Relational mapping procedure.
Part played by an object in a relationship (unary, binary, ternary, etc.).
Subtype whose instances may leave that type during their lifetime (e.g., Child).
Fact type, some of whose instances may be derived from others, while some other instances may be simply asserted.
Subtype, some of whose instances may be derived using a derivation rule while some other instances may be simply asserted.
Object type that is properly contained in another object type (e.g., Woman is a subtype of Person).
Set of possible instances.
Repetition is not allowed in the role or role sequence spanned by the constraint; a uniqueness constraint on a single predicate is an internal UC, and a uniqueness constraint over roles from different predicates is an external UC.
Business domain (the aspects of the world that we want to talk about).
Unchangeable object that is identified by a constant; in this book a value is either a character string or a number; sometimes called a label.
The following symbol glossary covers the main graphical symbols in ORM 2 (as supported by the NORMA tool) and the corresponding symbols in ORM 1 (as supported in Microsoft Visio for Enterprise Architects).
18.221.208.183