Re: any ever work with Use Cases to model a database?

• Original Message -----

> What experiences have you had? If not what kind of requirements documents do you use? Im particularly interested in
people who have worked on projects with relational back ends and object oriented front ends. It seems very difficult to get these two models to work together cohesively.

We used RUP and URL models as well as their use cases. Worked quite well. Once the BAs finished their URL object model and use case models, it was a matter basically of the lead Java designer and the lead Oracle designer getting together and hacking out a preliminary logical data model into Designer. Then the Oracle guys went away for a few days to hack out the final design, which then got reviewed by the Java designers to make sure it did everything they expected. Then it was on to the usual entity->table antics of Designer...

All the db interface was handled by PL/SQL packages, one per table or logical "object". All access was through these, using object types as parameters. It works well with JDBC and is tremendously fast.

Cheers
Nuno Souto
nsouto_at_optusnet.com.au

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: Nuno Souto
  INET: nsouto_at_optusnet.com.au

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).