Re: chooses not to generate code at all
- From: "H. S. Lahman" <h.lahman@xxxxxxxxxxx>
- Date: Wed, 31 Aug 2005 13:19:16 GMT
Responding to JXStern...
Fine, they're an instantiation of the data model, but they still carry business logic, perhaps ALL of it.
How? They are merely the result of applying the business logic in applications. But the business logic cannot be deduced from the data in general.
I repeat, the presumption behind the idea of relational databases is that all there is in the universe is data, following the behaviorist, logical positivist, verificationist philosophies of the twentieth century. They might simply claim that there is no such thing as business logic, at least nothing that is not redundant to the data. To a first approximation, I guess I believe in that.
That leads to an existential chicken-or-egg conundrum relative to software: How did the data come to be? If that presumption were true there would be no need for software applications.
My point in this anecdote is that for any pile of data I can come up with rules for generating _that particular set of values_ that have nothing to do with the semantics of the data. More important, I can come usually up with multiple formulas (albeit tediously for larger piles of data). Thus there is a *:1 relationship between the "business logic" and the DB data. So while the DB data may reflect the business logic, it does not model it because determining the business logic from the data is inherently ambiguous.
That's a very sophisticated argument, but it buys you nothing because by the same logic, you can never prove that any rules you supply, however you got them, is the correct set. If you say you can claim some kind of privilege for your rules because of blah blah blah, well, anyone can claim something else because of yada yada yada. And me, I'll claim the only way to even begin to decide between rulesets is to appeal to the data. Which is where we came in.
The correctness of the business logic doesn't matter. (In fact, correctness varies with time, which is a major reason why we need software between the customer and the data.) All that matters is that the customer believes it is correct and the software reproduces it faithfully when the software is implemented. IOW, the customer is always right.
************* There is nothing wrong with me that could not be cured by a capful of Drano.
H. S. Lahman hsl@xxxxxxxxxxxxxxxxx Pathfinder Solutions -- Put MDA to Work http://www.pathfindermda.com blog: http://pathfinderpeople.blogs.com/hslahman (888)OOA-PATH
.
- References:
- Re: chooses not to generate code at all
- From: JXStern
- Re: chooses not to generate code at all
- From: H. S. Lahman
- Re: chooses not to generate code at all
- From: JXStern
- Re: chooses not to generate code at all
- From: H. S. Lahman
- Re: chooses not to generate code at all
- From: JXStern
- Re: chooses not to generate code at all
- From: H. S. Lahman
- Re: chooses not to generate code at all
- From: Daniel Parker
- Re: chooses not to generate code at all
- From: H. S. Lahman
- Re: chooses not to generate code at all
- From: JXStern
- Re: chooses not to generate code at all
- From: H. S. Lahman
- Re: chooses not to generate code at all
- From: JXStern
- Re: chooses not to generate code at all
- From: H. S. Lahman
- Re: chooses not to generate code at all
- From: JXStern
- Re: chooses not to generate code at all
- Prev by Date: Re: Object, thing, creature, and methods...???
- Next by Date: Re: XP and Pair Programming
- Previous by thread: Re: chooses not to generate code at all
- Next by thread: Re: chooses not to generate code at all
- Index(es):
Relevant Pages
|
Loading