That's not a bad model to view it through, but I would say calling them "phases" instead of something like "activities" creates a false reliance on ordering. In many successful programming projects/products, those five activities occurred simultaneously, or out of order, or in waves of progress along all or some activities. Seldom has it ever been a clean single waterfall pass.