jwcolby
jwcolby at colbyconsulting.com
Tue Sep 11 04:57:03 CDT 2007
I am about to undertake a ground up redesign of a client's application. This application has been in service for perhaps 8 years and, while it functions, it has some serious normalization issues. Does anyone have any suggestions for tools for mapping the BE and storing comments on design issues as I encounter them? I need to be able to document the problems, make comments about why I perceive the issue as a problem, and suggestions on what to do to remove the design problem. I also have to preserve the existing data and migrate it to the new application once complete. I have performed this task many times in the past, but usually I have done so on databases designed by "complete amateurs". This database was actually designed by someone who apparently knew a lot about normalization but just didn't get it quite right, and / or the db had tables added which should not have been implemented as they were. Thus the basic structure will stand, and yet there will be areas where entire tables or areas of the database will be deleted or redesigned to eliminate redundant data etc. I need a tool to help me document what I will be doing and why. In the absence of anything more sophisticated I will be using a simple table of "table name / field / problem description / solution / implemented" kind of thing. I just thought you guys might know of some existing tool to do this. John W. Colby Colby Consulting www.ColbyConsulting.com