The final system is hence constructed, supported by the ultimate output. The final system is completely evaluated and tested. Routine maintenance is administered on a seamless basis to forecast large-scale failures and to reduce the time period. The users check the primary output, noting its strengths and weaknesses, the things which need to be carried ahead in the next steps and the things which need to be discarded. The developer collects and examines the remarks from the all the stakeholders.
5. The first paradigm is changed, supported by the comments provided by the users, and is shaped to a second output of the new system.
6. The second output is evaluated in the same manner as was the primary output.
7. These steps are reiterated persistently, till the users are satisfied with the output.