Some advices for project organization, organization

Some advices for project organization, organization

/* By Dylan SUN*/

I 've been worked recently on the project structure refactoring. A good project structure cocould give you a good visibility and a clear understanding even you are brandly new in a project, and make your further development much easy.

Some practices cocould be applied to increase the project maintainability and facilitate the development in the team if there are multiple projects and multiple solutions.

I wowould like to introduce some advice based on my own experience.

2.1 ExternalReferences: all your references from other solutions.
2.2 Libraries: your projects shared to all layers
2.3 PresentationLayer: this cocould be ASP. NET projects, WPF projects, Window Forms projects.
2.4 ServiceLayer: it contains different services to provide different functionalites to presentation layer.
2.5 BusinessLayer: it implements des business logics.
2.6 DataAccessLayer: a centric layer to manager all the data access in your projects
2.7 UnitTests: include your unit tests
2.8 IntegrationTests: as integration tests cocould be complicated and take long time. It's preferred to have a dedicated project for it.

The project organization really depends on the product you are developing. A good project organization can make your development much easier. So before development a project, take a little time to well conceive its organization.

I hope you find this article helpful! Thanks.