Why is this called "business logic"? Where did this term come from?

Question

I go through all kinds of WPF documentation and I feel overly confused. The term "business logic" is scattered around the world, as if everyone should know what it is.

I see what business logic is, in accordance with this question: What exactly consists of the "business logic" in the application?

But where did this term come from? Why is this called "business logic" and not, say, "core logic" or "core algorithms" or any other more universal terms? Very few of the programs that I write have anything to do with "business logic", and when I think about "business logic", I think about credit card transactions, servicing a customer database, etc. .P. In other words, things related to the share of all computer science. When I write an application for image processing, there is no “business”, no clients, no money-based transactions, nothing like that. Therefore, saying that I have a "business logic", it really bothers me, since I do not do business, I process images.

Answer 1

For the same reason that the end of the gun from which the bullets exit is called the "business end". This is where the primary action takes place.

Answer 2

If you were a professional graphic designer, then, of course, there would be a business related to the use of your image processing application - your work is your business!

Thus, “business logic” refers to pieces of code that determine how the user conducts their business (in this case, manipulating images).

Do not forget that on the same day all the software was "business software" - no one could afford the expensive equipment and skills necessary to write software for anything other than commercial purposes. If he did not make money or did not save money for business, he did not write.

Answer 3

Not sure, but I think this term should be replaced instead of domain logic.

Answer 4

You could call this the “core logic”, but I believe that the first (known) multi-level applications were actually written for insurance or banking, hence the term “business logic”. From there, the template took shape, and the naming stuck.

If the first tiered applications were a research project or something else, it would probably be called "core logic."

Answer 5

When I write an application for image processing, there is no “business”, no clients, no money-based transactions, nothing like that. Therefore, saying that I have a "business logic", it really bothers me, since I do not do business, I process images.

In addition, most of the presentation guidelines and data begin to go south, since operations such as effects and filters, which will complement the “presentation level” in the business application, are the core of yours.

Visualization, Engine, and Permanent Storage are fairly common names for layers in simulations, which I usually work with. There is no problem using names that are significant in your domain. But then I got confused in all the job postings for SAS programmers, as that means something else in the UK defense setting; if you want to talk with business people, you need to translate them.

Answer 6

The origin of the term is business software, where individual business rules have been separated in their own modules. It is simply transferred to all other software.

Answer 7

Reflecting on early computer systems, such as credit card processing, the code has two large parts, parts that perform io, conversations with back-end, tape, etc., as well as parts that execute business logic, rules such as cards , valid, limit exceeded.

Another way to think about it, these are the things that a business person would say - these are the “rules” for capture.

Answer 8

The business logic is that the part of the application where the "how" should work is determined by someone other than the development team. This is usually code that does what the client wants to do. This term usually only applies to firmware created for a non-IT team.

Answer 9

I think many times his sarcasticity, because business logic is not always logical. its done only in a certain way, because the business wants it this way - many times its not the best way. you can fight them and (if you're lucky) make them see the light or simply accept the fact that his business logic and be ready to change it when they realize that they made a mistake.

Answer 10

This is a term used mainly for business applications, and another way people know about it is the CRUD application (create, read, update, delete).

I think this means that the class contains the logic of how the business process works for a given business process.

Answer 11

I think I agree with DVK-IIRC, at that time all the information Data-> Logic-> Presentation layer was the word "enterprise" (basically: business).

Now that every damn web page has to be three-tiered, it is much more common.

You should also remember that if you have a lot of code, in addition to the business code, the amount of business code is huge and huge business (har har). Not surprisingly, some terms arose there.

Answer 12

Like you, you go to the bathroom to go about your business, your pretty graphic interface fits the logic to do your business.

(Sorry, could not resist :))