Software Patterns, Structural

Question 1

Adapter or Wrapper or Translator.

Answer 1

Convert the interface of a class into another interface clients expect. An adapter lets classes work together that could not otherwise because of incompatible interfaces. 
Wraps an object provide a different interface to it.

Question 2

Bridge

Answer 2

Decouple an abstraction from its implementation allowing the two to vary independently.

Question 3

Composite

Answer 3

Compose objects into tree structures to represent part-whole hierarchies. Composite lets clients treat individual objects and compositions of objects uniformly.
Clients treat collections and individual objects uniformly.

Question 4

Decorator

Answer 4

Attach additional responsibilities to an object dynamically keeping the same interface. Decorators provide a flexible alternative to subclassing for extending functionality.
Wraps an object to provide new behaviors.

Question 5

Facade

Answer 5

Provide a unified interface to a set of interfaces in a subsystem. Facade defines a higher-level interface that makes the subsystem easier to use.

Simplifies the interface of a set of classes.

Question 6

-Flyweight

Answer 6

Use sharing to support large numbers of similar objects efficiently.

Question 7

-Front Controller

Answer 7

The pattern relates to the design of Web applications. It provides a centralized entry point for handling requests.

Question 8

Module

Answer 8

Group several related elements, such as classes, singletons, methods, globally used, into a single conceptual entity.

Question 9

Proxy

Answer 9

Provide a surrogate or placeholder for another object to control access to it.

Question 10

-Twin

Answer 10

Twin allows to model multiple inheritance in programming languages that do not support this feature.