How to do a preproject Architecture review -


An architecture error is easy to see when this project is over. X gave us security problems, or wai gave us a lot of extra work. They were caught in the previous seats, but it would be good to catch them first.

We are planning to review the architecture before coding begins.

To present the project to the architect and see if we can find flaws in the design.

Does anyone have a more structured approach, perhaps with the "Have you thought" or "How are you going to" check list?

I was thinking something like this:

  • Security
  • Logging
  • Data Access
  • Deployment
  • Upgrade
  • Additional items to add to your list, special order In:

    • Performance - latency, bandwidth, scaling or other factors related to your flexibility
    • Supportability - You are already logging in, but other diagnostic measurements (Java -JMX, Windows-WMI / Performance Counter or some other flexibility - Flexibility - There is difficulty in changing architecture later (this is usually one of those things that is done externally and creates more problems as needed but discusses while evaluating the design
    • Threading model / locking model - Is it clear how data will be protected? How will the resource dispute be controlled?
    • Resources Requirements - Memory consumption at different levels of usage Is it involved in your constraints?
    • Error handling - When something fails in the product, do architecture get support for cleaning and reporting problems is? Understanding - Forget about the complex complex architecture implementation, if the majority of the team, and especially the clue, can not keep the architecture, then its philosophy and rule, in its head, architecture no difference. Will not do
    • Compatibility Whether it tries to use every possible pattern or focuses on regular, repetitive patterns It is not that choosing the correct pattern for each problem is not a good thing, but a lot Having all the patterns can make sense of understanding and implementation mistakes. An architect should try to show everything (or latest cool thing) in every project. Testable - Does the design support or test (system and integration) hurt the efforts whether the test can be automated or do you repeat the regression test depending on the continuous dependence of the testers so you know that Your team has not broke the product?
    • Does architecture actually solve the problem that you are trying to solve and within the scope of the problem? If the duplex is sufficient, then do not create the skyline.

    Comments

    Popular posts from this blog

    sql - dynamically varied number of conditions in the 'where' statement using LINQ -

    asp.net mvc - Dynamically Generated Ajax.BeginForm -

    Debug on symbian -