HP3000-L Archives

January 1999, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Shawn Gordon <[log in to unmask]>
Reply To:
Shawn Gordon <[log in to unmask]>
Date:
Thu, 7 Jan 1999 06:43:40 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (53 lines)
Most CASE tool's kind of disappeared, but Visual Speedware is a good if
expensive option, and Clarion from TopSpeed looked very encouraging.  Not
so much case, but a business oriented language that generated true, fast
executables that could also be ported to the web.  I did a little work with
it and ODBC/32 and the 3000 and it worked.

shawn





Steve Fatula <[log in to unmask]> on 01/06/99 07:38:04 PM

Please respond to Steve Fatula <[log in to unmask]>

To:   [log in to unmask]
cc:    (bcc: Shawn Gordon/IS/FHM/FHS)
Subject:  CS developers - CASE tool?




For the HP3000 client server developers out there, has anyone used a pc
based CASE tool in the CS development?

If so, which products have you used? Also, can any of the CASE products
provide any direct coding benefit? i.e., can any code be generated with
the CASE tool and the data you enter? We want to be able to define such
things as business objects and the like. We will be using a object
oriented methodology. One main use will be to document the system and
objects we create, instead of trying to draw the thing in say Visio.
But, it would be nice if after entering all this we can actually use
some of it.

We are likely going to develop an application that at a high level is
structured as:

HP3000 - Data repository, also has some standard routines like pricing,
etc. coded on it, probably in XLs. This allows us to centralize the more
complex business rules, and also cut down on traffic for more
complicated data access paths. We will NOT be using Allbase.

PC - Contains the remaining business rules, user interface etc. We may
in the end resort to an app server to contain all but the user interface
instead of the client pc, but probably not initially. This will be
figured in the design from the beginning. In this future scenario, the
web browser would be the client tool used.

So, we will have objects on the Hp end, and the client end.

Any suggestions?

ATOM RSS1 RSS2