The three (3) important characteristics of a bad design architecture that should be avoided are: rigidity, fragility, mobility.

The SOLID principles of object-oriented design are applied to software development projects to make software easier to change when requirements changes.

This principle suggests that each software module, class, or interface should have only one (1) reason to change.

Each of the SOLID principles can be practiced by any software developer to help them in solving various software development problems.

To implement the Interface Segregation Principle (ISP), use an interface, an abstract class, or abstract methods to extend the functionality of the class.

In software engineering, design principles are the reusable solutions to commonly occurring problems in software design.

When a solution is repeatedly used in various projects, someone eventually puts a name to it and describes the solution in detail.

It describes the elements that make up the design, their relationships, responsibilities, and collaborations.

These are the results and interchanges of applying the pattern to the problem.

This provides an interface for creating objects in a superclass but allows subclasses to alter the type of object that will be created.

This allows developers to produce families of related objects without specifying their concrete classes.

Builder Pattern allows developers to construct complex objects step by step.

The Creational Pattern delegates the cloning process to the actual objects being cloned.

When a developer wants to create an exact copy of an object, s/he has to create a new object of the same class.