Can someone point me to a source for starting to understand business logic?
Or is it just a buzzword?

My best guess is that it's implementing common sense rules and business
policy in your database model. Such as 'goods cannot ship before they pass
QA' or 'arrival date must not preceed ship date'. Is this basically correct?

Martha Stewart called it a Good Thing when "Steve Leferve" <lefevre.10 (AT) osu (DOT) edu> wrote:
No, it's not quite about "common sense;" it is about defining
predicates to enforce the policies that your organization uses.

- Some may involve the domains in which values must fall

- A regular expression might be a suitable "rule" to enforce that
invoice IDs must conform to a particular format;

- A stored function may be useful for requiring that credit card
numbers conform to checksum requirements.

- Similarly, some countries (such as Canada) have checksums in their
ID numbers.

- Postal codes often have formatting rules.

- Others may involve relationships between data.

- Country codes must properly reference the members of the official
ISO-3166 "list of countries."

- Certain documents must be in place before a sales request can be
processed.

- Additional documents may need to be in place before large sales or
sales of restricted products may be processed.

The more that you can document these and present them as enforceable
logic in the database, the more likely that you can keep your
databases from turning into crud...
--
let name="cbbrowne" and tld="cbbrowne.com" in String.concat "@" [name;tld];;
http://www.ntlug.org/~cbbrowne/sap.html
Rules of the Evil Overlord #86. "I will make sure that my doomsday
device is up to code and properly grounded."
<http://www.eviloverlord.com/>

"Steve Leferve" <lefevre.10 (AT) osu (DOT) edu> wrote


Yes, you are basically correct. One creates a formal model of the data with
which one can describe the above rules in a formal manner. A dbms that
understands the formalism used can then enforce all of the rules. Report
generation and application generation tools that understand the formalism
can automate significant amounts of development work. etc.

Perhaps, this link may help. You may need to register to access it though.
http://www.brcommunity.com/b170.php

--
Anith

"Christopher Browne" <cbbrowne (AT) acm (DOT) org> schrieb im Newsbeitrag
news:c1jpje$1jfbp8$1 (AT) ID-125932 (DOT) news.uni-berlin.de...
That's a quite narrow definition. IMHO BL is that part of an application
that directly deals with customer's requirements and processes, e.g.
implementation of bank account manipulations such as withdrawal and
deposit. The "rest" of the application deals with technical issues
(managing persistence, load balancing, startup shutdown...) that are not
driven by business requirements but by technical requirements (i.e.
required architecture, performance, accessibility etc.)

Kind regards

robert