We provide Principios SOLID online (apkid: com.alvikapps.thesolidprinciples) in order to run this application in our online Android emulator.
Description:
Run this app named Principios SOLID using MyAndroid.
You can do it using our Android online emulator.
In this app you will find the definition of each of the 5 SOLID principles to build quality software.
Here are the SOLID principles and a short definition.
SOLID Principles: Single Responsibility Principle:
The single responsibility principle states that a class must have one and only one reason to change, therefore only one responsibility.
This principle implies cohesion, which in Software Engineering means the degree of relationship between the pieces of functionality of the source code of a module or class.
SOLID Principles: Open / Close Principle:
The open / close principle states that the behavior of a class must be able to be extended without being modified.
In other words, a class must be open for an extension but closed for a modification.
For example, if we wanted to create a program that would find the area of a shape, we could start by creating a function that would check whether a shape is a rectangle or a circle and then determine the area accordingly.
The problem with this is that if we wanted to find the area of a different type of shape then we would have to modify the class.
By the open / close principle, it is better to make a separate class for each type of shape, with its own method or function to determine the area of the shape.
This would leave the program open for extension in the form of additional classes that are made to extend the functionality of the program, but the program would be closed for modification because the existing code would not have to be changed.
SOLID Principles: Liskov Substitution Principle:
Liskov's Substitution Principle states that subtypes must be replaceable by their base types.
One motivation behind this principle is to ensure that inheritance is not being used when it is not appropriate for the code.
Although it may be easier to extend a class to a subclass, if the functionality of the class is not going to be used or is going to be overridden by the subclass, then inheritance should not be used.
SOLID Principles: Principle of interface segregation:
The principle of interface segregation states that it is better to have several specific interfaces than one general interface.
This principle implies the cohesion of the interfaces and the benefits of having few behaviors.
According to the Principle of Segregation of the Interface, the dependency of one class with respect to another should be the smallest interface possible.
The idea behind the Principle of Interface Segregation is that if the code implements an interface then it should use everything in the interface and the code should not depend on methods that it does not use or that it should not have access to either.
The solution to this is to keep the interfaces small to minimize interdependence.
SOLID Principles: Dependency Inversion Principle:
The dependency reversal principle consists of two parts.
The first is that high-level modules should not depend on low-level modules; both should depend on abstractions.
The second is that the abstractions must not depend on the details, the details must depend on the abstractions.
Here are the SOLID principles and a short definition.
SOLID Principles: Single Responsibility Principle:
The single responsibility principle states that a class must have one and only one reason to change, therefore only one responsibility.
This principle implies cohesion, which in Software Engineering means the degree of relationship between the pieces of functionality of the source code of a module or class.
SOLID Principles: Open / Close Principle:
The open / close principle states that the behavior of a class must be able to be extended without being modified.
In other words, a class must be open for an extension but closed for a modification.
For example, if we wanted to create a program that would find the area of a shape, we could start by creating a function that would check whether a shape is a rectangle or a circle and then determine the area accordingly.
The problem with this is that if we wanted to find the area of a different type of shape then we would have to modify the class.
By the open / close principle, it is better to make a separate class for each type of shape, with its own method or function to determine the area of the shape.
This would leave the program open for extension in the form of additional classes that are made to extend the functionality of the program, but the program would be closed for modification because the existing code would not have to be changed.
SOLID Principles: Liskov Substitution Principle:
Liskov's Substitution Principle states that subtypes must be replaceable by their base types.
One motivation behind this principle is to ensure that inheritance is not being used when it is not appropriate for the code.
Although it may be easier to extend a class to a subclass, if the functionality of the class is not going to be used or is going to be overridden by the subclass, then inheritance should not be used.
SOLID Principles: Principle of interface segregation:
The principle of interface segregation states that it is better to have several specific interfaces than one general interface.
This principle implies the cohesion of the interfaces and the benefits of having few behaviors.
According to the Principle of Segregation of the Interface, the dependency of one class with respect to another should be the smallest interface possible.
The idea behind the Principle of Interface Segregation is that if the code implements an interface then it should use everything in the interface and the code should not depend on methods that it does not use or that it should not have access to either.
The solution to this is to keep the interfaces small to minimize interdependence.
SOLID Principles: Dependency Inversion Principle:
The dependency reversal principle consists of two parts.
The first is that high-level modules should not depend on low-level modules; both should depend on abstractions.
The second is that the abstractions must not depend on the details, the details must depend on the abstractions.
MyAndroid is not a downloader online for Principios SOLID. It only allows to test online Principios SOLID with apkid com.alvikapps.thesolidprinciples. MyAndroid provides the official Google Play Store to run Principios SOLID online.
©2024. MyAndroid. All Rights Reserved.
By OffiDocs Group OU – Registry code: 1609791 -VAT number: EE102345621.