Would you agree this is the definition of a PHP framework?

[tony_marston404]

@s_molinari

tony_marston404:
The methods fall into one of the following categories

1. Methods which allow it to be called by the layer above it (the Controller or the View)
2. Methods which allow it to call the layer below it (the Data Access Object).
3. Methods which sit between these two. Many of these are “customisable” methods which are empty, but could be filled with code in order to override the default behaviour.

Wouldn’t you say these are 3 different responsibilities? If not, why not?

No, they are NOT different responsibilities. All those operations form a cohesive unit and therefore belong in the same class. To split them into artificially small classes would convert a modular system into a fragmented system and make it less readable. I am not the only one with this opinion. This is what Tom DeMarco wrote in his book Structured Analysis and System Specification:

Cohesion is a measure of the strength of association of the elements inside a module. A highly cohesive module is a collection of statements and data items that should be treated as a whole because they are so closely related. Any attempt to divide them would only result in increased coupling and decreased readability.

@s_molinari

Responsibilities, not responsibility. It is plural, not singular.

So you are saying that the meaning of a word changes when it switches from singular to plural?? What a load of BS.

SRP is exactly the same as SoC
responsibility = concern
responsibilities = concerns