Modular design rules of divide & conquer problem solving strategy - Objects Design
Software Engineering (MCQ) questions and answers
Q. Modular design unintentionally follows the rules of 'divide and conquer' problem solving strategy.
- Published on 23 Jul 15
Software Management (
Introduction of Software Engineering (
Software Specification & Measurement (
Software Process (
Process Modelling and SDLC (
Planning and Managing the Project (
Capturing the Requirement (
Designing the System (
Objects Design (
Program Writing (
Formal Modelling & Verification (
Delivering the System (
Maintaining the System (
Evaluating Products, Processes & Resources (
Software Process Improvement (
Improving Predictions, Products, Processes & Resources (
-Posted on 16 Oct 15
- It is a technique used to divide a software system into multiple discrete and independent modules, which in turn are expected to be capable of carrying out task(s) independently.
- The working of these modules is on the basic constructs for the entire software.
- Modules are designed by the designers in such a way that they can be executed and/or compiled separately and independently.
- Modular design unintentionally follows the rules of ‘divide and conquer’ problem-solving strategy this is because there are many other benefits attached with the modular design of a software.
- Advantage of modularization:
1. Smaller components are easier to maintain
2. Program can be divided based on functional aspects
3. Desired level of abstraction can be brought in the program
4. Components with high cohesion can be re-used again
5. Concurrent execution can be made possible
6. Desired from security aspect
Post your comment / Share knowledge
Enter the code shown above:
(Note: If you cannot read the numbers in the above image, reload the page to generate a new one.)