Skip to main content

The Data Model Resource Book, Volume 1: A Library of Universal Data Models for All Enterprises, Revised Edition

The Data Model Resource Book, Volume 1: A Library of Universal Data Models for All Enterprises, Revised Edition

Len Silverston

ISBN: 978-0-471-38023-8

Mar 2001

560 pages

In Stock

$75.00

Description

A quick and reliable way to build proven databases for core business functions

Industry experts raved about The Data Model Resource Book when it was first published in March 1997 because it provided a simple, cost-effective way to design databases for core business functions. Len Silverston has now revised and updated the hugely successful 1st Edition, while adding a companion volume to take care of more specific requirements of different businesses.

This updated volume provides a common set of data models for specific core functions shared by most businesses like human resources management, accounting, and project management. These models are standardized and are easily replicated by developers looking for ways to make corporate database development more efficient and cost effective.

This guide is the perfect complement to The Data Model Resource CD-ROM, which is sold separately and provides the powerful design templates discussed in the book in a ready-to-use electronic format. A free demonstration CD-ROM is available with each copy of the print book to allow you to try before you buy the full CD-ROM.

Foreword.

Acknowledgments.

About the Author.

Introduction.

People and Organizations.

Products.

Ordering Products.

Shipments.

Work Effort.

Invoicing.

Accounting and Budgeting.

Human Resources.

Creating the Data Warehouse Data Model from the Enterprise Data Model.

A Sample Data Warehouse Data Model.

Star Schema Designs for Sales Analysis.

Star Schema Designs for Human Resources.

Additional Star Schema Designs.

Implementing the Universal Data Models.

Appendix A: Logical Data Model Entities and Attributes.

Appendix B: Data Warehouse Data Model Tables and Columns.

Appendix C: Star Schema Design Tables and Columns.

How to Use the CD-ROM Product.

Other Reusable Data Model and Data Warehouse Design Resources.

Index.
"I thought the models in the books were well thought out and adequately explained" (Computer Shopper February 2002)
ChapterPageDetailsDatePrint Run
102nd to last paragraph, last sentence
Change from: For example, each INFORMATION ORGANIZATION
Change to: For example, each INFORMAL ORGANIZATION

562nd paragraph with the Contact Mechanism Purpose section, first sentence
Change from: ... each PARTY CONTACT MECHANISM must have
Change to: ... each PARTY CONTACT MECHANISM may have

861st paragraph, first sentence
Change from: The ITEM VARIANCE entity ...
Change to: The INVENTORY ITEM VARIANCE entity ...

1102nd paragraph, last sentence
Change from: ORDER ITEM that is for a product feature that is ordered for an ORDER ITEM that is for a product feature.
Change to: ORDER ITEM that is for a product to an ORDER ITEM that is for a product feature, which is ordered for the former.

134First paragraph
Change from: This entity would maintain which SALES ORDER ITEMs fulfilled which REQUIREMENT ITEMs ...
It would also maintain which PURCHASE ORDER ITEMs are fulfilled by the REQUIREMENT ITEMs Change to: This entity would maintain which SALES ORDER ITEMs fulfilled which REQUIREMENT ...
It would also maintain which PURCHASE ORDER ITEMs are fulfilled by the REQUIREMEN

145Third paragraph with the Agreement Definition section, first sentence
Change from: ADDENDUMs modify the agreement
Change to: ADDENDUMs (see Figure 4.13) modify the agreement

1712nd paragraph, after 4th sentence
Change to: After the 4th sentence that ends with "that stores the details of the receipt.", insert the following sentence:
However, the SHIPMENT PACKAGE may exist without having a SHIPMENT RECEIPT, for instance on outgoing shipments when the organization assembles something into a package. So there is only a mandatory relationship from SHIOPMENT RECEIPT to SHIPMENT PACKAGE.

243Model 7.4 Invoice Status and Terms
In diagram 7.4 in INVOICE ITEM entity, attribute "unit price" should be changed to "amount"

246Model 7.5 Billing for Shipment items
Billing for Shipment items, Figure 7.5 Relationship names from and to SHIPMENT ITEM BILLING should be changed.
Change the relationship names:
- from SHIPMENT ITEM to SHIPMENT ITEM BILLING to "billed via"
- from SHIPMENT ITEM BILLING to SHIPMENT ITEM to "of"
SHIPMENT ITEM BILLING to INVOICE ITEM to "for"
INVOICE ITEM to SHIPMENT ITEM BILLING to "the billing for"

250Model 7.7 Billing for order items
Billing for order items, Figure 7.7 Relationship names from and to ORDER ITEM BILLING should be changed.
Changed the relationship names:
- from ORDER ITEM to ORDER ITEM BILLING to "billed via"
- from ORDER ITEM BILLING to ORDER ITEM to "of"
ORDER ITEM BILLING to INVOICE ITEM to "for"
INVOICE ITEM to ORDER ITEM BILLING to "the billing for"

271Accounting transaction details diagram, figure 8.3a--Relationship should be mandatory
Relationship from ACCOUNTING TRANSACTION to the TRANSACTION DETAIL shows a dotted line and therefore that it is optional.
Relationship from ACCOUNTING TRANSACTION to the TRANSACTION DETAIL should be mandatory in both directions and therefore it should be a solid line all the way across.

271Accounting transaction details diagram, Figure 8.3a--Recursive relationship error
The recursive relationship around the TRANSACTION DETAIL is shown incorrectly as a solid line.
The recursive relationship around the TRANSACTION DETAIL should be optional and therefore be a dotted line throughout the line.

271Accounting transaction details diagram, Figure 8.3a--Relationship name missing
The relationship from ORGANIZATION GL ACCOUNT to TRANSACTION DETAIL does not have a relationship name.
The relationship name from ORGANIZATION GL ACCOUNT to TRANSACTION DETAIL should be "associated with".

277Accounting transaction details diagram, figure 8.3b--Relationship should be mandatory
Relationship from ACCOUNTING TRANSACTION to the TRANSACTION DETAIL shows a dotted line and therefore that it is optional.
Relationship from ACCOUNTING TRANSACTION to the TRANSACTION DETAIL should be mandatory in both directions and therefore that it should be a solid line all the way across.

277Accounting transaction details diagram, Figure 8.3b--Recursive relationship error
The recursive relationship around the TRANSACTION DETAIL is shown incorrectly as a solid line.
The recursive relationship around the TRANSACTION DETAIL should be optional and therefore be a dotted line throughout the line.

297Overall Accounting and budgeting model, Figure 8.12--Relationship should be mandatory
Relationship from ACCOUNTING TRANSACTION to the TRANSACTION DETAIL shows a dotted line and therefore that it is optional.
Relationship from ACCOUNTING TRANSACTION to the TRANSACTION DETAIL should be mandatory in both directions and therefore that it should be a solid line all the way across.

302Error in Figure 9.2
Relationships from EMPLOYMENT are related to PERSON ROLE and ORGANIZATION ROLE
Relationships from EMPLOYMENT should be to EMPLOYEE and INTERNAL ORGANIZATION

444Error in referece to table
In the 2nd paragraph, first sentence, Table 15.13 should be Table 15.12

485Error in PRODUCT CATEGORY ROLLUP attribute names
PARTY TYPE ID MADE UP OF
PARTY TYPE ID PART OF
Should be:
PRODUCT CATEGORY ID MADE UP OF
PRODUCT CATEGORY ID PART OF

Appendix A485, 486Errata in text - Pages 485/486 (Appendix A)
Currently Reads:
PRODUCT INCOMPATABILITY

Should Read:
PRODUCT INCOMPATIBILITY
26-Apr-16

Appendix ALogical Data Model Entities & Attributes, BUDGET ITEM entity, BUDGET_TYPE_ID
The attribute BUDGET_TYPE_ID should not be part of the BUDGET ITEM entity

Appendix ALogical Data Model Entities & Attributes, ORDER ITEM entity, BUDGET_TYPE_ID
This attribute should not be in the entity ORDER ITEM. Delete the last line in the ORDER ITEM that shows BUDGET_TYPE_ID as an attribute.

Appendix ALogical Data Model Entities & Attributes, BUDGET SCENARIO IMPACT entity, BUDGET_TYPE_ID
This attribute should not be in the entity BUDGET SCENARIO IMPACT. Delete the line in the BUDGET SCENARIO IMPACT entity that shows BUDGET_TYPE_ID as an attribute.

Appendix ALogical Data Model Entities and Attributes, BUDGET REVISION IMPACT entity, BUDGET_TYPE_ID
This attribute should not be in the entity BUDGET REVISION IMPACT. Delete the line in the POSITION entity that shows BUDGET_TYPE_ID as an attribute.

Appendix ALogical Data Model Entities & Attributes, REQUIREMENT BUDGET ALLOCATION entity, BUDGET_TYPE_ID
This attribute, BUDGET_TYPE_ID, should not be in the entity REQUIREMENT BUDGET ALLOCATION. Delete this first attribute and its associated values of "yes"yes" and "id", and move the BUDGET_ITEM up to be the first attribute in this entity.

Appendix ALogical Data Model Entities & Attributes, BUDGET entity, BUDGET_TYPE_ID
The first column for BUDGET_TYPE_ID should be "no" since it is not part of the primary key

Appendix AEntity FACILITY has missing attribute
Entity FACILITY is missing the PART OF FACILITY ID attribute which does occur in Volume 2 . Need to add PART OF FACILITY ID attribute as part of the FACILITY just after the FACILITY row and the column values are "no" "yes" "ID"

Appendix ALogical Data Model Entities and Attributes
FINANCIAL ACCOUNT should show another attribute (another row) named FINANCIAL ACCOUNT TYPE ID with values of "no" "yes" "ID"

Appendix ALogical Data Model Entities and Attributes
The first attribute in FINANCIAL ACCOUNT TYPE should be FINANCIAL ACCOUNT TYPE ID instead of FINANCIAL ACCOUNT ID

Appendix A464Logical Data Model Entities and Attributes
The word FINANCIAL ACCOUNT TRANSACTION is repeated for the field ENTRY DATE. This is not correct. The entity name should only be printed once for the first attribute.

Appendix A464Logical Data Model Entities and Attributes
Only the attribute FINANCIAL_ACCOUNT_TRANSACTION_ID should be marked "yes" for the PK column. The field FINANCIAL ACCOUNT ID should have "no" in the first column indicating that it is not a primary key. Also the field FINANCIAL_ACCOUNT_TRANSACTIONID should be FINANCIAL_ACCOUNT_TRANS_ID instead.

Volume 1 CD-ROMCD Error with "description" field
REASON should have the "description" field as an attribute and not part of the primary key.

Volume 1 CD-ROMCD Error with key for ORDER_ITEM_ROLE
ORDER_ITEM_ROLE does not contain the order_item_seq_id as part of its key. ORDER_ITEM_ROLE should contain the order_item_seq_id as part of its key.

Volume 1 CD-ROMCD Error: Missing attributes for AGREEMENT
AGREEMENT table should have a "description" and "from date" attributes. Add "description" and "from date" attributes to AGREEMENT.

Volume 1 CD-ROMCD Error with relationship from ORDER ROLE to ORDER ITEM ROLE
Relationship from ORDER ROLE to ORDER ITEM ROLE is incorrect and should be moved. Was changed to a relationship from ORDER ITEM to ORDER ITEM ROLE.

Volume 1 CD-ROMCD Error with relationship with INTERNAL ACCTG TRANS
INTERNAL ACCTG TRANS should be related to INTERNAL ORGANIZATION and not PARTY ROLE. INTERNAL ACCTG TRANS should be related to INTERNAL ORGANIZATION and not PARTY ROLE.

Visit these related products by Len Silverston

For more information about this and the author's other data model products, visit this site.