Relativism is easy to see an architecture error when completing a project. X gave us security concerns, or Y gave us a lot of extra work. They are caught in retrospect, but it would be nice to catch them earlier.
We plan to conduct architecture reviews before coding begins.
One way is simply to get the architect to present the project and see if we can find design flaws.
Does anyone have a more structured approach, perhaps with a checklist of "Did you think" or "How are you going to do."
I was thinking of something like:
- Security
- input
- Data access
- Deployment
- Update
source
share