Question

In my company I must use a Bll, Dal and model layer for creating applications with a database.

I’ve learned at school that every databasetable should be an object in my model. so I create the whole model of my database.
Also I’ve learned that for every table (or model object) there should be a DAO created into the DAL. So I do this to.

Now i’m stuck with the BLL classes. I can write a BLLclass for each DAO/ModelObject or I can write a BLLclass that combine some (logic) DAO’s…
Or i can write just one Bllclass that will manage everything. (this last one I’m sure it aint the best way..)

What is the best practice to handle this Bll ‘problem’?

And a second question. If a bll is in need of tablecontent from an other table where it aint responsible for, whats the best way to get the content? Go ask on the responsible BLL or go directly to the DAO?

I’m struggling with these questions the last 2 months, and i don’t know what is the best way to handle it.

Answer 1

You should start with what you need to make work the app.

For instance: “I need a web ui for user login”

1. So I need a controller that use a model to check nickname and pass
2. Then I need a bll object to do the logic for check nickname and pass
3. Then I need a dal object to access the database to retrieve user info

If you not start to think like that (a top to bottom aproach) then you are going to write a lot of code that is never going to be used.

note: if the dal is orm mapping or not is anecdotal. Also if the model use a bsl or the bsl use a model. IMHO.