Object-Role Modeling (ORM) Diagrams

Design Elements — Object-role Modeling (ORM) Diagram

Related News:

New Object-Role Modeling Diagrams Solution Added to Solution Park

Examples

There are a few samples that you see on this page which were created in the ConceptDraw DIAGRAM application by using the Object-role Modeling (ORM) Diagrams solution. Some of the solution's capabilities as well as the professional results which you can achieve are all demonstrated here on this page.

All source documents are vector graphic documents which are always available for modifying, reviewing and/or converting to many different formats, such as MS PowerPoint, PDF file, MS Visio, and many other graphic ones from the ConceptDraw Solution Park or ConceptDraw STORE. The Object-role Modeling (ORM) Diagrams solution is available to all ConceptDraw DIAGRAM users to get installed and used while working in the ConceptDraw DIAGRAM diagramming and drawing software.

Example 1: Constituent Geometry ORM Diagram

This diagram was created in ConceptDraw DIAGRAM using the Object-role Modeling (ORM) Diagram library from the Object-role Modeling (ORM) Diagrams Solution. An experienced user spent 10 minutes creating this sample.

This sample represents the example of application the Object Role Modeling (ORM) for construction the scheme for the Constituent Geometry. Typically, the Constituent Geometry is applied for modeling the structure of data and description geometry of the individual constituents in a Particular Lithology. All these descriptions are founded on the descriptions on which references the descID and on the terms having the qualitative or quantitative definitions. As for the sub classes, the Constituent Geometry description includes two sub classes, these are the Grain Geometry and Body Geometry. The difference in names is connected with the difference in terminology that is used for describing the individual grain components and lithological components in a mixed rock. Both sub classes are represented in this diagram using the oval objects. These and other types of objects you see on the diagram are taken from the ORM Diagrams library included in the Object-role Modeling (ORM) Diagrams solution.

Example 2: Disjunctive Mandatory Limit ORM Diagram

This diagram was created in ConceptDraw DIAGRAM using the Object-role Modeling (ORM) Diagram library from the Object-role Modeling (ORM) Diagrams Solution. An experienced user spent 3 minutes creating this sample.

This sample represents the simple Object-role modeling (ORM) diagram, which depicts the disjunctive mandatory constraint. You can observe three entities, the black dot indicates the mandatory constraint. The disjunctive mandatory constraint is the more complex form that the mandatory constraint. It connects the roles of the same entity at the multiple predicates and moreover indicates that all objects of the entity need to be a part of some of those predicates. At this type of constraint each of the roles that are mandatory, is connected to a black dot, and each entity's object participates implicitly in those predicates, at which this entity has a role. Thus, each entity at the system has an implicit disjunctive mandatory constraint on its roles. Only the objects of an independent type are the exception and can exist without participation in predicates. Use the ConceptDraw DIAGRAM to depict other types of constraints on ORM diagram similarly easily and quickly as this one.

Example 3: Employee ORM Diagram

This diagram was created in ConceptDraw DIAGRAM using the Object-role Modeling (ORM) Diagram library from the Object-role Modeling (ORM) Diagrams Solution. An experienced user spent 5 minutes creating this sample.

This sample is an Object-role modeling (ORM) diagram that demonstrates a model of employee data, among them two dates – birthdate and hiredate, the rank, and the company car number. The employee's birthdate is the date when it was born on and the hiredate is the date when it was hired on work at this company, at this the birthdate is always less than hiredate. The Rank can take one of two values – ‘Exec’ or ‘NonExec’ and each Employee who has the Rank ‘Exec’ uses some CompanyCar, while each Employee who has the Rank ‘NonExec’ uses at most one CompanyCar. The Object-role models are typically based on the elementary facts and expressed with the aid of diagrams. At this, the ORM is attribute-free, it can be applied to all elementary facts and lets group them into the structures. The ORM approach is visual and expressive, that advantageously distinguishes it from the ER and UML.

Example 4: Fractional Analysis ORM Diagram

This diagram was created in ConceptDraw DIAGRAM using the Object-role Modeling (ORM) Diagram library from the Object-role Modeling (ORM) Diagrams Solution. An experienced user spent 10 minutes creating this sample.

This ORM diagram sample depicts the Fractional Analysis, which is a way and concept widely used for modeling the situations when some entities are composed of other entities at the specified proportions. The Fractional analysis is applied in many fields, such as the chemistry, modal mineralogy, agro sphere, where it is used for the distribution grains by size, and others. The Fractional analysis uses the constituent types, which are specified in a system classification table. The constituents are used as fractional parts of described entities and the components of Fractional analysis. If the fraction of some constituent is described as a range of scalar quantities, it is required to correct default values so to be executed the constraint "sum of fractions = 1". When the constituent is added to the analysis, it is needed to check that the sum of maximum value for all fractions is >= 1 and the sum of minimum value is <= 1.

Example 5: General Lithology ORM Diagram

This diagram was created in ConceptDraw DIAGRAM using the Object-role Modeling (ORM) Diagram library from the Object-role Modeling (ORM) Diagrams Solution. An experienced user spent 15 minutes creating this sample.

This sample depicts the General Lithology scheme in a form of ORM diagram, which was designed with the help of tools of ConceptDraw's Object-role Modeling (ORM) Diagrams solution. This scheme describes the lithology and models the structure of the lithology type definition. The definitions of general and particular lithology lie at the base of logical classification the rocks into the common lithological classes. The General Lithology has varied degrees of specificity. Some types are defined only with one aspect of lithology. This sample is constructed for the agro sphere and represents the grain sorting, such characteristics as the grain size and grain shape have great value in a process of sorting. There are listed the attributes on this diagram sample and every General lithology must have one and only one value for each attribute from the first group and a value for at least one of attributes from the second group.

Example 6: Geologic Surface ORM Diagram

This diagram was created in ConceptDraw DIAGRAM using the Object-role Modeling (ORM) Diagram library from the Object-role Modeling (ORM) Diagrams Solution. An experienced user spent 15 minutes creating this sample.

This Object-role modeling (ORM) diagram example shows the scheme for the Geologic Surface. The Geologic Surface (SurfaceID) object is the main on this scheme. It needs to have the type attribute determining the subclass membership for the surface, the attribute indicating if the surface is directed or not, as well as such characteristics as the thickness of the surface, slip vectors, age range can be also defined. The slip vectors are associated with fault surfaces, moreover, the surface can have several slip vectors, which let define the displacements respecting the fault. The age ranges are inherent and associated with Faults and Contacts, at this the Faults can have more than one associated age range, but only one age range can be associated with a Contact. You can also see the Degenerate Volume object on this diagram, which represents the entities describing the discrete or boundary layers, and is associated with a Rock Body type (RockUnitID) object.

Example 7: Object-Role Modeling Example

This diagram was created in ConceptDraw DIAGRAM using the Object-role Modeling (ORM) Diagram library from the Object-role Modeling (ORM) Diagrams Solution. An experienced user spent 5 minutes creating this sample.

This sample represents the Object-Role Modeling example designed in ConceptDraw DIAGRAM software with the use of ORM notation objects offered by the Object-role Modeling (ORM) Diagrams library from the Object-role Modeling (ORM) Diagrams Solution. The ORM is a data modeling language, which is widespread for modeling different systems in terms of system's objects and the roles played by them, for software engineering and designing relational databases. You can see in this diagram two objects Employee and Department represented by the solid ellipse objects, which are the main components of the modeled system, the values Employee Name and Department Name represented by the dashed ellipses, the vertical binary predicates and the Workplace binary predicate, in which the entities play the indicated two roles 'works_in' and 'employed'. Using the predesigned vector ORM objects from the offered ConceptDraw's Object-role Modeling (ORM) Diagrams library you can design both simple Object-role Modeling diagrams and complex with many objects.

Example 8: Object-Role Model Overview

This diagram was created in ConceptDraw DIAGRAM using the Object-role Modeling (ORM) Diagram library from the Object-role Modeling (ORM) Diagrams Solution. An experienced user spent 20 minutes creating this sample.

This ORM diagram sample represents the object-role model overview with a detailed description of ORM semantics - the special graphical symbols and notations, concepts and all composition elements used for construction the ORM diagrams. The ORM notation uses such types of objects as an ellipse for representing the entity, dashed ellipse for representing a value, single, double and triple rectangles for representing different types of predicates, arrows to represent the constraints, and many other symbols, which let make the most detailed ORM diagram. The Object-role modeling (ORM) technology is successfully used for modeling the business rules, for designing the XML schematics, for graphical representation and description the conceptual models, the data warehouses, engineering requirements and web forms. The ORM is incredibly convenient for describing the aspects of different domains of science due to the expressiveness of representing information and clearness of description the concepts and techniques applied for realization the ORM conceptual models.

Example 9: Particular Lithology ORM Diagram

This diagram was created in ConceptDraw DIAGRAM using the Object-role Modeling (ORM) Diagram library from the Object-role Modeling (ORM) Diagrams Solution. An experienced user spent 15 minutes creating this sample.

This Object-role Modeling Diagram sample represents the scheme for the Particular Lithology. It was constructed to model the concept of lithology and to descript the particular rock. The Particular Lithology is modeled as the totality of constituents and represents the set of entities associated with General Lithology. The Particular Lithology entities are used to describe the rocks, mineralogy, grain, etc. Each constituent can be employed in one or more relationships within a whole with Particular Lithology and for each role can be depicted the constituent geometry. The Particular Lithology can have different physical property attributes, such as for example color, density, sound velocity, magnetic susceptibility, refractive index, etc. This sample was designed easily and quickly by using only the ready-made objects from the ORM Diagrams library of Object-role Modeling (ORM) Diagrams solution included to Software Development area of ConceptDraw Solution Park. Besides, it contains a lot of comments and additional textual information useful for comprehension Particular Lithology concept.

Example 10: Scalar Quantity ORM Diagram

This diagram was created in ConceptDraw DIAGRAM using the Object-role Modeling (ORM) Diagram library from the Object-role Modeling (ORM) Diagrams Solution. An experienced user spent 10 minutes creating this sample.

Quantity is one of the main mathematical terms, occurred yet in ancient times. It is an abstract concept, which expresses the category of volume. The most often quantities are applied to represent the measurements that serve for extremely different purposes and to describe the special properties of real objects or phenomena of surrounding world. There are several types of quantities, they can be scalar, each value of which is expressed by one real numeric value (length, area, time, temperature, mass, volume, etc.), or vector that are characterized by value and direction (speed, force, acceleration, electric field, etc.). This sample models and represents the scalar quantity concept. The represented scalar quantities are used to define the numerical values for the whole model. The concept is modeled with several representations, as complex, as quite simple, but in each case the scalar quantity is defined with a specified unit of measurement attribute.