Convert ASP.NET MVC to n-tier architecture

Question

I just created an application using ASP.NET MVC. My company's programmers want to build all future modules using the n-Tiered architecture (presentation layer, business logic, data access layer).

I am not a programmer and do not know why this makes sense? Do I have to completely rewrite all the code or can it be transformed?

We create HRIS with Business Intelligence.

Someone please explain why or why this approach does not make sense or does not make sense.

Answer 1

Honestly, it makes no sense to me.

"N-" :

• -

MVC ( M odel, V iew, C ontroller) :

• ( ) ( )
• ( )
• (- )

, . , ?

.

Answer 2

, , :

- , , , , :

1) / 2) - 3) /

, , ( biz). , , .

, . : ? ... , "" .

, , ( ), , . , , , , .

, , . , , :

• , . , MVC,
• - , , ,

!

Answer 3

, ? .

M, V C , .

, , ( ) // , , , , MVC , MVC.

Answer 4

A three-tiered approach does contribute to better future reuse. In fact, your newly created MVC-based application can use a three-tier model (at least the model and part of the controller). The MVC can act as a facade using a 3-level solution in the background.