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

Viewed 4571

I'm going through all sorts of WPF documentation, and I'm feeling unnecessarily confused. The term 'business logic' is scattered throughout it, as if everyone should know what it is.

I can see what business logic is, according to this question here: What exactly consists of 'Business Logic' in an application?

But where did the term come from? Why is it called 'business logic' and not, say, 'core logic' or 'main algorithms' or any other more generic terms? Very few of the programs I write have anything to do with 'business logic', and when I think of 'business logic' I think of things handling credit card transactions, customer database maintenance, and the like. In other words, things that relate to a fraction of the entirety of computer science. When I write an imaging application, there is no 'business' involved, no customers, no money-based transactions, nothing of the sort. So saying that I have 'business logic' really confuses me, since I'm not conducting business, I'm processing images.

13 Answers

I think nmr is quite correct. I'm teaching my HCI software engineering course, and I need to encourage students to stop thinking of "Business Logic" and think more about MVC.

Quite often, their previous professors would tell them that, "Underneath the HCI is the BIDness Logic"

Can we please LOSE the business logic? Since software rarely has NO user interface, we can say, for the rest of the software, there is the View, the user Control, and the Model.

And there will be message passing between these three entities. Which are, by the way, "output", "input"/"state". Just as Turing (and Church) had taught us.

So... let's lose 'the bidness logic'

Related