. NET distributed architecture development combat one of the story origins

This article mainly describes some of the background of the project.

New Richard was assigned to an enterprise Automation Information management team--automation Information Management Project (hereafter short aim), when Richard entered the project, the project started, The architecture of the project has also built the--soa architecture two weeks ago, and the main technologies used are also finalized: WCF, Linq.

Note: Because the project is the first to adopt the "new technology" (because it was not previously used wcf,linq, so called the new technology), the project began.

Six months later the problem began to appear (in fact, the problem began to appear, but we still think the problem is not: because at the time of design, the project's architecture was designed by the other two people in the project team, the whole project development is basically not using object-oriented thinking to develop, And while the architecture design is divided: Data tier, business layer, service layer, and UI layer, but each layer is tightly coupled, can be said to be "far-reaching": if the data access layer slightly changed, the business layer will follow, and then change the beginning of a layer of spread.

Everyone began to feel so tired, but the project has done this stage, it is impossible to repeat. Every time a new demand comes, the changes to the project can be said to be upside down. And the original design of the structure of the man also on the project began one months after the walk.

The following diagram shows the architectural design in the project:

I look good, the general structure is this design. Let's start by describing some of the call relationships between them and see what's wrong: