Converting ASP.NET MVC to n-Tiered Architecture

Question

I just built an application using ASP.NET MVC. The programmers at my company want to build all future modules using n-Tiered (Presentation Layer, Business Logic Layer, Data Access Layer) architecture.

I am not the programmer and need to know why this makes sense? Do I have to completely rewrite the entire code or can it be converted?

We are building an HRIS system with Business Intelligence.

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

Answer 1

Honestly, it doesn't make sense to me.

In "N-Tier" architecture, you have three layers:

• Data Access Layer
• Business Logic Layer
• Presentation Layer

In MVC (short for Model, View, Controller), you have three layers:

• Model (Data Access Layer) (if you use the Repository pattern)
• View (Presentation Layer)
• Controller (Business Logic Layer)

In short, your application is already written, and provides separation of concerns. Now they want to rewrite it to essentially just rename folders?

That doesn't make sense at all.