<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:ArtifactDescription xmi:version="2.0"
    xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.5/uma.ecore"
    xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.0" xmi:id="-3fT4U_TQiQFAHZQp8_7GkQ"
    name="logical_data_model,_TI3JIBtsEdu_BZ3CL1I6hw" guid="-3fT4U_TQiQFAHZQp8_7GkQ"
    changeDate="2007-07-17T15:45:41.742-0700" version="1.0.0">
  <mainDescription>&lt;a id=&quot;XE_logical_data_model&quot; name=&quot;XE_logical_data_model&quot;>&lt;/a> &#xD;
&lt;p class=&quot;MsoNormal&quot; style=&quot;MARGIN: 0cm 0cm 0pt&quot;>&#xD;
    &lt;span style=&quot;FONT-SIZE: 10pt; FONT-FAMILY: Arial&quot;>&lt;span&#xD;
    style=&quot;mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial&quot;>From the point of view of an object-oriented developer&#xD;
    data modeling is conceptually similar to class modeling. With data modeling you identify entity types whereas with&#xD;
    class modeling you identify classes.&amp;nbsp; Data attributes are assigned to entity types just as you would assign&#xD;
    attributes and operations to classes. Traditional data modeling is different from class modeling because it focuses&#xD;
    solely on data – class models allow you to explore both the behavior and data aspects of your domain, with a data model&#xD;
    you can only explore data issues.&lt;/span>&lt;/span>&#xD;
&lt;/p>&lt;br class=&quot;MsoNormal&quot; style=&quot;MARGIN: 0cm 0cm 0pt&quot; />&#xD;
&lt;br />&#xD;
&lt;p class=&quot;MsoNormal&quot; style=&quot;MARGIN: 0cm 0cm 0pt&quot;>&#xD;
    &lt;span style=&quot;mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial&quot;>We use UML simple class diagram to represent&#xD;
    a&lt;/span> &lt;b>&lt;span style=&quot;mso-bidi-font-family: Arial&quot;>Logical Data Model&lt;/span>&lt;/b> &lt;span&#xD;
    style=&quot;mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial&quot;>but&amp;nbsp;by applying&amp;nbsp;Agile's principle of multiple&#xD;
    models, it is possible to use other diagram.&lt;/span>&#xD;
&lt;/p>&lt;br class=&quot;MsoNormal&quot; style=&quot;MARGIN: 0cm 0cm 0pt&quot; />&#xD;
&lt;br />&#xD;
&lt;p class=&quot;MsoNormal&quot; style=&quot;MARGIN: 0cm 0cm 0pt&quot;>&#xD;
    &lt;b>&lt;span style=&quot;mso-bidi-font-family: Arial&quot;>Logical Data Models&lt;/span>&lt;/b> &lt;span&#xD;
    style=&quot;mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial&quot;>are used to explore the domain concepts, and their&#xD;
    relationships, of&amp;nbsp;the problem domain.&amp;nbsp; This could be done for the scope of a single project or for&amp;nbsp;the&#xD;
    entire enterprise.&amp;nbsp; LDMs depict the logical entity types, typically referred to simply as entity types, the data&#xD;
    attributes describing those entities, and the relationships between the entities.&amp;nbsp;&lt;/span>&#xD;
&lt;/p>&lt;br class=&quot;MsoNormal&quot; style=&quot;MARGIN: 0cm 0cm 0pt&quot; />&#xD;
&lt;br />&#xD;
&lt;p class=&quot;MsoNormal&quot; style=&quot;MARGIN: 3pt 0cm&quot;>&#xD;
    &lt;span style=&quot;mso-bidi-language: HE&quot;>A &lt;b>Fact Model&lt;/b> represents structured business vocabulary with true statement&#xD;
    like: A customer places an order. The fact model looks like the Object Role Model described by Halpin (2001). When the&#xD;
    model starts to grow the notation become quickly invisible and no more helpful, so we do not encourage to follow the&#xD;
    notation.&lt;/span>&#xD;
&lt;/p>&lt;br class=&quot;MsoNormal&quot; style=&quot;MARGIN: 0cm 0cm 0pt&quot; />&#xD;
&lt;br />&#xD;
&lt;p class=&quot;MsoNormal&quot; style=&quot;MARGIN: 0cm 0cm 0pt&quot;>&#xD;
    &lt;b>&lt;span style=&quot;mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial&quot;>A Fact Model should always include elementary&#xD;
    (atomic) fact type:&lt;/span>&lt;/b>&#xD;
&lt;/p>&#xD;
&lt;p class=&quot;MsoNormal&quot; style=&quot;MARGIN: 0cm 0cm 0pt 18pt; TEXT-INDENT: -18pt&quot;>&#xD;
    &lt;span style=&quot;FONT-FAMILY: 'Times New Roman'; mso-bidi-font-size: 10.0pt&quot;>•&lt;/span>&lt;span&#xD;
    style=&quot;FONT-SIZE: 7pt; FONT-FAMILY: 'Times New Roman'&quot;>&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/span>&#xD;
    &lt;span style=&quot;mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial&quot;>Noun:&amp;nbsp; Customer, Order, Product&lt;/span>&#xD;
&lt;/p>&#xD;
&lt;p class=&quot;MsoNormal&quot; style=&quot;MARGIN: 0cm 0cm 0pt 18pt; TEXT-INDENT: -18pt&quot;>&#xD;
    &lt;span style=&quot;FONT-FAMILY: 'Times New Roman'; mso-bidi-font-size: 10.0pt&quot;>•&lt;/span>&lt;span&#xD;
    style=&quot;FONT-SIZE: 7pt; FONT-FAMILY: 'Times New Roman'&quot;>&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/span>&#xD;
    &lt;span style=&quot;mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial&quot;>Verb:&amp;nbsp; places, briefs&lt;/span>&#xD;
&lt;/p>&lt;br class=&quot;MsoNormal&quot; style=&quot;MARGIN: 0cm 0cm 0pt 18pt; TEXT-INDENT: -18pt&quot; />&#xD;
&lt;br />&#xD;
&lt;p class=&quot;MsoNormal&quot; style=&quot;MARGIN: 0cm 0cm 0pt&quot;>&#xD;
    &lt;span style=&quot;mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial&quot;>We may use&amp;nbsp;Object Role Models to explore the&#xD;
    domain with project stakeholders but later replace them with a more traditional artifact such as an LDM, a class&#xD;
    diagram, or even a PDM&lt;/span>&#xD;
&lt;/p>&lt;br />&#xD;
&lt;br /></mainDescription>
  <purpose>Data modeling is the act of exploring data-oriented structures.&amp;nbsp; Like other modeling artifacts data models can be used&#xD;
for a variety of purposes, from high-level conceptual models to physical data models.</purpose>
</org.eclipse.epf.uma:ArtifactDescription>