New game
Download
Get Academic Plan
Share game
Integrate it into your platform

You can integrate the game into an LMS compatible with LTI 1.1 or LTI 1.3 such as Canvas, Moodle, or Blackboard. This way, the scores will be automatically saved into the platform’s gradebook.
Download
You have exceeded the maximum number of games you can integrate into Google Classroom with your current Plan.

To integrate as many games as you want in Google Classroom, you need an Academic Plan or a Commercial Plan.

You have exceeded the maximum number of games you can integrate into Microsoft Teams with your current Plan.

To integrate as many games as you want in Microsoft Teams, you need an Academic Plan or a Commercial Plan.

Downloading games is an exclusive feature for users with an Academic Plan or a Commercial Plan.

Get your Academic Plan or your Commercial Plan now and start integrating your games into your LMS, website or blog.

If you wish, you can download a demo game here and test its integration:

SOLID Principles Quick True/False

Yes or No

(2)
Played 80 %Accuracy 82 Average time 00:47

About this activity

Challenge your SOLID knowledge with quick true/false items.

Created by

India

Download the paper version to play

Make your own free game from our game creator
Compete against your friends to see who gets the best score in this game

Top Games

%
Anonymous
Anonymous
%
%
%
You have exceeded the maximum number of games you can print with your current Plan.

To print as many games as you want, you need an Academic Plan or a Commercial Plan.

Print your game
SOLID Principles Quick True/False
 

SOLID Principles Quick True/FalseOnline version

Challenge your SOLID knowledge with quick true/false items.

by Swati Nikam
1

Liskov Substitution Principle (LSP) requires that subclasses can be substituted for their base class without changing expected behavior.

2

Interface Segregation Principle ( ISP) encourages clients to depend on large, all-encompassing interfaces.

3

Dependency Inversion Principle (DIP) suggests that high-level modules should depend on abstractions, not on concrete implementations.

4

Open/Closed Principle (OCP) means software entities should be open for extension but closed for modification.

5

Interface Segregation Principle (ISP) advocates for many client-specific interfaces rather than one fat interface.

6

Open/Closed Principle (OCP) says you should frequently modify existing classes to add new features rather than extending them.

7

Dependency Inversion Principle (DIP) states that high-level modules should depend on low-level modules directly, for performance reasons.

8

Single Responsibility Principle (SRP) mandates that a class must have only one method.

9

Single Responsibility Principle (SRP) states a class should have only one reason to change.

10

Liskov Substitution Principle (LSP) requires that subclasses must accept at least the same inputs as the base class and may override behavior arbitrarily.

Are you sure you want to leave the page?

If you leave the page, you will lose your game progress.