Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
11 Cards in this Set
- Front
- Back
|
Single Responsibility Principle |
A class should have one reason and only one reason to change. That is the class shouldnt have more than one responsibilities |
|
|
Open Closed Principle |
Open for extension, Closed for modification |
|
|
Liskov Substitution Principal |
States that objects of a superclass should be replaceable with objects of the superclass without breaking the application |
|
|
Integration Segregation Principle |
Clients should not be forced to depend on interfaces that they do not use. The goal of ISP is to reduce the side effects and frequence of required changes by splitting the software into multiple independent parts |
|
|
Dependency Inversion |
High level modules should not depend on low level modues. Both should depend on abstraction. Abstraction should not depend on details. Details should depend on abstractions. Combinations of open close and liskov principle |
|
|
Flyweight Design Pattern |
Used to form large object structures across many disparate objects. (Structural) |
|
|
Adapter Design Pattern |
Lets classes work together that couldnt otherwise because of incompatible interfaces (Structural) |
|
|
Facade Design Pattern |
Defines a higher level interface that makes the subsystem easier to use (Structural) |
|
|
Proxy Design Pattern |
Allows for object level access across control by acting a pass through entity or placeholder object (Structural) |
|
|
Mediator Design Pattern |
Promotes loose coupling by keeping objects from referring to each other explicity (Behavioural) |
|
|
State Design Pattern |
Allows and object to alter behaviour when the state changes(Behavioural) |
