Business Logic - Revision history

User at 00:11, 28 March 2024

2024-03-28T00:11:00Z

User at 22:05, 27 March 2024

2024-03-27T22:05:58Z

User at 12:07, 1 March 2024

2024-03-01T12:07:50Z

User at 21:04, 28 February 2024

2024-02-28T21:04:30Z

User at 21:01, 6 December 2022

2022-12-06T21:01:04Z

User at 16:37, 1 November 2022

2022-11-01T16:37:12Z

User at 15:57, 15 July 2021

2021-07-15T15:57:55Z

User at 19:40, 8 July 2021

2021-07-08T19:40:36Z

User at 14:00, 11 June 2021

2021-06-11T14:00:14Z

User at 15:55, 19 February 2021

2021-02-19T15:55:07Z

@@ Line 55: / Line 55: @@
 *[[Database Management System (DBMS)]]: Discussing software that provides an interface to database users for managing data, where business logic determines how data is queried, updated, and maintained.
 *[[Object Oriented Programming (OOP)]]: Explaining the programming paradigm based on the concept of "objects", which can encapsulate data and business logic in a modular and reusable manner.
-*Microservices Architecture: Covering an architectural style that structures an application as a collection of loosely coupled services, which can independently implement specific business logic functionalities.
+*[[Microservices Architecture]]: Covering an architectural style that structures an application as a collection of loosely coupled services, which can independently implement specific business logic functionalities.
 *[[Service Oriented Architecture (SOA)]]: Discussing an architectural pattern in software design where services are provided to other components via a communication protocol over a network, with business logic often encapsulated within these services.
 *Rule Engine: Explaining software systems that execute one or more business rules in a runtime production environment, enabling dynamic decision-making based on business logic.

@@ Line 1: / Line 1: @@
-'''[[Business]] Logic''' refers to the underlying [[Process|processes]] within a program that carry out the operations between a company’s [[Server|servers]] and the [[User Interface|user interface]] with which that company's customers interact. Business logic is more properly thought of as the code that defines the [[Database Schema|database schema]] and the processes to be run, and contains the specific calculations or commands needed to carry out those processes. The user interface is what the [[customer]] sees and interacts with, while the business logic works behind the [[User Interface|UI]] to carry out actions based on the inputted values.<ref>What is Business Logic? [https://www.techopedia.com/definition/27382/business-logic Techopedia]</ref>
+== What is Business Logic? ==
-'''Business Logic vs Business Rules'''<ref>Business Logic vs Business Rules [http://www.ben-morris.com/what-do-we-actually-mean-when-we-say-business-logic/ ben-morris.com]</ref><br />
+== Components of Business Logic ==
 Business logic is often mistaken for something that encapsulates the [[Business Rule|business rules]] implemented in a [[system]]. There is an important difference between the two. Business rules are a formal expression of business [[policy]], while business logic determines how this policy is implemented as a [[process]]. For example, the [[application]] of VAT on invoices is a business rule but the calculations involved in applying it are implemented as business logic. The catch is that the separation between business logic and other parts of the system is not necessarily that clear. Many business rules need to be implemented across more than one tier. For example, a business rule that dictates that negative figures should always be presented on financial reports affects both [[Data Processing|data processing]] and report writing, i.e. presentation and business logic. This is one of the drawbacks of [[Layered Architecture|tiered or layered architectures]] that seek to isolate business logic into a separate tier. It can be difficult to meaningfully segregate functionality into a self-contained tier depending on the type of processing that is being carried out. Over the long term this “business logic” often leaks across tier boundaries so the implementation of business rules becomes scattered across a system. This gives rise to anti-patterns such as “shotgun surgery” where any change in a business rule requires numerous changes in different parts of the system.
 == See Also ==
-<div style="column-count:2;-moz-column-count:3;-webkit-column-count:3">
+Business Logic refers to the rules that define or constrain some aspect of business behavior. Embedded within the software that operates business processes, it dictates how data can be created, stored, and changed. Business logic is the backbone of an application, controlling the sequence of operations, the criteria under which those operations execute, and the execution's overall outcome in response to specific business requirements or conditions. This can include calculations, data processing instructions, and any other automated decision-making processes. By encapsulating the core functionalities that process inputs and produce outputs based on business rules, business logic ensures that business operations are efficiently and correctly executed.
-*[[Software]]
-*[[Software Architecture]]
+*[[Application Program Interface (API)]]: Discussing interfaces that allow different software applications to communicate with each other, often used to access business logic from external systems or services.
-*[[Application Architecture]]
+*[[Software Development Life Cycle (SDLC)]]: Covering the process of planning, creating, testing, and deploying an information system, within which the development and modification of business logic play a crucial role.
-*[[Enterprise Architecture]]
+*[[Enterprise Resource Planning (ERP)]]: Explaining integrated management software systems used to manage day-to-day business activities, where business logic is key to automating and streamlining business processes.
-*[[Application]]
+*[[Customer Relationship Management (CRM)]]: Discussing systems that help manage a company’s interactions with current and potential customers, driven by business logic that automates and optimizes customer engagements.
-</div>
+*[[Business Process Management (BPM)]]: Covering the discipline of improving organizational efficiency and effectiveness through the management of business processes, which relies on business logic to enforce process rules and workflows.
-===References===
+== References ==
 <references />

← Older revision		Revision as of 12:07, 1 March 2024
Line 1:		Line 1:
−	'''Business Logic''' refers to the underlying [[Process\|processes]] within a program that carry out the operations between a company’s [[Server\|servers]] and the [[User Interface\|user interface]] with which that company's customers interact. Business logic is more properly thought of as the code that defines the [[Database Schema\|database schema]] and the processes to be run, and contains the specific calculations or commands needed to carry out those processes. The user interface is what the [[customer]] sees and interacts with, while the business logic works behind the [[User Interface\|UI]] to carry out actions based on the inputted values.<ref>What is Business Logic? [https://www.techopedia.com/definition/27382/business-logic Techopedia]</ref>	+	'''[[Business]] Logic''' refers to the underlying [[Process\|processes]] within a program that carry out the operations between a company’s [[Server\|servers]] and the [[User Interface\|user interface]] with which that company's customers interact. Business logic is more properly thought of as the code that defines the [[Database Schema\|database schema]] and the processes to be run, and contains the specific calculations or commands needed to carry out those processes. The user interface is what the [[customer]] sees and interacts with, while the business logic works behind the [[User Interface\|UI]] to carry out actions based on the inputted values.<ref>What is Business Logic? [https://www.techopedia.com/definition/27382/business-logic Techopedia]</ref>

← Older revision		Revision as of 21:04, 28 February 2024
Line 1:		Line 1:
−	'''[[Business]] Logic''' refers to the underlying [[Process\|processes]] within a program that carry out the operations between a company’s [[Server\|servers]] and the [[User Interface\|user interface]] with which that company's customers interact. Business logic is more properly thought of as the code that defines the [[Database Schema\|database schema]] and the processes to be run, and contains the specific calculations or commands needed to carry out those processes. The user interface is what the [[customer]] sees and interacts with, while the business logic works behind the [[User Interface\|UI]] to carry out actions based on the inputted values.<ref>What is Business Logic? [https://www.techopedia.com/definition/27382/business-logic Techopedia]</ref>	+	'''Business Logic''' refers to the underlying [[Process\|processes]] within a program that carry out the operations between a company’s [[Server\|servers]] and the [[User Interface\|user interface]] with which that company's customers interact. Business logic is more properly thought of as the code that defines the [[Database Schema\|database schema]] and the processes to be run, and contains the specific calculations or commands needed to carry out those processes. The user interface is what the [[customer]] sees and interacts with, while the business logic works behind the [[User Interface\|UI]] to carry out actions based on the inputted values.<ref>What is Business Logic? [https://www.techopedia.com/definition/27382/business-logic Techopedia]</ref>

← Older revision		Revision as of 21:01, 6 December 2022
Line 1:		Line 1:
−	'''[[Business]] Logic''' refers to the underlying [[Process\|processes]] within a ~~[[Computer Program\|~~program]] that carry out the operations between a company’s [[Server\|servers]] and the [[User Interface\|user interface]] with which that company's customers interact. Business logic is more properly thought of as the code that defines the [[Database Schema\|database schema]] and the processes to be run, and contains the specific calculations or commands needed to carry out those processes. The user interface is what the [[customer]] sees and interacts with, while the business logic works behind the [[User Interface\|UI]] to carry out actions based on the inputted values.<ref>What is Business Logic? [https://www.techopedia.com/definition/27382/business-logic Techopedia]</ref>	+	'''[[Business]] Logic''' refers to the underlying [[Process\|processes]] within a program that carry out the operations between a company’s [[Server\|servers]] and the [[User Interface\|user interface]] with which that company's customers interact. Business logic is more properly thought of as the code that defines the [[Database Schema\|database schema]] and the processes to be run, and contains the specific calculations or commands needed to carry out those processes. The user interface is what the [[customer]] sees and interacts with, while the business logic works behind the [[User Interface\|UI]] to carry out actions based on the inputted values.<ref>What is Business Logic? [https://www.techopedia.com/definition/27382/business-logic Techopedia]</ref>

← Older revision		Revision as of 14:00, 11 June 2021
Line 4:		Line 4:
	'''Business Logic vs Business Rules'''<ref>Business Logic vs Business Rules [http://www.ben-morris.com/what-do-we-actually-mean-when-we-say-business-logic/ ben-morris.com]</ref><br />		'''Business Logic vs Business Rules'''<ref>Business Logic vs Business Rules [http://www.ben-morris.com/what-do-we-actually-mean-when-we-say-business-logic/ ben-morris.com]</ref><br />
	Business logic is often mistaken for something that encapsulates the [[Business Rule\|business rules]] implemented in a [[system]]. There is an important difference between the two. Business rules are a formal expression of business [[policy]], while business logic determines how this policy is implemented as a [[process]]. For example, the [[application]] of VAT on invoices is a business rule but the calculations involved in applying it are implemented as business logic. The catch is that the separation between business logic and other parts of the system is not necessarily that clear. Many business rules need to be implemented across more than one tier. For example, a business rule that dictates that negative figures should always be presented on financial reports affects both [[Data Processing\|data processing]] and report writing, i.e. presentation and business logic. This is one of the drawbacks of [[Layered Architecture\|tiered or layered architectures]] that seek to isolate business logic into a separate tier. It can be difficult to meaningfully segregate functionality into a self-contained tier depending on the type of processing that is being carried out. Over the long term this “business logic” often leaks across tier boundaries so the implementation of business rules becomes scattered across a system. This gives rise to anti-patterns such as “shotgun surgery” where any change in a business rule requires numerous changes in different parts of the system.		Business logic is often mistaken for something that encapsulates the [[Business Rule\|business rules]] implemented in a [[system]]. There is an important difference between the two. Business rules are a formal expression of business [[policy]], while business logic determines how this policy is implemented as a [[process]]. For example, the [[application]] of VAT on invoices is a business rule but the calculations involved in applying it are implemented as business logic. The catch is that the separation between business logic and other parts of the system is not necessarily that clear. Many business rules need to be implemented across more than one tier. For example, a business rule that dictates that negative figures should always be presented on financial reports affects both [[Data Processing\|data processing]] and report writing, i.e. presentation and business logic. This is one of the drawbacks of [[Layered Architecture\|tiered or layered architectures]] that seek to isolate business logic into a separate tier. It can be difficult to meaningfully segregate functionality into a self-contained tier depending on the type of processing that is being carried out. Over the long term this “business logic” often leaks across tier boundaries so the implementation of business rules becomes scattered across a system. This gives rise to anti-patterns such as “shotgun surgery” where any change in a business rule requires numerous changes in different parts of the system.
		+
		+
		+
		+	== See Also ==
		+	<div style="column-count:2;-moz-column-count:3;-webkit-column-count:3">
		+	[[Business]]<br />
		+	[[Business-to-Business (B2B)]]<br />
		+	[[Business Application]]<br />
		+	[[Business-Driven Development (BDD)]]<br />
		+	[[Business-to-Business Gateway]]<br />
		+	[[Business-to-Consumer (B2C)]]<br />
		+	[[Business Accelerator]]<br />
		+	[[Business Activity Monitoring (BAM)]]<br />
		+	[[Business Analysis]]<br />
		+	[[Business Analytics]]<br />
		+	[[Business Application]]<br />
		+	[[Business Application Programming Interface (BAPI)]]<br />
		+	[[Business Architecture]]<br />
		+	[[Business Asset]]<br />
		+	[[Business Capability]]<br />
		+	[[Business Capability Modeling]]<br />
		+	[[Business Ethics]]<br />
		+	[[Business Case]]<br />
		+	[[Business Centric Methodology (BCM)]]<br />
		+	[[Business Continuity Management (BCM)]]<br />
		+	[[Business Continuity Plan (BCP)]]<br />
		+	[[Business Continuity Planning (BCP)]]<br />
		+	[[Business Cycle]]<br />
		+	[[Business Diversification]]<br />
		+	[[Business Driven Technology]]<br />
		+	[[Business Drivers]]<br />
		+	[[Business Ecosystem]]<br />
		+	[[Business Environment and Internal Control Factors (BEICF)]]<br />
		+	[[Business Excellence]]<br />
		+	[[Business Expansion]]<br />
		+	[[Business Function]]<br />
		+	[[Business Function Model]]<br />
		+	[[Business IT Alignment]]<br />
		+	[[Business Impact Analysis (BIA)]]<br />
		+	[[Business Incubator]]<br />
		+	[[Business Insurance]]<br />
		+	[[Business Integration]]<br />
		+	[[Business Intelligence]]<br />
		+	[[Business Interruption Insurance]]<br />
		+	[[Business Life Cycle]]<br />
		+	[[Business Logic]]<br />
		+	[[Business Management System (BMS)]]<br />
		+	[[Business Model Innovation (BMI)]]<br />
		+	[[Business Model for Information Security (BMIS)]]<br />
		+	[[Business Motivation Model (BMM)]]<br />
		+	[[Business Objects]]<br />
		+	[[Business Operations]]<br />
		+	[[Business Oriented Architecture (BOA)]]<br />
		+	[[Business Mission]]<br />
		+	[[Business Vision]]<br />
		+	[[Business Model]]<br />
		+	[[Business Goals]]<br />
		+	[[Business Objective]]<br />
		+	[[Corporate Structure]]<br />
		+	[[Corporate Social Responsibility (CSR)]]<br />
		+	[[Chief Executive Officer (CEO)]]<br />
		+	[[IT Strategy (Information Technology Strategy)]]<br />
		+	[[IT Governance]]<br />
		+	[[Enterprise Architecture]]<br />
		+	[[IT Sourcing (Information Technology Sourcing)]]<br />
		+	[[IT Operations (Information Technology Operations)]]<br />
		+	</div>