Karteikarten
Design patterns
Karten in diesem Stapel (10)
- 1SingletonEnsure that there is just one object of a certain kind, potentially accessible from everywhere
- 2The need to abstract away from the construction of an object or family of objects from the place they are neededFactory method, abstract factory, builder
- 3Factory methodDefine an interface for creating an object, but let sub classes decide which class to instantiate
- 4Abstract methodProvide an interface for creating families of related or dependent objects without specifying their concrete classes
- 5BuilderSeparate the construction of complex objects from its representation so that the same construction process can create different representations
- 6Some objects are expensive to create or tied to OS resources that need to be carefully managedObject pool, use a set of initialized objects in a pool rather than allocating and destroying on demand
- 7Propagate updates from one object to all interested parties, without coupling all objects togetherObserver, define a one-to-many dependency between objects so that when one object changes state, all its dependencies are notified and updated automatically
- 8Convert the interface of a class into another interface which classes expectAdapter
- 9Decouple an abstraction from its implementation so that the two can vary independentlyBridge
- 10Big 4Pattern name, the problem, the solution, consequences
Informationen
- Beschreibung
- Information Technology Karteikarten am Design patterns, erstellt von Johan Isaksson am 19/10/2018.
- Erstellt von
- Johan Isaksson
- Aufrufe
- 5
- Bewertung