The project existing architecture is from Microsoft's classic enterprise application example: duwamish7, so I believe that such architecture should be suitable for our current business scale, but why do you have code repeat in practical applications, logic mess, maintenance difficulties? ? I think a big factor is that there is no good understanding of the DUWAMISH architecture, but just in the form of the project, the function of the development is not uniform (because the functional demand is a little proposed, often It is a functional development. After a while, another requirement will be proposed), and the result is like a layer of dog skin plaster to the original code.
After I have seen 9CBS "Duwamish 7 major analysis" article, "Reconstruction" has gradually emerged from me to my mind. Since the duwamish architecture is based on .NET's technology itself is suitable for SME applications, after reproducing the idea of researching this architecture, the comparison of existing projects is in design, and then "reconstruct"! (However, there is no detailed learning "refractoring" "refractoring" not know if this term is suitable for what I want to do, but this is the best one you want!) I think about the .NET-based duwamish architecture Some principled discussions should be able to find some basics in another book in Flower Martin! "Enterprise Architecture Pattern!
At present, the development of the project is first lacking a person who can know a clear understanding of the architecture. The functional design is completely carried out by the designer. If the designer is not a person who knows a clear understanding of the architecture, then his code began to corrode health. Architecture! Then, if the developers have a good understanding of the architecture through this sorting, do you need to assess whether it is good to meet the architecture of it in the design of new features? And if the architecture itself needs to be corrected, this part of this part is done?
