Say that you are writing a system that solves a business problem for a client.
The sum of all your code — is the application logic or system architecture — is basically the complete system that you are building.
Business logic is a subset of code that models and manages actual business processes. "What happens when an order for product X is placed? How is the cost of product Y calculated?" I.e. bits of code where you probably need some input from an expert / expert / project participant.
Ideally, business logic is divided into its own level or level ( see the Wikipedia article on N-level architecture ). The rest of the code can often be simply thought of as an infrastructure that will help execute this business logic (database wrapper, helper functions, service facades, external integration, graphical interface, etc.).
thomanil Sep 22 '09 at 6:29 2009-09-22 06:29
source share