MugUp logoMugUp
HomeBrowsePricingAboutBlogContact
LoginSign Up
© 2026 MugUp. All rights reserved.
HomeAboutDeck LibraryBlogChangelogContactFeature RequestsDeck Requests
Terms of ServicePrivacy PolicyCookie Policy
  1. Browse decks
  2. Clean Code & Software Engineering Principles
  3. SOLID Principles, One by One
Public deck

Clean Code & Software Engineering Principles

The language-agnostic foundation deck for engineers: SOLID, design heuristics, naming, functions, code smells and refactoring moves — the vocabulary that code review assumes you already have.

Engineering
AShared by Alex Chen
1PlaySign in to clone

You’re reading a free preview. Sign up to see every topic and question — and to play this deck as games.

See the whole deck

SOLID Principles, One by One

The five principles collected under the SOLID acronym, stated precisely — including the two that are most often misquoted.

Play topicBack to deck

Content

42 total questions

MCQ: 10
Fill-in: 8
Flashcards: 14
Pair match: 10
SOLID Principles, One by One – Flashcards
Flashcards

Card #1

What does the acronym SOLID stand for?

Card #2

State the Single Responsibility Principle.

Card #3

State the Open/Closed Principle, and name who introduced it.

11 more questions in this game

Showing 3 of 14. Sign up free to see the rest.

Sign up freeLog in
SOLID Principles, One by One – MCQ
Multiple Choice Questions
  1. 1. Which statement is the actual Interface Segregation Principle?

    • Clients should not be forced to depend on methods they do not use
    • Every interface should declare at most one method
    • Interfaces should always be preferred to abstract classes
    • A class should implement no more than one interface
  2. 2. Who introduced the Open/Closed Principle?

    • Bertrand Meyer
    • Barbara Liskov
    • Kent Beck
    • Michael Feathers
  3. 3. A high-level OrderService directly constructs a MySqlOrderRepository. Which principle does this most directly violate?

    • Dependency Inversion
    • Interface Segregation
    • Liskov Substitution
    • Open/Closed
7 more questions in this game

Showing 3 of 10. Sign up free to see the rest.

Sign up freeLog in
SOLID Principles, One by One – Fill-in-the-blank
Fill in the Blank
  1. 1. The Open/Closed Principle says software entities should be open for extension but closed for ___.

    Answer:modification

    Hint: The opposite of extension here

  2. 2. The ___ Substitution Principle requires that a subtype be usable anywhere its base type is expected.

    Answer:Liskov

    Hint: Named after a computer scientist

  3. 3. Interface Segregation says clients should not be forced to depend on ___ they do not use.

    Answer:methodsalso: method

    Hint: What an interface declares

5 more questions in this game

Showing 3 of 8. Sign up free to see the rest.

Sign up freeLog in
SOLID Principles, One by One – Pair match
Pair Match
Single Responsibility↔One reason to change; answers to one actor
Open/Closed↔Extend behaviour without editing working code
Liskov Substitution↔Subtypes usable wherever the base type is
7 more questions in this game

Showing 3 of 10. Sign up free to see the rest.

Sign up freeLog in