Q.1 Which of the following is NOT a fundamental software design principle?
Abstraction
Encapsulation
Redundancy
Modularity
Explanation - Redundancy is not considered a design principle; instead, principles like abstraction, encapsulation, and modularity guide effective software design.
Correct answer is: Redundancy
Q.2 What does the principle of 'Separation of Concerns' emphasize?
Combining multiple tasks into one function
Isolating different aspects of a system
Reusing the same code everywhere
Hiding unnecessary details
Explanation - Separation of Concerns means dividing a software system into distinct sections so each handles a separate concern or responsibility.
Correct answer is: Isolating different aspects of a system
Q.3 Which design principle supports reusability by bundling data and methods?
Abstraction
Encapsulation
Inheritance
Polymorphism
Explanation - Encapsulation ensures that related data and functions are grouped together, which supports reusability and maintainability.
Correct answer is: Encapsulation
Q.4 What is the main goal of modularity in software design?
To increase system complexity
To divide system into manageable parts
To duplicate components
To improve runtime speed only
Explanation - Modularity breaks software into independent modules, making development and maintenance easier.
Correct answer is: To divide system into manageable parts
Q.5 Which of the following is an example of 'Design for Change' principle?
Hardcoding values
Using configuration files
Duplicating code
Writing monolithic programs
Explanation - Using configuration files makes a system adaptable without modifying the core code, following the 'Design for Change' principle.
Correct answer is: Using configuration files
Q.6 Which design principle ensures that classes should have only one responsibility?
Open/Closed Principle
Single Responsibility Principle
Liskov Substitution Principle
Interface Segregation Principle
Explanation - The Single Responsibility Principle states that a class should have only one reason to change, ensuring focused responsibilities.
Correct answer is: Single Responsibility Principle
Q.7 The Open/Closed Principle states that software entities should be:
Open for extension but closed for modification
Open for modification but closed for extension
Always open for changes
Always closed to changes
Explanation - This principle allows extending functionality without modifying existing code, thus ensuring stability.
Correct answer is: Open for extension but closed for modification
Q.8 Which of these is an example of 'Loose Coupling' in software design?
Hardcoded dependencies
Direct database calls in UI layer
Using dependency injection
Global variables across modules
Explanation - Dependency injection reduces coupling by allowing components to depend on abstractions rather than concrete implementations.
Correct answer is: Using dependency injection
Q.9 High cohesion in a module means:
Module has unrelated functions
Module has closely related responsibilities
Module depends heavily on others
Module is loosely connected
Explanation - High cohesion ensures a module is focused on a single purpose, improving clarity and maintainability.
Correct answer is: Module has closely related responsibilities
Q.10 Which design approach emphasizes solving problems at the highest level of abstraction?
Bottom-up design
Top-down design
Spiral design
Incremental design
Explanation - Top-down design begins with a general system overview and progressively breaks it down into detailed parts.
Correct answer is: Top-down design
Q.11 The Liskov Substitution Principle ensures:
Child classes should not override parent methods
Child classes must be substitutable for parent classes
All methods must be static
Inheritance should be avoided
Explanation - Liskov Substitution Principle states that derived classes should be replaceable by their base classes without affecting correctness.
Correct answer is: Child classes must be substitutable for parent classes
Q.12 In software design, DRY stands for:
Don't Repeat Yourself
Do Right Yourself
Design Reuse Yield
Data Reuse Year
Explanation - DRY principle encourages avoiding code duplication to improve maintainability and reduce errors.
Correct answer is: Don't Repeat Yourself
Q.13 Which of the following is an advantage of modular design?
Increased redundancy
Easier debugging and testing
Higher coupling
Unclear responsibilities
Explanation - Modular design simplifies debugging and testing as each module can be tested independently.
Correct answer is: Easier debugging and testing
Q.14 In object-oriented design, what principle promotes code reuse through inheritance?
Abstraction
Encapsulation
Polymorphism
Inheritance
Explanation - Inheritance allows one class to acquire properties and behaviors of another, promoting code reuse.
Correct answer is: Inheritance
Q.15 Which of the following is NOT a part of SOLID principles?
Single Responsibility
Open/Closed
Dependency Inversion
Encapsulation
Explanation - Encapsulation is an OOP concept but not one of the SOLID principles.
Correct answer is: Encapsulation
Q.16 Which principle is applied when designing interfaces that clients should not be forced to implement?
Single Responsibility Principle
Open/Closed Principle
Interface Segregation Principle
Dependency Inversion Principle
Explanation - Interface Segregation Principle states that no client should be forced to depend on methods it does not use.
Correct answer is: Interface Segregation Principle
Q.17 What is the benefit of abstraction in software design?
Increases implementation complexity
Hides unnecessary details
Exposes internal logic
Reduces modularity
Explanation - Abstraction focuses on essential features while hiding the underlying details, simplifying design.
Correct answer is: Hides unnecessary details
Q.18 Which design method emphasizes iterative prototyping and feedback?
Waterfall model
Spiral model
Big Bang model
V-Model
Explanation - Spiral model combines iterative development with systematic risk evaluation and feedback loops.
Correct answer is: Spiral model
Q.19 What does 'low coupling' between modules mean?
Modules depend heavily on each other
Modules have minimal dependencies
Modules duplicate each other’s code
Modules are all identical
Explanation - Low coupling ensures modules can work independently, improving flexibility and reusability.
Correct answer is: Modules have minimal dependencies
Q.20 Which design methodology emphasizes incremental improvements over big upfront design?
Agile design
Waterfall design
Structured design
Monolithic design
Explanation - Agile design promotes adaptive planning and iterative development, adjusting design as requirements evolve.
Correct answer is: Agile design
Q.21 What is the main drawback of tight coupling in software?
Improves maintainability
Reduces flexibility
Simplifies testing
Increases modularity
Explanation - Tightly coupled modules depend on each other too much, reducing flexibility and complicating maintenance.
Correct answer is: Reduces flexibility
Q.22 The Dependency Inversion Principle states:
Depend on concrete classes, not abstractions
Depend on abstractions, not on concretions
Avoid inheritance completely
Always use global variables
Explanation - The principle suggests designing systems where high-level modules depend on abstractions instead of specific implementations.
Correct answer is: Depend on abstractions, not on concretions
Q.23 Which design strategy refines the system by breaking down high-level processes into smaller parts?
Top-down design
Bottom-up design
Black-box testing
Prototyping
Explanation - Top-down design progressively decomposes a system from high-level to low-level components.
Correct answer is: Top-down design
Q.24 In design patterns, the 'Observer' pattern is mainly used for:
One-to-many dependency management
Creating objects
Hiding complexity
Code optimization
Explanation - Observer pattern ensures that when one object changes state, its dependents are notified automatically.
Correct answer is: One-to-many dependency management
Q.25 What is the purpose of using design principles in software engineering?
To make software harder to understand
To improve maintainability and quality
To increase coding effort
To avoid documentation
Explanation - Design principles help create software that is easier to understand, extend, and maintain.
Correct answer is: To improve maintainability and quality