LLD - 2 Assessment

Objective Problems:

1. Low-Level Designing involves:
   a) Creating detailed specifications for a software system
   b) Designing the user interface of a website
   c) Planning the high-level architecture of a system
   d) Testing the software for bugs and errors
2. Design principles are fundamental guidelines that:
   a) Help in creating complex user interfaces
   b) Provide step-by-step coding instructions
   c) Guide developers in designing software systems with desirable qualities
   d) Ensure code security and data encryption
3. Why should we use design principles?
   a) To make the code more complex and challenging to maintain
   b) To provide strict rules that every developer must follow
   c) To ensure maintainable, scalable, and robust software systems
   d) To avoid the need for code documentation
4. Design Patterns are used to:
   a) Provide step-by-step instructions for software installation
   b) Solve specific design problems in software development
   c) Document software requirements and specifications
   d) Facilitate project management and team collaboration
5. What is the key difference between design patterns and design principles?
   a) Design patterns provide guidelines, while design principles offer specific solutions.
   b) Design patterns focus on high-level architecture, while design principles are implementation-specific.
   c) Design patterns address recurring design problems, while design principles offer general guidelines.
   d) Design patterns are essential for low-level coding, while design principles are for high-level decision-making.
6. The Single Responsibility Principle (SRP) states that a class should have:
   a) Multiple reasons to change and modify the behaviour dynamically
   b) One reason to change and a single responsibility
   c) Multiple responsibilities to reduce code duplication
   d) No reason to change after it's created
7. The Open-Closed Principle (OCP) suggests that software entities should be:
   a) Closed for extension but open for modification
   b) Open for extension and closed for modification
   c) Constantly modified to accommodate new features
   d) Open for extension only when necessary
8. The Liskov Substitution Principle (LSP) states that:
   a) Subclasses should not be used interchangeably with their base class
   b) Subclasses should override all methods of the base class
   c) Subclasses should only inherit from one superclass
   d) Subclasses should be used interchangeably with their base class without affecting the correctness
9. Violating LSP can lead to:
   a) Increased reusability of code
   b) Unpredictable behaviour and bugs
   c) Simplification of the codebase
   d) Improved scalability of the software system
10. The consequences of breaking the Liskov Substitution Principle include:
    a) Improved maintainability and robustness
    b) Fragile Base Class Problem and tight coupling
    c) Simplified client code and reduced complexity
    d) Increased code reusability and code documentation

Subjective Problems:

1. Low-Level Designing plays a crucial role in the software development process. Explain the key steps involved in Low-Level Designing and discuss its significance in building robust and scalable software systems.
2. Design principles act as guiding principles for developers in designing software. Choose any two design principles (other than SOLID) and elaborate on their significance and how they contribute to creating high-quality software.
3. Design Patterns are widely used to address common design challenges in software development. Select one design pattern (e.g., Singleton, Observer, Factory) and explain its purpose, benefits, and real-world scenarios where it can be applied.
4. Compare and contrast Design Patterns and Design Principles. Highlight the main differences between these two concepts and explain how they complement each other in creating well-designed and maintainable software systems.
5. SOLID principles are fundamental guidelines in Object-Oriented Programming. Choose any two SOLID principles (other than Single Responsibility, Open-Closed, and Liskov Substitution) and discuss how they contribute to writing flexible, extensible, and easy-to-maintain code. Provide examples to support your explanation.