Subdividing Data Elements
In this section, we try to find out if some elements should be broken into more simple ones. The reason for doing so is that, if an element is composed of many parts, applications will have to break it for sorting and selection purposes. Thus it's better to break the elements right now at the source. Recomposing it will be easier at the application level.
Breaking the elements provides more clarity at the UI level. Therefore, at this level we will avoid (as much as possible) the well-known last-name/first-name inversion problem.
As an example for this problem, let's take the buyer's name. During the interview, we noticed that the name is expressed in various ways on the forms:
|
Form |
How the name is expressed |
|---|---|
|
Delivery certificate ... |
Get Creating your MySQL Database: Practical Design Tips and Techniques now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
