Implementing the un-implementable
By Sean McGrath, ITworld
There is a school of thought that holds fast to the principle that systems analysis has to be fully bottomed out before design/coding can sensibly proceed. The classic embodiment of this approach is the so-called waterfall method. There is another school of thought that holds fast to the principle that systems analysis is a fool's errand. Better to design a little, code a little, deliver a little and then iterate the procedure over and over again. Extreme programming embodies this approach. Today, I have a different form of controversy in mind. Brace yourself for a real shocker.
There is a school of thought that holds fast to the principle that systems analysis has to be fully bottomed out before design/coding can sensibly proceed. The classic embodiment of this approach is the so-called waterfall method. There is another school of thought that holds fast to the principle that systems analysis is a fool's errand. Better to design a little, code a little, deliver a little and then iterate the procedure over and over again. Extreme programming embodies this approach. Today, I have a different form of controversy in mind. Brace yourself for a real shocker.
0 Comments:
Post a Comment
<< Home