S.O.L.I.D

longlh3009
Mind Map by longlh3009, updated more than 1 year ago
longlh3009
Created by longlh3009 about 6 years ago
8
1

Description

1 Technical Issues Mind Map on S.O.L.I.D, created by longlh3009 on 08/17/2015.

Resource summary

S.O.L.I.D
  1. Single Responsibility Principle (SRP)
    1. A class should have only one reason to change.
    2. Open Close Principle (OCP)
      1. Software entities like classes, modules and functions should be open for extension but closed for modifications
      2. Liskov's Substitution Principle(LSP)
        1. We must make sure that the new derived classes just extend without replacing the functionality of old classes. Derived types must be completely substitutable for their base types.
        2. Interface Segregation Principle (ISP)
          1. Clients should not be forced to depend upon interfaces that they don't use.
          2. Dependency Inversion Principle (DIP)
            1. - High-level modules should not depend on low-level modules. Both should depend on abstractions. - Abstractions should not depend on details. Details should depend on abstractions.
            Show full summary Hide full summary

            Similar

            Software Processes
            Nurul Aiman Abdu
            Software testing strategies: Summary
            harrymt
            Software Application
            Dim Ah
            Diseño de Software
            Verny Fernandez
            Input and Output Devices
            Jess Peason
            GCSE Computer Science (AQA)
            Wolfie Ruth
            2.1.3 Software
            Lavington ICT
            GCSE AQA Computer Science - Definitions
            James Jolliffe
            Hardware, Software and Networking
            dphillips211
            Hardware and Software
            Balikkoftesi