When using the Waterfall Approach, development activities are performed in order, with possibly minor overlap, but with little or no iteration between activities.
Explanation:
There is a seamless execution of software operation with perhaps a slight variation, but little or no repetition. User standards are identified, requirements are described and the whole system is designed, intended and tested at one moment in time for ultimate delivery.
A document-based approach better suited to structures of strongly precedent and reliable requirements.
Sometimes referred known as the great linear and sequential model, the waterfall model is also quite linear and sequential for the activity flow in this model, as its title suggests.
