Business logic
From Wikipedia, the free encyclopedia
In computing, in particular in object-oriented analysis and design of business computer systems, the business logic of a software system (sometimes called the domain logic because it relates to the problem domain[1] or the functional process logic) is that part of the whole system that deals with the performance of business-related tasks, such as transactions or account updates. It is distinguished from presentation logic, which is the part of the system that embodies the presentation of the objects in the system to the user, and from the CRUD layer, which is the part of the system that embodies the raw database access.[2][3]
Contents |
[edit] Scope of business logic
Business logic
- models real life business objects (such as accounts, loans, itineraries, and inventories);
- handles the storage of business objects (e.g. the mappings from the business objects to the database tables in the CRUD layer);
- 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[4]:
- 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.
[edit] Location of business logic
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.[5]
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[6] 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.
[edit] Tools for handling business logic
Business logic can be extracted from procedural code using a business rule management system.[7]
[edit] References
- ^ Simon Brown (April 2003). Implementing Business Logic in J2EE Applications.
- ^ Paragon Corporation (2003-07-19). Separation of Business Logic from Presentation Logic in Web Applications.
- ^ "business logic". TechEncyclopedia. (2006). CMP Media.
- ^ Steven Minsky (2005-03-27). The Challenge of BPM Adoption. eBizQ.
- ^ Khawar Zaman Ahmed and Cary E. Umrysh (2001-10-17). “Introduction to Enterprise Software”, Developing Enterprise Java Applications with J2EE™ and UML. Addison-Wesley. ISBN 0-201-73829-5.
- ^ Chad Z. Hower. Dude, where's my business logic?. The Code Project.
- ^ James Owen. "Bring business logic to light: JRules 4.5 tames business rules with friendly tools", JavaWorld, 2003-09-19.
[edit] Further reading
- Brett McLaughlin (March 2002). “Business Logic, Part 1”, Building Java Enterprise Applications, Vol I: Architecture. O'Reilly and Associates. ISBN 0-596-00123-1. — McLaughlin discusses the façade pattern for implementing the business layer of an application.
- Kathy Bohrer (November 1997). "Middleware isolates business logic". Object Magazine 7 (9): 41–46;. ISSN 1055-3614.
- Harumi Kuno, Mike Lemon, Alan Karp, and Dorothea Beringer (2001). F. Casati, D. Georgakopoulos, and M.-C. Shan "Conversations + Interfaces = Business Logic". Technologies for E-Services: Second International Workshop, TES 2001, Rome, Italy, September 14-15, 2001, Proceedings, Springer Berlin / Heidelberg. ISSN 0302-9743.
- Volker Turau (2002). "A framework for automatic generation of web-based data entry applications based on XML". Proceedings of the 2002 ACM symposium on Applied computing, Madrid, Spain: Web and e-business application, 1121–1126, ACM Press. ISBN 1-58113-445-2. — Turau presents an application framework implemented using Java Servlets and Java Server Pages that enables the separation between business logic and presentation logic, allowing development of each to proceed in parallel along relatively independent but cooperating tracks.
- Pau, L-F. and Vervest, P.H.M. (2003-12-08). "Network-based business process management: embedding business logic in communications networks". Erasmus University. — Pau and Vervest develop an approach for the embedding of business logic into the communications network that underlies a distributed application with a multiplicity of actors, in order to optimize the allocation of business resources from a network point of view.
