resources:diagrams:projects:generic:development_view:SOLID

Summary

SOLID Development PatternsSingleResponsibility\PrincipleOpenClosePrincipleLiskov'sSubstitionPrincipleInterfaceSegragationPrincipleDependencyInversionPrincipleAn object should haveone and only one reasonto change, meaningthat a class shouldhave only one job.Objects should beopen for extension,but closed formodification.Code to the mostabstractrepresentation(ie, a base class).clients should notbe forced to implement/useinterface/methodsthey do not require.Entities must dependon abstractions noton concretions.(JGI).