I don’t have a drawing tool at hand, so I’ll have to describe my issues in text. This diagram is way too simple to describe what actually happens. For instance, suppose the Coding step exposes an error in Design. It should not be necessary to pass through Testing...Analysis to get back to the Design step. You can generalize that and improve the accuracy of the cycle by adding loops from the output of each stage back to the beginning of every predecessor stage. however, this has the counterbalancing negative effect of making the diagram very ugly.
I don’t suppose it’s necessary to have a fully realistic SDLC flow diagram, so long as we all understand that no matter where we are in the cycle, if we discover an error has been made at some preceding point, we should feel free to return to that point and try to fix the problem, rather than blindly trudging through and letting an end user feel the pain.
development/overview.txt · Last modified: 2007/09/05 19:15 (external edit)
Discussion
Well, you wanted discussion ;)
I don’t have a drawing tool at hand, so I’ll have to describe my issues in text. This diagram is way too simple to describe what actually happens. For instance, suppose the Coding step exposes an error in Design. It should not be necessary to pass through Testing...Analysis to get back to the Design step. You can generalize that and improve the accuracy of the cycle by adding loops from the output of each stage back to the beginning of every predecessor stage. however, this has the counterbalancing negative effect of making the diagram very ugly.
I don’t suppose it’s necessary to have a fully realistic SDLC flow diagram, so long as we all understand that no matter where we are in the cycle, if we discover an error has been made at some preceding point, we should feel free to return to that point and try to fix the problem, rather than blindly trudging through and letting an end user feel the pain.