Comments on: System Design 101: Clear Requirements Help Reduce Project Cost http://r3r.com/blog/2007/system-design-101-clear-requirements-help-reduce-project-cost/ We use technology to help you connect more effectively with your audience, act on the most insightful data, and automate it all. Tue, 15 May 2012 17:30:07 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: J. Reitherhttp://r3r.com/blog/2007/system-design-101-clear-requirements-help-reduce-project-cost/comment-page-1/#comment-245 J. Reither Fri, 29 Feb 2008 21:10:06 +0000 http://blog.reitherco.com/?p=43#comment-245 jointcontact: Yes, sometimes it's "impossible to understand the full business or technical requirements..." Sometimes gut instinct is all you have. But every project should at least start with a goal in mind, and that goal should be the core of your documentation - it's going to be the bar by which the success of your project is measured. jointcontact: Yes, sometimes it’s “impossible to understand the full business or technical requirements…” Sometimes gut instinct is all you have. But every project should at least start with a goal in mind, and that goal should be the core of your documentation – it’s going to be the bar by which the success of your project is measured.

]]> By: jointcontacthttp://r3r.com/blog/2007/system-design-101-clear-requirements-help-reduce-project-cost/comment-page-1/#comment-68 jointcontact Mon, 31 Dec 2007 02:25:41 +0000 http://blog.reitherco.com/?p=43#comment-68 Thanks for this blog posting. One item I would like to add is that ironing out requirements for a new project is great, but sometimes its impossible to understand the full business or technical requirements if taking over work from a previous project.Resources and technologies change which can confuse the process and introduce hidden work items that I call "gotchas". These are the real problems with typical SLDC process and also contribute towards increase project costs. Thanks for this blog posting. One item I would like to add is that ironing out requirements for a new project is great, but sometimes its impossible to understand the full business or technical requirements if taking over work from a previous project.

Resources and technologies change which can confuse the process and introduce hidden work items that I call “gotchas”. These are the real problems with typical SLDC process and also contribute towards increase project costs.

]]> By: Sathianathanhttp://r3r.com/blog/2007/system-design-101-clear-requirements-help-reduce-project-cost/comment-page-1/#comment-69 Sathianathan Thu, 20 Dec 2007 14:53:31 +0000 http://blog.reitherco.com/?p=43#comment-69 Excellent content. And i also want to add that the Quality Product is developed based on the understanding of the system requirement clearly. The efforts need to be spent much only on this area after the analysis phase. The map designed to reach the goal in a step wise manner will help to ease out the tension in evey phase and also the system could be effectively controlled. I fully agree, that the big picture people needs to be explained the value of the work that is involved in the analysis phase. Excellent content. And i also want to add that the Quality Product is developed based on the understanding of the system requirement clearly. The efforts need to be spent much only on this area after the analysis phase. The map designed to reach the goal in a step wise manner will help to ease out the tension in evey phase and also the system could be effectively controlled. I fully agree, that the big picture people needs to be explained the value of the work that is involved in the analysis phase.

]]>