| <?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" xmlns:rmc="http://www.ibm.com/rmc" |
| rmc:version="7.5.0" xmi:id="-3fT4U_TQiQFAHZQp8_7GkQ" |
| name="logical_data_model,_TI3JIBtsEdu_BZ3CL1I6hw" guid="-3fT4U_TQiQFAHZQp8_7GkQ" |
| changeDate="2008-09-04T14:53:40.968-0700" version="1.0.0"> |
| <mainDescription><a id="XE_logical_data_model" name="XE_logical_data_model"></a> 
 |
| <p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
 |
| <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><span
 |
| style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">A logical data model or LDM is a graphical
 |
| representation of some of the business requirements and especially the concepts manipulated by the business member. LDM
 |
| is independent of the technology of implementation, and is mostly used&nbsp;as a communication vehicle for the business
 |
| analyst and&nbsp;to prepare the implementation of data models.&nbsp;&nbsp;</span></span>
 |
| </p>
 |
| <p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
 |
| <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><span
 |
| style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">From the point of view of an object-oriented developer
 |
| data modeling is conceptually similar to class modeling. With data modeling you identify entity types whereas with
 |
| class modeling you identify classes.&nbsp; Data attributes are assigned to entity type just as you would assign
 |
| attributes and operations to classes. Traditional data modeling is different from class modeling because it focuses
 |
| solely on data – class models allow you to explore both the behavior and data aspects of your domain, with a data model
 |
| you can only explore data issues.</span></span>
 |
| </p><br class="MsoNormal" style="MARGIN: 0cm 0cm 0pt" />
 |
| <p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
 |
| <span style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">We use UML simple class diagram to represent
 |
| a</span> <span style="mso-bidi-font-family: Arial">Logical Data Model</span> <span
 |
| style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">but&nbsp;by applying&nbsp;Agile's principle of multiple
 |
| models, it is possible to use other diagrams.</span>
 |
| </p><br class="MsoNormal" style="MARGIN: 0cm 0cm 0pt" />
 |
| <p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
 |
| <span style="mso-bidi-font-family: Arial">Logical Data Models</span> <span
 |
| style="mso-bidi-font-size: 10.0pt; mso-bidi-font-family: Arial">are used to explore the domain concepts, and their
 |
| relationships, of&nbsp;the problem domain.&nbsp; This could be done for the scope of a single project or for&nbsp;the
 |
| entire enterprise.&nbsp; LDMs depict the logical entity types, typically referred to simply as entity types, the data
 |
| attributes describing those entities, and the relationships between the entities.</span>
 |
| </p>
 |
| <p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
 |
| &nbsp;
 |
| </p>
 |
| <p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt">
 |
| Defining a logical data model prepare for future reuse, and help to build common definition of terms. This is one of
 |
| major building block for enterprise data model.
 |
| </p></mainDescription> |
| <purpose>Data modeling is the act of exploring data-oriented structures.&nbsp; Like other modeling artifacts data models can be used
 |
| for a variety of purposes, from high-level conceptual models to physical data models.</purpose> |
| </org.eclipse.epf.uma:ArtifactDescription> |
