business-logic

When reading, I keep seeing references to what they call Business Objects . I've looked up on Wikipedia and such but I keep not getting what a Business Object is. Is there any easy explanation of what it is for someone that doesn't know a thing about software architecture and such? Also, what is Business Logic ? This is easy Every entity in the system, representing the human-world object which the system is expected to interact with is a business object. The human-world logic in the system around manipulating business objects is a business logic. This is opposed to the objects and logic being

I often see the phrases 'business logic' and 'application logic' in terms of web development (I assume it also applies to programming in general rather than just web development). This is quite new to me so I don't really know what it means, could anyone please explain me what is exactly meant by this? Is it just a 'buzz word' used by programmers? Or? Business logic is basically rules of the system according to functional specifications. For example Object A of type B must have attributed C and D, but not E. Application Logic is more of a technical specification, like using Java servlets and

Recently I started to move from a .NET platform to J2EE. I'm Eclipse to build JSP and Servlet applications which should use Business Logic layer. The approach in .NET is very simple I'm building web Application Project inside the solution, then Creating Class Library project and refers its output in Web Application References. How should I do it in Eclipse? Should I create separate project and build JAR file as output and refer it in Web Project? I'm new to Java so any comment will be more then welcomed. Danny. Yes, creating a separate Java project would be the way to go. Just a simple Java

i'm new to appcelerators titanium and javascript and i'm interested in coding an iphone app. i recognized that there is a need of "many" code for creating the UI. that's no problem so far, but i tend to separate that code from my application logic wisely. what are the best practices? [update] tweetanium is a great example how to structure a titanium mobile application ok, i just found a cool practice. i include the con_file.js with the application logic the view_file.js with Titanium.include('../controller/con_file.js'); now i'm able to access the hole data structure. i'll have a try: i tend

In separate data access & business logic layer, can I use Entity framework classes in business layer? EDIT: I don't think I will need to swap out the data access layer from my business logic in the future (i.e. will be SQL Server), however I will for the UI layer. Therefore the question is more meant to be are there any major issues with using EF classes for me in the business layer? Seems like there would be less plumbing code. Typically, the "best practice" approach would be something like this: in your Data layer, you have EF entities that get loaded from and stored back to the database in

What are the arguments for and against business logic in stored procedures? Against stored procedures: business logic in programming space I place a high value on the power of expression, and I don't find the SQL space to be all that expressive. Use the best tools you have on hand for the most appropriate tasks. Fiddling with logic and higher order concepts is best done at the highest level. Consequently, storage and mass data manipulation is best done at the server level, probably in stored procedures. But it depends. If you have multiple applications interacting with one storage mechanism

Let's say I want to enforce a rule: Everytime you call "StartJumping()" in your function, you must call "EndJumping()" before you return. When a developer is writing their code, they may simply forget to call EndSomething - so I want to make it easy to remember. I can think of only one way to do this: and it abuses the "using" keyword: class Jumper : IDisposable { public Jumper() { Jumper.StartJumping(); } public void Dispose() { Jumper.EndJumping(); } public static void StartJumping() {...} public static void EndJumping() {...} } public bool SomeFunction() { // do some stuff // start jumping.

First of all, I have seen many questions of this, but not enough reasoning behind that. If my question is not good enough and should be removed I'll understand. I have taken a look at, for example, this and a 45+ voted up answer says he advises you to put the business logic in the model, which sounds pretty logical. However, my first large project I have done with all my BL fully in the controllers, because I didn't question these things and looked how it is done in the AccountController which is the automatically added if you choose MVC with form authentication. All the methods look pretty