Modularization is very important to the execution of a program. Due to the operations of a program, the flow and step its must complete has to utilize modules, in order to function properly. Even though writing a program, start to finish, can be done, it is not without its own complications.
Modules are better built in parts; multiple parts of a program require attention, and this allows multiple people to target various parts at a time. For instance, in the Payroll Report program, one team can design the housekeeping() module, while another can work on the detailLoop(). This allows different people to pull focus on various factors, and not worry about designs outside the scope of work. Because of how this is designed, modules assist in maintaining the programs creation and execution. If something is wrong in a module, then that particular module can be reviewed, or rewritten, without the entire project going under. This also allows for verified modules to be utilized in other programs that may be useful. Another payroll program that is orchestrated to employees that are prevailing wage may have need for a separate program, due to union or federal regulations. By such, even though payroll functions share a general ideal on how to operate, factors in hourly / salary employees do not carry over in prevailing wage. so, the housekeeping() module may remain, but the detailLoop() module will undergo a different programming. This helps cut the work down, because one module can be used, and that leaves the staff to focus on one module.