Return-Path: Received: from ensim.rackshack.net (root@localhost) by orafaq.net (8.11.6/8.11.6) with ESMTP id h9BB3sI19503 for ; Sat, 11 Oct 2003 06:03:55 -0500 X-ClientAddr: 66.27.56.212 Received: from www3.fatcity.com (rrcs-west-66-27-56-212.biz.rr.com [66.27.56.212]) by ensim.rackshack.net (8.11.6/8.11.6) with ESMTP id h9BB3gc19496 for ; Sat, 11 Oct 2003 06:03:43 -0500 Received: (from root@localhost) by www3.fatcity.com (8.11.6/8.11.6) id h9B7jbZ13558 for oracle-l@orafaq.net; Sat, 11 Oct 2003 00:45:37 -0700 Received: by fatcity.com (05-Jun-2003/v1.0g-b73/bab) via fatcity.com id 005D2BAF; Sat, 11 Oct 2003 00:44:25 -0800 Message-ID: Date: Sat, 11 Oct 2003 00:44:25 -0800 To: Multiple recipients of list ORACLE-L X-Comment: Oracle RDBMS Community Forum X-Sender: "Nuno Souto" Sender: ml-errors@fatcity.com Reply-To: ORACLE-L@fatcity.com Errors-To: ML-ERRORS@fatcity.com From: "Nuno Souto" Subject: Re: any ever work with Use Cases to model a database? Organization: Fat City Network Services, San Diego, California X-ListServer: v1.0g, build 73; ListGuru (c) 1996-2003 Bruce A. Bergman Precedence: bulk Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit ----- 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@optusnet.com.au -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Nuno Souto INET: nsouto@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@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).