More Database Design Mistakes To Avoid
Architecture Mistakes to Avoid
The saying goes, a picture is worth a thousand words.
If an organization has a good database model, with meaningful table and field names, a look at the model should give you a pretty good idea what the system does.
Like a picture, when you look at a model, it’s supposed to communicate. Consider a model car, or airplane, or a scale model of building.
Without a model or picture, can you communicate how to build the special research car, XOF1? How it runs? Or what it looks like?
Similarly, can you look at an ERD (Entity Relationship Diagram) diagram your of database, and have a pretty good idea of the system does? Or not?
At so many places, I’ve have to look in many places to understand the system.
– Many queries to the Oracle Data dictionary
– Values in database fields.
– Rows in database tables.
– Extensive data analysis.
– Requirements documents, that don’t give any specifications, most always outdated. Read the rest of this entry »
You must be logged in to post a comment.