FUNDAMENTALS OF COMPUTER

SYSTEMS DEVELOPMENT ANALYSIS

APPLICATION DEVELOPMENT PROCESSES

Question [CLICK ON ANY CHOICE TO KNOW THE RIGHT ANSWER]
This principle suggests that each software module, class, or interface should have only one (1) reason to change.
A
SRP-Single responsibility Principle
B
OCP-Open-Closed Principle
C
ISP-Interface Segregation Principle
D
DIP-Dependency Inversion Principle
Explanation: 

Detailed explanation-1: -The idea behind the SRP is that every class, module, or function in a program should have one responsibility/purpose in a program. As a commonly used definition, “every class should have only one reason to change".

Detailed explanation-2: -The Single Responsibility Principle (SRP) is the concept that any single object in object-oriented programing (OOP) should be made for one specific function. SRP is part of SOLID programming principles put forth by Robert Martin. Traditionally, code that is in keeping with SRP has a single function per class.

Detailed explanation-3: -Single Responsibility Principle Robert Martin summarizes this principle well by mandating that, “a class should have one, and only one, reason to change.” Following this principle means that each class only does one thing and every class or module only has responsibility for one part of the software’s functionality.

Detailed explanation-4: -The single-responsibility principle is a computer-programming principle that states that every module, class or function in a computer program should have responsibility over a single part of that program’s functionality, and it should encapsulate that part.

Detailed explanation-5: -refers to the principle that no user should be given enough privileges to misuse the system on their own. For example, the person authorizing a paycheck should not also be the one who can prepare them.

There is 1 question to complete.