Which design pattern (singleton, adapter, factory, observer) is NOT applicable here and why? Mention two reasons.
Consider the following scenario:
Imagine that you're creating a toys management application. The first version of yoursystem can only build car toys, so the bulk of your code lives inside the Car class. After a while, your system becomes pretty popular. Each day you receive dozens of requests for supplying Car toys as well as new one like Duck toy.Great news, right? But how about the code? At present, most of your code is coupled to the Car class. Adding Duck toy into the system would require making changes to the entire codebase. Moreover, if later you decide to add another type of toy to the system,you will probably need to make all of these changes again.As a result, you will end up with pretty nasty code, riddled with conditionals that switchthe system's behavior depending on the class of toy objects.
Which design pattern (singleton, adapter, factory, observer) is NOT applicable here and why? Mention two reasons.
Step by step
Solved in 2 steps
