Re: Biz Modeling - let's try again


Alvin Ryder wrote:
topmind wrote:
Seems I am not the only one scratching my head on this one:

http://discuss.fogcreek.com/joelonsoftware3/default.asp?cmd=show&ixPost=76769

-T-

I'm not a fan of the term "business logic" or "business model" because
then people try to put it in one layer or place and argue about where
that one place should be and what technology is best for it: the RM,
OOP, procedural code versus whatever else.

There are *many kinds* of business rules and policies, they span all
layers of software.
-GUI rules like 'if field is blank display "field cannot be blank" in
red'
-ai type rules. Expert systems can apply complex business rules.
-db types rules. "if parent has kids, disallow deletion of parent".
-if user not logged in display "login page".

Should all of these rules by burried in the db or is procedural code
necessarily better than anything. I'd rather do my ai in Prolog or LISP
and GUI business rules in the GUI.

You make it sound mutually-exclusive. I think the problem is that RM
vendors have spent their effort cloning Oracle's features rather than
expand on other issues, like dynamic relational,
integration/coordination between app-side tables and server-side
tables, better table browsers, etc. The RM=Oracle view is a bit
limiting.

I see nothing wrong with putting a GUI model in relational tabels. Such
would be considered too slow in the past, but CPU's are catching up to
that. (Actually, FoxPro does it to a large extent, although it is
largely undocumented). Dynamic or type-free column typing would also
help with GUI's.


So I don't actually agree with much of that article, which is ironic
because I have agreed with you that the RM has some great strengths in
the domain modeling arena in this same thread ;-)

Cheers.

-T-

.

Relevant Pages

  • Re: Biz Modeling - lets try again
    ... then people try to put it in one layer or place and argue about where ... Expert systems can apply complex business rules. ... "if parent has kids, disallow deletion of parent". ... and GUI business rules in the GUI. ...
    (comp.object)
  • Re: 3 tier architecture: a lot of questions
    ... > The way from GUI to BO is more obscure to me, ... Below that is the GUI Layer, which adapts the Toolkit to the Representation ... Below the GUI Layer is the Representation Layer. ... > is not preferable to wait until the user wants to save the contract. ...
    (comp.object)
  • Re: 3270 emulator?
    ... platforms to run the same (COBOL developed) applications, ... Programs do NOT reference GUI controls, instead, they ... invoke methods of a presentation layer Class. ...
    (comp.lang.cobol)
  • Re: OO & GUI: Appliaction Facade or MVC
    ... The Logic Layer shall not use GUI Layer or GUI Toolkit identifiers. ... queries the GPS system for one update. ...
    (comp.object)
  • Re: please help on some general concepts on data c# 2.0 vs2005
    ... I normally use a Database layer, a Business layer and a GUI layer. ...
    (microsoft.public.dotnet.general)