locked
wat is business logic RRS feed

All replies

  •  

    It acts as an interface between User Interface and database !! In some projects programs are separated into a 3 TIER architecture  with business logic referring to the mid tier. !!

     

     

    CLIENT             --->               B/Logic                 --->           Server [dB]

    Sunday, September 30, 2007 4:36 PM
  •  

    Business logic is a non-technical term generally used to describe the functional algorithms which handle information exchange between a database and a user interface. There exists no definition of business logic in any programming language specification or API, nor in any academic research. However, usage of the term persists in trade publications where several individuals have tried to informally advance a meaning that could be standardised. Mostly the term is applied to web application development where programs are separated into a 3-tier architecture with business logic referring to the mid tier. It should be noted that business logic is a poorly-defined term which is used in several different ways by several different groups of people.

     

    Scope of business logic

    Business logic:

        * models real life business objects (such as accounts, loans, itineraries, and inventories);
        * prescribes how business objects interact with one another; and
        * enforces the routes and the methods by which business objects are accessed and updated.

    Business logic comprises:[1]

        * business rules that express business policy (such as channels, location, logistics, prices, and products); and
        * workflows that are the ordered tasks of passing documents or data from one participant (a person or a software system) to another.

    Location of business logic
    Business logic in theory occupies the middle tier of a 3-tier architecture.
    Business logic in theory occupies the middle tier of a 3-tier architecture.

    In single-tier applications, business logic, presentation logic, and CRUD are often fused, with each having intimate knowledge of, or being strongly coupled to, the others. This is seen as problematic, since changes to one result in changes to both of the others, requiring retesting and revalidation of the entire system for a single change. The interweaving also limits the extent to which the CRUD and the business logic can be reused.[2]

    In a multitier architecture, business logic is a separate module. In the common 3-tier architecture, the business logic in theory occupies the middle tier, the business-services tier or business layer. In practice, the business logic is often interwoven in the other two tiers (the user services tier and the database services tier), such as by encoding business logic in stored procedures and in decisions about input validation and display formatting. Hower[3] and others strongly argue against this practice, and advocate storing all business logic in a business layer, and not encoding any business logic in the application's user services or database services tiers.

    Monday, October 1, 2007 2:39 AM