When should a modular design be implemented as monolithic software? How can this be accomplished? Is performance the only justification for implementation of monolithic software?

Modularity and Monolithic:

Modularity means, combination of design pattern and architecture. It is the single attribute of software which allows a program to be intellectually manageable.

It is divided into different name formats.

1.         Addressable components.

2.         Modules.

Modules are integrated to satisfy problem requirements. The simplicity of each small module will be overshadowed by the complexity of integration "Cost".

Hence, modular design is implemented as monolithic software, when the modularity is the single attribute of software that allows a program to be intellectually manageable".

It can be accomplished by divided into manageable pieces

Implementation of monolithic software:

Monolithic is the compartmentalization of data and function. Monolithic software is cannot be easily grasped by a software engineer which is a large program composed of a single module. But when the complex problem is divided into manageable pieces, then solution will make easy. In this, number of control paths like, span of reference, number of variables, and overall complexity would make understanding close to impossible.

Example:

"Divide-and-conquer"

please see the attached file for the complete solution.