James Britt
11/1/2004 3:43:00 AM
Patrick May wrote:
> It is an odd distinction. Why is the in-memory code object, transient
> and fleeting, the "Business Object", while the permanent record is
> relegated to the invisible role of "plumbing"?
Well, in this analogy, the plumbing would be the database and the
library code needed for database access. The data themselves, though,
are not plumbing, and are arguably more important than any of the code,
business or otherwise.
And, assuming you have your business code on disk, it shouldn't be any
more transient and fleeting than any other code.
>
> I prefer to call them BO objects, myself. Because I think they are a
> smell. There are points of interface that are important to the
> business. The place where customers buy things. The place where
> inventory is recorded. The interfaces used by non-programmers to
> monitor these things. All the stuff in between -- the BO domain -- to
> me, all that is just plumbing between the places where the business
> makes money. Like all other code smells, this one should be managed in
> a discrete fashion.
Well, call them what you like. As a practical matter, though, the term
'business object' is quite common, whatever one's personal views on the
philosophy behind it. But I would suggest that in the common parlance
it is in the business objects where money-making code resides. Well,
unless you sell the plumbing.
(I'm also getting the impression that you believe that code that makes
money for a business smells, or is somehow distasteful, but I may be
misreading your comments.)
James