Where to keep business logics in MVC architecture?

Question

In my company we have recently started developing MVC application. Our task is to write the business logic layer and in future it should be with less maintenance.

We have couple of web services to add/update/delete user information.

Now we have to add the business logics like:

If Field1 on the page is 'xxxx' then field2 should be in the range of 1000 to 2000 If field3 is some department then field4 should be only in some sub departments.

So we have to design the layer so that in future our admin(who don't have programming knowledge) can go in and change the logics so that it will work. Please give me some suggestions.

So far what i have got is: Write all these conditions in Model and validate them when user click save button.

Thanks in advance.

Answer 1

Business logic should kept inside the model. You should aim to have a big Model and a small controller.

You may find this interesting to read this.

Also check Where does the “business logic layer” fit in to an MVC application?