76:
44:
Logical data models represent the abstract structure of a domain of information. They are often diagrammatic in nature and are most typically used in business processes that seek to capture things of importance to an organization and how they relate to one another. Once validated and approved, the
157:
A logical data model is sometimes incorrectly called a physical data model, which is not what the ANSI people had in mind. The physical design of a database involves deep use of particular database management technology. For example, a table/column design could be implemented on a collection of
56:, since this describes the semantics of the information context, which the logical model should also reflect. Even so, since the logical data model anticipates implementation on a specific computing system, the content of the logical data model is adjusted to achieve certain efficiencies.
67:' or as an alternative to the domain model. While the two concepts are closely related, and have overlapping goals, a domain model is more focused on capturing the concepts in the problem domain rather than the structure of the data associated with that domain.
83:, which "shows that a data model can be an external model (or view), a conceptual model, or a physical model. This is not the only way to look at data models, but it is a useful way, particularly when comparing models".
195:
Uses more defined and less generic specific names for tables and columns, such as abbreviated column names, limited by the database management system (DBMS) and any company defined standards
103:– where data is described in terms of tables and columns – had just been recognized as a data organization theory but no software existed to support that approach. Since that time, an
302:
American
National Standards Institute. 1975. “ANSI/X3/SPARC Study Group on Data Base Management Systems; Interim Report”. FDT(Bulletin of ACM SIGMOD) 7:2.
212:
32:) but in terms of data structures such as relational tables and columns, object-oriented classes, or XML tags. This is as opposed to a
161:
Conceptual, logical and physical data models are very different in their objectives, goals and content. Key differences noted below.
184:
Includes tables, columns, keys, data types, validation rules, database triggers, stored procedures, domains, and access constraints
107:
approach to data modelling – where data is described in terms of classes, attributes, and associations – has also been introduced.
286:
432:
189:
Non-technical names, so that executives and managers at all levels can understand the data basis of
Architectural Description
343:
104:
28:
of a specific problem domain expressed independently of a particular database management product or storage technology (
540:
315:
200:
Uses general high-level data constructs from which
Architectural Descriptions are created in non-technical terms
428:
515:
238:
510:
489:
248:
484:
336:
561:
423:
158:
computers, located in different parts of the world. That is the domain of the physical model.
80:
53:
33:
520:
258:
75:
8:
448:
329:
46:
29:
443:
397:
283:
474:
469:
453:
392:
366:
145:
36:, which describes the semantics of an organization without reference to technology.
530:
438:
100:
505:
402:
290:
253:
243:
181:
Includes entities (tables), attributes (columns/fields) and relationships (keys)
128:
52:
Logical data models should be based on the structures identified in a preceding
525:
418:
376:
555:
371:
293:. The European Process Industries STEP Technical Liaison Executive (EPISTLE).
221:
Represented in the DIV-3 Viewpoint (DoDAF V2.0), and SV-11 View (DoDAF V1.5)
141:
218:
Represented in the DIV-2 Viewpoint (DoDAF V2.0), and OV-7 View (DoDAF V1.5)
479:
64:
535:
352:
25:
121:
Helps common understanding of business data elements and requirement
60:
115:
263:
152:
321:
233:
131:
and thus prevent data and business transaction inconsistency
206:
Includes primary keys and indices for fast data access.
59:
The term 'Logical Data Model' is sometimes used as a
137:
Decreases development and maintenance time and cost
192:Uses business names for entities & attributes
553:
203:Is independent of technology (platform, DBMS)
337:
116:Reasons for building a logical data structure
45:logical data model can become the basis of a
124:Provides foundation for designing a database
110:
153:Conceptual, logical and physical data model
344:
330:
74:
282:Matthew West and Julian Fowler (1999).
87:When ANSI first laid out the idea of a
554:
325:
318:By George Tillmann, DBMS, June 1995.
178:Includes high-level data constructs
284:Developing High Quality Data Models
276:
134:Facilitates data re-use and sharing
49:and form the design of a database.
13:
14:
573:
309:
541:Data Format Description Language
351:
296:
1:
316:Building a Logical Data Model
269:
516:Core architecture data model
239:Core architecture data model
167:Conceptual data model (CDM)
7:
227:
39:
10:
578:
173:Physical data model (PDM)
91:in 1975, the choices were
70:
511:Business process modeling
498:
490:Unified Modeling Language
462:
429:Entity–relationship model
411:
385:
359:
249:Entity-relationship model
170:Logical data model (LDM)
127:Facilitates avoidance of
111:Logical data model topics
81:three level architecture
215:Viewpoint (DoDAF V2.0)
424:Data structure diagram
84:
78:
54:conceptual data model
34:conceptual data model
521:Enterprise modelling
485:Object–role modeling
259:Object-role modeling
211:Represented in the
140:Confirms a logical
47:physical data model
30:physical data model
289:2008-12-21 at the
85:
18:logical data model
549:
548:
475:Information model
470:Data-flow diagram
225:
224:
569:
531:Process modeling
346:
339:
332:
323:
322:
303:
300:
294:
280:
164:
163:
101:relational model
577:
576:
572:
571:
570:
568:
567:
566:
552:
551:
550:
545:
506:Database design
494:
458:
407:
381:
355:
350:
312:
307:
306:
301:
297:
291:Wayback Machine
281:
277:
272:
254:Database schema
244:Database design
230:
155:
146:impact analysis
129:data redundancy
118:
113:
105:object-oriented
79:The ANSI/SPARC
73:
42:
12:
11:
5:
575:
565:
564:
547:
546:
544:
543:
538:
533:
528:
526:Function model
523:
518:
513:
508:
502:
500:
496:
495:
493:
492:
487:
482:
477:
472:
466:
464:
463:Related models
460:
459:
457:
456:
451:
446:
441:
436:
426:
421:
415:
413:
409:
408:
406:
405:
400:
395:
389:
387:
383:
382:
380:
379:
374:
369:
363:
361:
357:
356:
349:
348:
341:
334:
326:
320:
319:
311:
310:External links
308:
305:
304:
295:
274:
273:
271:
268:
267:
266:
261:
256:
251:
246:
241:
236:
229:
226:
223:
222:
219:
216:
208:
207:
204:
201:
197:
196:
193:
190:
186:
185:
182:
179:
175:
174:
171:
168:
154:
151:
150:
149:
138:
135:
132:
125:
122:
117:
114:
112:
109:
89:logical schema
72:
69:
41:
38:
22:logical schema
9:
6:
4:
3:
2:
574:
563:
562:Data modeling
560:
559:
557:
542:
539:
537:
534:
532:
529:
527:
524:
522:
519:
517:
514:
512:
509:
507:
504:
503:
501:
497:
491:
488:
486:
483:
481:
478:
476:
473:
471:
468:
467:
465:
461:
455:
452:
450:
447:
445:
442:
440:
437:
434:
430:
427:
425:
422:
420:
417:
416:
414:
410:
404:
401:
399:
396:
394:
391:
390:
388:
384:
378:
375:
373:
370:
368:
365:
364:
362:
358:
354:
347:
342:
340:
335:
333:
328:
327:
324:
317:
314:
313:
299:
292:
288:
285:
279:
275:
265:
262:
260:
257:
255:
252:
250:
247:
245:
242:
240:
237:
235:
232:
231:
220:
217:
214:
210:
209:
205:
202:
199:
198:
194:
191:
188:
187:
183:
180:
177:
176:
172:
169:
166:
165:
162:
159:
147:
143:
142:process model
139:
136:
133:
130:
126:
123:
120:
119:
108:
106:
102:
98:
94:
90:
82:
77:
68:
66:
62:
57:
55:
50:
48:
37:
35:
31:
27:
23:
19:
480:Object model
367:Architecture
298:
278:
160:
156:
96:
93:hierarchical
92:
88:
86:
65:domain model
58:
51:
43:
21:
17:
15:
393:Conceptual
536:XML schema
439:Geographic
353:Data model
270:References
144:and helps
26:data model
377:Structure
556:Category
499:See also
449:Semantic
433:enhanced
419:Database
403:Physical
372:Modeling
287:Archived
228:See also
40:Overview
444:Generic
398:Logical
386:Schemas
99:. The
97:network
71:History
61:synonym
454:Common
264:FCO-IM
412:Types
234:DODAF
213:DIV-1
24:is a
360:Main
95:and
63:of '
20:or
558::
16:A
435:)
431:(
345:e
338:t
331:v
148:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
