Our current practice today: a developer asks a DBA for a table and they create it (no modeling is done). I believe that someone within our IT should be doing some logical modeling (& conceptual??) and turning that over to the DBA for the physical modeling. I am looking for some thoughts related to the following as well as any other helpful comments you may have in general:
Is the exercise of modeling common practice within your organization? And for all tables (ie temp and work types)? What is your process? Who is responsible for the logical model and physical model? (developer, business analyst, data architect, dba) What model is used for modeling data? (orm, er, uml) And what notation? (IE, Barker, ...) What case tool? Are there any good papers out there comparing the pros/cons of available tools? Anybody have any experience with universal data models? Specifically the use of Len Silvestons Finally, has anyone used the cbt product called infostructor ( http://www.agpw.com) for training and what are your thoughts on it? I really appreciate any info that you can provide. Since the existing process is so easy (from the developers point of view), you can imagine the headache of trying to implement a little more structure in the design. I believe that since we are relatively small today, we can get away with poor planning, but someday as we grow it will come back to haunt us. -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Tracy Rahmlow INET: [EMAIL PROTECTED] Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
