This article was nominated for deletion on 31 July 2006. The result of the discussion was keep. |
This article is rated C-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||
|
The contents of the Business logic layer page were merged into Business logic on April 2013. For the contribution history and old versions of the redirected page, please see its history; for the discussion at that location, see its talk page. |
The contents of the Business logic abuse page were merged into Business logic on April 2013. For the contribution history and old versions of the redirected page, please see its history; for the discussion at that location, see its talk page. |
Technically speaking, not so much I think. The same goes for Web services. It is more of a conceptual thing really. It seems to me that daemons are more likely to be a feature of an operating system than a stand-alone software application though.
Daemons are processes run for any purpose, including things such as system mainenance. "Business logic" is supposed to be related to an application at least. (I hope.) Nixdorf 10:29, 1 Mar 2004 (UTC)' ==
I'm curious when this term first started seeing widespread use. To me it feels like something recent... I don't recall hearing it 10 years ago.
Personally I have my doubts, and the article as it stands does little to allay them. A citation or two would put old cycnics like me in their place, but if no clear references are found, I think that a vote for deletion would be in order. In my (not inconsiderable) database admin career, I have only heard this phrase muttered in the wooliest of terms by people who, to put it unkindly, were speaking our of their arses. Not that this in itself is a reason to can 'business logic', it is merely an observation. So: sensible definition or VFD--Fergie 12:44, 1 June 2006 (UTC)
"The core of any application is the business functionality it provides" I am sorry but this quote is just plain incorrect. There are many examples of applications with no affiliation to business needs. grep, cat, many if not most open source applications. Business logic only has meaning in a business or enterprise context. Even then whether it is the "core" of an application is debatable.
My criticisms below referred to the version circa July 2006 [1]. Neale Monks 18:25, 26 October 2006 (UTC)
Sorry, this article reads to me like a pitch from a management consultant. It doesn't explain anything at all. I'm a smart guy with a science degree and a PhD, and I have _no idea_ what it's about.
To actually make sense here, the article needs to explain whay business logic is, give actual examples, define new terms, and so on. For example, how can "logspecific" be used without either linking to another article defining it, or actually defining it within this article? Ditto "business layers", "business processes", "long running transactions", etc.
Cheers, Neale Neale Monks 10:03, 18 July 2006 (UTC)
Please do not delete this page. This concept has been a critical unifying element of modern business software which has been a major contributor to the recent explosion in productivity in the United States.
Here is my quick attempt a a brief explanation. With more time perhaps I can come up with a draft of this page in an alternative form:
Business logic is a concrete representation of abstract business rules that is usually used in conjunction with a database of business transactions. For example, retail transactions may include sales taxes, per customer purchase limits, a small credit for not needing a bag, and so on. By keeping the business logic apart from the storage of the data it is possible to use the same business logic with different data or with different applications, for example summarizing periodic sales performance or calculating yearly taxes by using the same data that came from the cash register program and which is checked for validity using the same logic. Encoding business logic is a strategy used by enterprises with complex data or transactions to minimize the cost of automating their operations. Without using this strategy the cost of developing software applications for automating business processes may become prohibitive. -- M0llusk 05:40, 8 August 2006 (UTC)
Mainly from the vote for deletion page. People who have expressed an opinion think that Business logic can mean one or more of the following:
1)A mid-level abstraction layer in a multi-tier architecture
2)The logic of business processes (any type of logic, any type of business) --Fergie 09:26, 17 August 2006 (UTC) 3)Nothing. Yet can be used as filler in situations where the speaker wishes to use an impressive sounding software-engineering term (such as promotional material for expensive software). In other words the term is notable precisely because it is vague meaningless software terminology.
4)Various confused definitions containing combinations of random strings of buzzwords such as 'business rules', 'enterprise' and 'business objects' a la point 3 above.
Are there any more meanings that I have missed? If so- please note them here.--Fergie 07:44, 8 August 2006 (UTC)
--24.4.211.92 09:05, 9 August 2006 (UTC)
This article is not polished. However, the term "Business logic" is used too frequently to ignore the need for proper definition. A standard understanding should be developed as to what exactly the term "Buisness logic" means. —The preceding unsigned comment was added by 72.25.168.234 (talk) 17:17, 10 April 2007 (UTC).
I am currently reading a book on the cherryPy python-based HTTP framework. The author mentions "business logic." I've heard this time many, many times before, and I still have no idea what it means. I fudge understanding every time. I'm not a businessman, and my work doesn't involve business, but somehow all of the technologies I use are predicated on this concept of business logic. It seems to me that when they talk about business logic, what they really mean is something like "the methods by which the application performs its intended function". Isn't this just what we've been calling "features" all this time? Or possibly "use cases?" I hope someone explains everything in this article - it certainly won't be me. I don't have a clue. --[[User:my computer said love][my computer said love]] —Preceding unsigned comment added by My computer said love (talk • contribs) 14:51, 20 March 2009 (UTC)
"Business Logic is Business as Intelligence is for CIA". Or you could say, the "business" name is just a name, you can call business logic = processor or business logic = "according some data or input i will do something".
--200.83.2.4 (talk) 20:37, 6 July 2009 (UTC)--200.83.2.4 (talk) 20:37, 6 July 2009 (UTC)
I am tempted to clear this entry out and start over. An earlier entry mentions that it is a vague term and there are many interpretations of its meaning. That was deleted but I think it is important. Based on the revision history of this page, plus the numerous articles and books that mention the term I think we can say that business logic is the code that handles what ever you define the business of your application to be.
If you determine that the business of your application is to handle information exchange between a database and a user interface (as the current author suggests) then the "business logic" would be the code that makes decisions regarding those operations. However, if for example you are writing an application that manages a DVD store, you might determine that the business of your application is the management of DVD rentals and purchases. With this line of thinking, the code that makes decisions and has operations related to the management of a DVD store would be considered the business logic code.
The current definition suggests that only an application that has a database could then have business logic which is not valid. A service written to monitor a file system directory and manage the files based on various events would probably not require a database. However, it would require logic related to the business of managing files.
--Joseph A. Reddy (talk) 15:52, 17 April 2009 (UTC)
Business logic is a non-technical term generally used to describe the functional algorithms that handle information exchange between a database and a user interface. It is distinguished from input/output data validation and product logic.
How lame definition. —Preceding unsigned comment added by 200.83.2.4 (talk) 20:27, 6 July 2009 (UTC)
--200.83.2.4 (talk) 20:33, 6 July 2009 (UTC)--200.83.2.4 (talk) 20:33, 6 July 2009 (UTC)
I suggest the possibility that the fragment "the functional algorithms that handle information exchange between a database and a user interface" is very misleading. I have almost no software background, but based on other material I have read I thought that, most fundamentally, business logic is the logic that implements the functionality of interest. It would, on this view, therefore be constituted by a set of "processes/operations" and "objects" that express domain concepts and domain behaviours. The fragment (extracted from the very first sentence of the article) seems to suggest that business logic is focused on information exchange in particular. Is that correct? I doubt it. Again, I have almost no background in this area, but I suspect the words in this first sentence may not have been carefully chosen. I stand to be corrected, of course.Expos4ever (talk) 22:39, 11 February 2013 (UTC)
Certainly in my work as a professional software engineer, I have always understood "business logic" as a pretty concrete, non-buzzword term. I rewrote the intro and significant parts of the rest of the article to more clearly explain what this term means and how to spot it. Hopefully this addresses the complaints and confusion expressed above. -- Beland (talk) 21:07, 15 July 2013 (UTC)
How has this not been deleted as a waste of time or some sad attempt to drive people via keyword searches to freshly minted experts in this "term" (see, non-buzzword term). I'm guessing it leads to certain resume's or seminars. It's also just so painfully, painfully bad. It's like making a seminar about how to purchase a Business Building. Or what it means when people exchange dollar bills for a good or service: The Business Money Handover. Make this stop.. — Preceding unsigned comment added by 208.107.23.136 (talk) 02:42, 7 August 2014 (UTC)
The "Business logic and tiers/layers" section have a notice "This section needs to be verified." What verification are we looking for? The section seems fine to me. Suggest we remove the notice. Svesterli (talk) 09:53, 26 October 2016 (UTC)
Hello fellow Wikipedians,
I have just modified one external link on Business logic. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template ((source check))
(last update: 18 January 2022).
Cheers.—InternetArchiveBot (Report bug) 23:08, 27 July 2017 (UTC)