Comments on: How to incur 3X costs for 1X worth of functionality http://blog.markturansky.com/archives/92 software architecture & engineering, code hints, sometimes philosophy, photography, life, etc. Wed, 07 Jul 2010 08:09:58 -0400 http://wordpress.org/?v=2.8.6 hourly 1 By: Bubba http://blog.markturansky.com/archives/92/comment-page-1#comment-756 Bubba Tue, 17 Jun 2008 17:34:51 +0000 http://blog.markturansky.com/archives/92#comment-756 You are dead-on about the design review. In any situation where the codebase is a) non-trivial and b) involves more people than can share a pizza design reviews are a must. They are not silver bullets though and just walking through them won't get it done. In my experience, the design review most have people engaged (i.e., not sleepwalking through the review because the manager made them do it) and should have some clearly defined principles to follow. Good design reviews don't just look at "will this meet the app needs" but also have to pay attention to adherence to non-functional requirements (scalability, maintainability, extensibility, availability, reliability, etc) and overall architecture. You are dead-on about the design review. In any situation where the codebase is a) non-trivial and b) involves more people than can share a pizza design reviews are a must.

They are not silver bullets though and just walking through them won’t get it done. In my experience, the design review most have people engaged (i.e., not sleepwalking through the review because the manager made them do it) and should have some clearly defined principles to follow.

Good design reviews don’t just look at “will this meet the app needs” but also have to pay attention to adherence to non-functional requirements (scalability, maintainability, extensibility, availability, reliability, etc) and overall architecture.

]]>