Determine the best design pattern for This system

Question

I want to design a Lights hardware controller that do the following:

1. Have commands that control the lights for the place like turn on, turn off, turn on all lights, turn off all lights.
2. Other operation may be defined in the future such as adding affects or like these operation(which pattern tat help me to add new operation to existing one without polluting the existing system).
3. The controller should support multiple kinds of lights(is adapter a good option here?? any other options??) .
4. The controller have a computer UI in addition to manual control(which is the best pattern for providing interface between the controller and the software UI).

I want to use some design patterns here like (Iterator, Composite, Observer, Facade, Factory, Builder, Template Method, Decorator, Command, Visitor, Proxy, and/or Adapter). I want to know which patterns are best suitable for each and how I can apply them here? And if there if is any example similar to this one?

Answer 1

All this

providing interface between the controller and the software UI

reminds me about the Mediator design pattern. Since it defines simplified communication between classes. Also define an object that encapsulates how a set of objects interact. Mediator promotes loose coupling by keeping objects from referring to each other explicitly, and it lets you vary their interaction independently.

About the

multiple kinds of lights

I think that concept of divergent change will help you greatly. In short through the rest of your list:

1. Command design pattern - encapsulate your commands as an object

2. Builder with Decorator or State

3. Facade for the Controller and Composite for the lights