Single-Responsibility Principle

A module should be responsible to one and only one user

A class should have only one reason to change (correct)

A module should be responsible to multiple users

A class should have multiple reasons to change

To make a class more robust (correct)

To couple two things that change for different reasons

To make a class more efficient

To make a class more versatile

Separating the content of a report from the format of a report (correct)

Having a module that compiles and prints a report

Having a module that is responsible to multiple users

Having a module that is responsible to one user