How to correctly build n-layer architecture of an ASP.NET MVC application?

Question

ASP.NET

Functional requirements:
The application should consist of the following subsystems:
1. Diary.
2.List of contacts.
How to build the right architecture? It comes to mind that there should be 1 Pl (project), split the business logic into 2 parts (2 projects), and 1 DAL.

Answer 1

In a separate layer, you should select only what is subject to changes with support, or will be used as a component somewhere else. By default it is ui/web, dal, business-logic. Sometimes models are taken out in a separate layer, because. they can be used as a gap between different layers, especially if it's a dto of a model.