divide and conquer Comparison Table

Object Oriented Software Engineering View all facts Glossary Help

subject > criterion > principle > design principle > divide and conquer

Next design principle: increasing cohesion Up: design principle Previous design principle: designing for testability

divide and conquer comparison table

Subject is an instance of is a kind of have benefits has definition

design principle principle

divide and conquer design principle
Separate people can work on each part. The original development work can therefore be done in parallel
An individual software engineer can specialize in his or her component and become expert at it
Each individual component is smaller, and therefore easier to understand
When one part needs to be replaced or changed, it can hopefully be done without having to replace or extensively change other parts
The principle of dividing something large into smaller units, so it can be dealt with more easily

Subject	is an instance of	is a kind of	have benefits	has definition
design principle		principle
divide and conquer	design principle		Separate people can work on each part. The original development work can therefore be done in parallel An individual software engineer can specialize in his or her component and become expert at it Each individual component is smaller, and therefore easier to understand When one part needs to be replaced or changed, it can hopefully be done without having to replace or extensively change other parts	The principle of dividing something large into smaller units, so it can be dealt with more easily

Next design principle: increasing cohesion Up: design principle Previous design principle: designing for testability