Design Challenge #12 - Logical Data Modeling in Practice
|
The Logical Data Model (LDM) is a model showing the rules behind how something works independent of context. Context includes factors such as database platform, reporting tools, and usage requirements. The LDM purely focuses on content, showing how a business area or application work at a point in time. This is the theory, but in practice what else do we typically include on the LDM? For this design challenge, we would like to know from a practical viewpoint what you typically show on a LDM. There are no wrong answers here. Simply answer Yes, No, or Sometimes to the following questions and feel free to add comments to explain your response.
Employee Hire Date
Employee End Date Original Product Name (Note not necessarily what the product name is today but what it was when the product first appeared in the marketplace.) First Salesperson Id (The relationship between a salesperson and a customer stores not just the current relationship but also the relationship of the salesperson who first made contact with the customer.) Gross Sales Amount (There is a calculation that produces this measure.) Customer Source System Id (Note this is the unique identifier to a customer in the Order System. It is a surrogate key.) Monthly Sales Reporting Entity (This is a summary view of order line details.) Employee Access Id (An employee foreign key on the Claim entity which is used to enforce security as to which employee is allowed to view which Claims.) |