Question
Which SOLID principle ensures that a class has only one
reason to change?Solution
The Single Responsibility Principle (SRP) states that a class should have only one reason to change, meaning it should have only one responsibility or function. This principle promotes cohesion by ensuring each class handles a specific part of the software functionality. For instance, a Customer class should handle customer data, while an Invoice class manages invoice generation. Adhering to SRP simplifies debugging, enhances maintainability, and prevents interdependent changes from cascading through the codebase. Why Other Options Are Incorrect :
- Open/Closed Principle : This emphasizes that classes should be open for extension but closed for modification, unrelated to SRP.
- Liskov Substitution Principle : This ensures that derived classes can replace base classes without altering program correctness.
- Dependency Inversion Principle : This recommends high-level modules should not depend on low-level modules but rather on abstractions.
- Interface Segregation Principle : This advises against forcing a class to implement interfaces it does not use, unrelated to SRP.
Which of the following is NOT part of auditor’s understanding of the entity and its environment under SA 315?
Which of the following financial statements can be prepared using a receipt and payment account?
Which of the following is NOT a key element of an independent auditor’s report under SA 700?
During a statutory audit, the auditor discovers a pattern of journal entries posted near year-end reversing shortly after year-end that inflate reported...
Vouching primarily relates to:
Internal auditor is removed and appointed by which among the following?
Which of the following provides the most reliable audit evidence?
Which of the following is NOT a type of audit opinion as per SA 700?
Internal check is a part of the:
Why must auditors obtain an understanding of internal control even if they do not intend to rely on it?