Computer scienceSoftware development foundationsComputer science fundamentalsSoftware constructionIntroduction to design principles and SOLID

Single responsibility principle

One reason to change

Report a typo

What is the best description of the "one reason to change" objects?

Select one option from the list

They are responsible only for one issue

They split to different objects after one change

They have one method for changes

They consist of one method

Create a free account to access the full topic