Object-Oriented Design: Composition, Inheritance

What is the primary focus of the Single Responsibility Principle (SRP)?

What does the Open-Closed Principle (OCP) advocate for in software design?

Which principle ensures that subtypes are substitutable for their base types without altering the correctness of the program?

What is the main goal of the Interface Segregation Principle (ISP)?

What is the core concept behind the Dependency Inversion Principle (DIP)?

In object-oriented design, what is the term for when objects are related to one another?

Which type of object-oriented relationship implies that all objects have their own lifecycle, but there is ownership?

What is the term for a technique to combine objects or data types into more complex one?

Which type of relationship is best described as 'is-a'?

Which of the following is an example of an aggregation relationship?

In the context of SOLID principles, what does 'cohesion' refer to?

Which of the following design principles is most concerned with reducing the impact of changes in one part of the system on other parts?

What is the primary benefit of adhering to the SOLID principles in software design?

Which of the following represents a violation of the Interface Segregation Principle?

What is the key difference between aggregation and composition?

In the context of object-oriented programming, what does encapsulation primarily achieve?

What is the significance of 'decomposition' in software design?

Which of the following is a characteristic of a poorly designed system according to the Open-Closed Principle?

Which SOLID principle is most directly related to achieving high cohesion?

What is the primary consequence of violating the Liskov Substitution Principle?

In a well-designed system following the Dependency Inversion Principle, what should interfaces primarily define?

Which of the following scenarios exemplifies the correct use of the Open-Closed Principle?

You have a class that handles both database connections and data validation. Which SOLID principle is being violated?

What does the term 'coupling' refer to in software design?

If a class Square inherits from a class Rectangle, and the Rectangle class has methods to set width and height independently, what could happen if Square doesn't adhere to the Liskov Substitution Principle?

What is the primary goal of using abstraction in object-oriented design?

Consider a scenario where you have a ReportGenerator class. You want to be able to generate reports in different formats (PDF, Excel, CSV) without modifying the ReportGenerator class itself. Which SOLID principle would guide this design?

Which of the following best describes a situation where composition should be preferred over inheritance?

Given a Vehicle interface with methods like startEngine() and fly(), which SOLID principle is violated if a Car class implements this interface?

You have a PaymentProcessor class that directly depends on a CreditCard class for making credit card transactions. How could you refactor this to adhere to the Dependency Inversion Principle?

Which of the following is NOT a benefit generally associated with applying SOLID principles to software design?

In terms of object-oriented design relationships, what is the most significant contrast between 'association' and 'composition'?

Given a scenario where you have a logging system. Initially, it only supports logging to a local file. Now, your team wants to add support for logging to a database and a remote server. How can you best achieve this while adhering to the Open/Closed Principle?

Consider an Animal class with a makeSound() method. You have Dog and Cat classes inheriting from Animal. If you add a fly() method to the Animal class, what SOLID principle is most likely being violated?

In a system designed with the Dependency Inversion Principle (DIP), which of the following is true regarding the relationship between high-level modules and concrete implementations?

You are designing a system with a Sorter class that sorts a list of objects. You want to allow different sorting algorithms (e.g., bubble sort, merge sort) to be used. How could you design this using the DIP while allowing the client to chose from available sorting algorithms at runtime?

Assume you have a legacy system, and a particular module is notoriously difficult to change. Every small modification results in unforeseen bugs in seemingly unrelated parts of the system. Which SOLID principle is most likely being violated in this module?