How deeply does Software Design for Python Programmers cover single responsibility principle?

Defines cohesion and demonstrates responsibility allocation, while deferring broader design tradeoffs to iterative development.

Single responsibility principle

As explained in Software Design for Python Programmers

The Single Responsibility Principle states that a class should have one primary responsibility and remain cohesive around it.

The Single Responsibility Principle keeps each class cohesive around one primary responsibility. A clear responsibility makes a class easier to use and maintain because its methods and instance variables serve one purpose. section 2.3.1

A cohesive book catalogue

A Book stores a book’s title and author attributes. A Catalogue maintains Book objects, adds new books, and finds matches. The separation keeps book data distinct from collection management and searching. section 2.3.1

Apply the principle by checking whether a class has a single, recognizable purpose:

Use later design principles to manage change, delegation, coupling, extension, interfaces, and duplication without creating unnecessary complexity. section 2.4

How Software Design for Python Programmers covers it

Cover of Software Design for Python Programmers

liveBook manning.com

Read Software Design for Python Programmers on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

The Art of CodeThe Single Responsibility Principle is an object-oriented design principle stating that a class should have only one reason to change.
liveBook manning.com

Object-Oriented Software Design in C++A design principle stating that a class should have one major responsibility.
liveBook manning.com

.NET MAUI in ActionThe single-responsibility principle is a software design principle stating that a component should have one primary reason to change.
liveBook manning.com

Unit Testing Principles, Practices, and PatternsThe Single Responsibility Principle states that a class or module should have one responsibility and one reason to change.
liveBook manning.com

ASP.NET Core in Action, 3eThe single-responsibility principle is a design principle stating that a class should have responsibility for one piece of functionality and change only when that functionality changes.
liveBook manning.com

GitHub Actions in Action: Continuous integration and delivery for DevOpsThe single responsibility principle is a software design principle stating that a component should have one primary responsibility and one reason to change.

Compare how 7 books explain single responsibility principle →

Related concepts

principlekind of · A principle is a general rule, guideline, or value that guides decisions, behavior, or judgments.
cohesive classimplemented by · A class whose methods and instance variables collectively serve one closely related primary responsibility.
SOLID principleskind of · The SOLID principles are five object-oriented software-design principles concerning single responsibility, openness to extension, substitutability, interface segregation, and dependency inversion.
separation of concernsimplements · Separation of concerns is a design principle that organizes a system so distinct responsibilities are handled by separate, independently manageable parts.
functionconfigures · A function is a callable program unit that performs an operation, may accept inputs, and can produce a result or side effect.
pipeline componentimplemented by · A pipeline component is a discrete, executable stage in a data or machine-learning workflow that performs an operation and may consume or produce data artifacts.

This explainer was generated by Manning's knowledge graph from the text of Software Design for Python Programmers. The section links point to the parts of the book it draws on.