Business Rules approach to design?

I know this is big in the ODTUG circles. Has anyone used this approach to design databases? Seems promising. Though the hardest part would be in convincing the 'i just want to code' folks to adapt it.

I havent really read that much into it. It also appears that the level of skill and experience required at the upper levels of the project would have to be quite high to make this work.

anyone have an opinion?

(see jared, now we have a database design post).

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: <rgaffuri_at_cox.net
  INET: rgaffuri_at_cox.net

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (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).