Requirements document - if you get that wrong, no amount of prototyping, modeling, or testing can save you. If you've gotten the client's specifications wrong, then you've gone ahead and built the wrong product.
Look at it this way - the customer asks you to build him a gorilla, and you thought you heard donkey.... do you really think that if you have in your head a load-bearing equine cart puller, that you can pull a knuckle walking banana-eating primate out of the later steps? The customer won't be paying a lot of attention until the test phase.... during prototype and design, all they'll notice is it is a mammal, which both are.
So don't assume that the next steps of the waterfall process will catch it - get the Requirements right, first and foremost. Know what your customer wants you to build.
2006-07-17 08:43:53
·
answer #1
·
answered by evolver 6
·
0⤊
0⤋
The most important step? Testing, but it is often left out. However, all of the steps of the development cycle are necessary to create a successful project.
2006-07-17 08:09:40
·
answer #2
·
answered by John J 6
·
0⤊
0⤋
Which model are you using?
Regardless of the development model, make darned sure you design for flex ability and maintainability! Regardless of how carefully you design to a specific set of requirements, one of the few things you can count on is that the requirements/expectations will change, usually after you are approximately 85% done with the implementation and pretty much totally committed to the basic structure.
Keep it simple while at the same time abstracting everything you possibly can.
2006-07-17 07:54:06
·
answer #3
·
answered by Anonymous
·
0⤊
0⤋
In terms of costs over time, the requirements phase of the SDLC can be considered the most important. If all the needs are not discovered early, it will be more expensive to try to "patch" those features late in implementation / testing than if those needs were documented up front in the requirements phase. That is why a good business analyst is essential nowadays - he/she can capture those needs early so they can be implemented and tested efficiently.
Cheers,
Andy
2006-07-17 07:51:59
·
answer #4
·
answered by xx342334234234 2
·
0⤊
0⤋
Step Of Sdlc
2016-12-10 20:49:58
·
answer #5
·
answered by stiefel 4
·
0⤊
0⤋
turning out to be up i presumed my challenge changed into to be ahead in college. Older I were given my challenge replaced to surviving, then it replaced to proving myself to others, then to stumble on a mate. Now, my challenge is to stay my own existence. Its an trouble-free time period yet quiet complicated. we stay from a progression of old recommendations and conditioning. Theres a second that comes very diffused and its like arising for air. Then it fades away. Now, my challenge is to be at shore and take in the solar to have the capacity to speak and to stay my own existence no longer others peoples. :)
2016-10-14 21:43:39
·
answer #6
·
answered by gettinger 4
·
0⤊
0⤋
Well, it seems to me they are all important.
Requirements, Design, Implementation, Test, Maintenance. What could be left out?
2006-07-17 07:46:26
·
answer #7
·
answered by Bors 4
·
0⤊
0⤋