You really need to take in the whole post. If you read further, you would have read how the author says Bob Martin refined the definition of SRP to more “class level”.
However, SRP was re-interpreted by Uncle Bob with the definition “THERE SHOULD NEVER BE MORE THAN ONE REASON FOR A CLASS TO CHANGE”. By the definition, SRP was narrowed down to class level.
So in 20 words or less.
SoC is more about software architecture and SRP is more about OOP concepts.
And, still, your monster class breaks both definitions. Your own description of what it does points this out.
my abstract class contains all the methods that either a Controller or a View can use on a Model, or where the Model calls a DAO
Scott