Database Design Always Matters
Spend a little time upfront or a lot more time later
Issue: 13.2 (March/April 2015)
Author: Craig Boyd
Author Bio: Craig Boyd is currently a data architect for a growing consumer lending company. But in his 18 years of IT experience, he has been everything from a PC Technician, iSeries System Administrator, iSeries Programmer, Sr. Technical Lead, Data Modeler, and Oracle DBA. He lives in the great state of Texas with his wife and two kids.
Article Description: No description available.
Article Length (in bytes): 10,427
Starting Page Number: 73
Article Number: 13212
project-13212.zip Updated: 2015-03-01 18:09:04
Related Link(s): None
Excerpt of article text...
In this month's column we are going to wrap up our marathon series on working through altering a database design. We have been working our way through five steps:
Figure out the current state of the existing database
Identify the existing design flaws and determine how best to fix them
Gather requirements for the changes
Create the final design based on fixing the design flaws and the changes from the new requirements
If we have to spread the changes out over several agile iterations, how do we do that?
...End of Excerpt. Please purchase the magazine to read the full article.