Comments on: Let design guide, not dictate http://www.ericfeminella.com/blog/2008/05/27/let-design-guide-not-dictate/ Thoughts on Software Design and Development Sun, 08 Jan 2012 14:25:56 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Augie http://www.ericfeminella.com/blog/2008/05/27/let-design-guide-not-dictate/comment-page-1/#comment-49515 Augie Fri, 06 Jun 2008 18:42:38 +0000 http://www.ericfeminella.com/blog/2008/05/27/let-design-guide-not-dictate/#comment-49515 Eric great article. Eric great article.

]]> By: eric http://www.ericfeminella.com/blog/2008/05/27/let-design-guide-not-dictate/comment-page-1/#comment-44986 eric Fri, 30 May 2008 18:32:57 +0000 http://www.ericfeminella.com/blog/2008/05/27/let-design-guide-not-dictate/#comment-44986 Very well put Rex :) Requirements guides design guides implementation guides iteration. I plan on writing about requirements in a separate post, however that is a whole other subject in of itself. Thanks, Eric Very well put Rex :) Requirements guides design guides implementation guides iteration.

I plan on writing about requirements in a separate post, however that is a whole other subject in of itself.

Thanks,
Eric

]]> By: Rex Sheridan http://www.ericfeminella.com/blog/2008/05/27/let-design-guide-not-dictate/comment-page-1/#comment-44539 Rex Sheridan Thu, 29 May 2008 17:44:17 +0000 http://www.ericfeminella.com/blog/2008/05/27/let-design-guide-not-dictate/#comment-44539 I think this is an insightful post, probably because I agree with everything you said :) I should add that a high-level requirements document really helps in the design process. It should be simply a description of what the software SHOULD do, nothing else. It doesn't need to be all that formal either. But then again, I work for a smaller company where such formalism is often unnecessary overhead. So my thoughts are: Requirements guides design guides implementation guides iteration. I think this is an insightful post, probably because I agree with everything you said :) I should add that a high-level requirements document really helps in the design process. It should be simply a description of what the software SHOULD do, nothing else. It doesn’t need to be all that formal either. But then again, I work for a smaller company where such formalism is often unnecessary overhead.

So my thoughts are: Requirements guides design guides implementation guides iteration.

]]> By: Fabianv http://www.ericfeminella.com/blog/2008/05/27/let-design-guide-not-dictate/comment-page-1/#comment-44460 Fabianv Thu, 29 May 2008 08:58:59 +0000 http://www.ericfeminella.com/blog/2008/05/27/let-design-guide-not-dictate/#comment-44460 You're my hero... You’re my hero…

]]>