Re: Oracle Case Dictionary

jheise_at_ic1d.harris.com (Jan Heise) writes:

>We are looking for anyone with experience using Oracle Case Dictionary 5.0.
>Preferably in a UNIX environment.
>Please post response here or directly to awhite_at_ic1d.harris.com
>Thanks,
>Jan Heise,

   I've been working with Oracle CASE for about 6 months now.    Platforms have been OS/2 stand alone, a sunOS worksatation and    lately, a SunOS sparcserver. The product seems quite stable    and we've had no problems operationally.

   As far as the product is concerned, people generally    love it (like me) or hate it. It is expensive for the comercial    user, and most people are hesitant to take the plunge. What makes    this even togher is that Oracle want's you to take an $x,000    intro course just learn about what CASE can do. I can't figure    out whether the sales reps are just not knowledgable in CASE or    if this is a scheme to make money. Either way, I think it    is hindering the adoption of the product in many companies.

   The reaction I'm getting lately is: "CASE can do THAT!? All I    know is that it's expensive . . ."

   I've been using CASE to model a full blown manufacturing    application and so far have generated several sub-application    with about 60 - 70% complete code generation. We are adding    quite a bit of additional custom code and the sub-applications    we are working on are the most complex in terms of enforcing    business rules. I have a feeling when we move to some of the    more "mundane" order entry-type areas we may see up to 80%    complete code generation.

   The CASE dictionary itself has a few main concepts to master    and then is quite straightforward to use. For an    application, you must specify Entities with their attributes,    the realtionships between entities and the collections of    attributes which will become the unique Id's for each entity.    You can specify domains on attributes for allowable values or    value ranges and use these throughout for consistency.    

   The second big portion is the functional design where you    define the functions of the business is a hierarchical    form. Each function may then make use of certain entities    and attributes forming a cross reference table. This is what is    basically used when generating forms and reports.

   There's tons more to it. Please feel free to ask some specific    questions.

Rich Holowczak
Rutgers University
holowcza_at_andromeda.rutgers.edu Received on Fri Nov 19 1993 - 15:44:41 CET