Re: Anyone using Oracle*Case or TopCase?

From: Gert de Boer <deboer_at_wsl34>
Date: Thu, 6 Jan 1994 07:30:44 GMT
Message-ID: <CJ767A.64q_at_bernina.ethz.ch>

Carsten Kristensen (ckr_at_ocsbrg.no) wrote:
: Repost: Since we're looking at Oracle*Case versus TopCase right now,
: any experiences or views on either of these two would be very much
: appreciated.
 

: Thanks!
: --
: =================================================================
: | Carsten Kristensen | E-mail: ckr_at_ocsbrg.no |
: | Offshore Computer Services AS | Tel : +47 55 99 88 70 |
: | Bergen, Norway | Fax : +47 55 99 88 84 |
: =================================================================

I happen to know them both. TopCase even very good. Today I am working with OracleCase (it may not be the newes version), and I find it terrible.

1. The (Forms) interface of Oracle isn't very good. Often 'unhandled exceptions'. There are also some mistakes in the logic of the OracleCase screens which you, as an application builder, would never make.
2. There are no Forms for all important repository tables in OracleCase. E.g. 'show me all the defined columns with name like %dis%: impossible.
3. No Data-Driven-Detailmenu: in TopCase it is possible to see child records of a parent record in one key stroke. When you also use lookup-forms in TopCase you can walk through your entire application. That holds for the TopCase interface and the applications that TopCase generates.
4. The OracleCase Repository is one very big table for all objects: the repositories tables turn out to be views on this gigantic table. The meta structure of OracleCase is difficult to understand.
5. Strange identifications of database objects in OracleCase. E.g. references between tables are defined by 'from-table-name' and 'role-name'. When you have some relations with rolename 'have' (very common), OracleCase turns the names of the key constraints in 'table has1', 'table has2' etc. The table at the other end of the reference does not seem to be important.
6. The ER designer of OracleCase is not very well integrated with the repository. Attribute names are just text objects. When you use TopCase together with e.g. Pro*Niam (also of Cosima/Comtecno), you get nearly all the results of you analysis in the TopRepository.
7. TopCase has a one to one relation between contents of the repository and the DDL statements it generates. For OracleCase it seems to depend on the history of your several generations.
8. OracleCase is very poor structured: it does not lead you the natural way through your sytem designing.
9. The other way round: TopCase does not know of functions. However, it has many textfields to comment on the use of attributes.
10. TopCase's Forms are not so beautiful as those from OracleCase: but I never got a Form (in OracleCase and TopCase) that could be used without screenpainting.
11. TopCase also exists in a X and MS-Windows version, working with the same repository. In the Windows version you have 'instant-generation': there is no need for generating anymore. TopCase reads the repository, and in a few seconds starts the Windows interface you wanted to.
12. TopCase windows can also be used with other RDBMS's.
13. TopCase is in fact a lowercase tool: it can be used in combination with many uppercase tools. Just read the information from your uppercase tool, and fill the TopRepository with it.
14. With TopCase it is easier to go back, and correct mistakes or implement changes. Application are easier to maintain.

If you have some other particular questions, just ask, email or posting in this group.

Gert

---

Gert de Boer
WSL
Zurcherstrasse 111
8903 Birmensdorf
Switzerland
phone: +4117392577
fax: +4117392215
e-mail:deboer_at_wsl.ethz.ch

---

Received on Thu Jan 06 1994 - 08:30:44 CET