August 9, 2007 at 9:41 am
Dear all:
The company I work for is in the midst of creating a new web application and accompanying database. It is considered "severely rapid application development" in my book, and I have a question about logistics.
When designing databases for other places (mainly as a contract employee) I tested potential designs before choosing the final one. In this case, they wish to have the database design totally done and approved before any "sandbox play". My question is (and feelings will not be hurt by answers as long as politically correct):
Is it common practice to have a database design carved in stone before actually building the database?
I've recommended a couple of concepts based on knowledge but not experience, and feel I need to test the concept before sending in a final drawing. These ideas are not Earth-shattering and would not cause a total re-design if unsuccessful in test. Any thoughts/experience on this would be greatly appreciated. Thanks-TC
August 9, 2007 at 9:59 am
I don't know if it's common practice to have a carved in stone design before doing dev work. I'd surely be ok with having a solid design plan, but which still allows for small changes (adding a column in and there or a few new tables). I've rarely seen a [bigger] project where the plan didn't have to change ANYWHERE along the way. I think it's a good idea to have a sold db design to start with, but being prepared to do small modifications... this excluding changing the full design of a whole slew of tables... and all the rest of the coded app.
August 9, 2007 at 10:04 am
I've worked for companies which finalized the database structure before a line of code was written and companies where the database structure was more of a fluid thing throughout the development process. In my experience the first method always produced a better database in terms of performance and scalability. The second was usually the product of poor project management and shifting application scope. I'm not saying that you don't make minor "tweaks" to the design throughout the development process, but having a really good ERD beforehand with all functionality required taken into account helps. Then again, that's my experience, YMMV.
August 9, 2007 at 10:05 am
As usual, I find myself agreeing with Ninja.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply