A computing system controls many devices the CPU, hard drive, and RAM. Each have

Question

A computing system controls many devices the CPU, hard drive, and RAM. Each have many settings. ie. CPU (set speed, set # of cores, power on power off). Hard Drive (read sector read byte, write sector, write byte, power on, power off), RAM (read byte, write byte power on, power off). A programmer could code against the components directly to put the computer to sleep/hibernate or restore from sleep/hibernate. Instead, an interface is created encapsulating the interfaces to the components so that a programmer can now code to a new interface sleep() and hibernate(). This is an example of creating/using a: A computing system controls many devices the CPU, hard drive, and RAM. Each have many settings. ie. CPU (set speed, set # of cores, power on power off). Hard Drive (read sector, read byte, write sector, write byte, power on, power off), RAM (read byte, write byte power on, power off). A programmer does not like the interface provided by the sub system and wants to integrate the functionality provided into an existing interface so that they may access the functionality polymorphically. The programmer is building a The facade pattern does not promote loose coupling because the client is tightly coupled to the underlying sub classes encapsulated by the interface.

Explanation / Answer

question 1.

answer is facade pattern

question 2

answer is adapter pattern

question 3.

false

1.The façade contain a set of interfaces in a subsystem and also defines a higher-level interface that makes the subsystem easier to use.

2.The subsystems helps to reduce complexity and common design goal is to minimize the   communication and dependencies between subsystems.

3.One way to achieve this goal is to introduce a Façade object and provides a single, simplified interface to the more general facilities of a subsystem.

4. It provide a simplified, improved, or more object-oriented interface to a sub-system that is complex , poory designed, a decayed legacy system consuming it.

5. Façade allows for the reuse of a valuable sub-system without coupling to the specifics of its nature.

6. Subsystems often get more complex as they evolve. Most patterns, when applied, result in more and smaller classes.

7.This makes the subsystem more reusable and easier to customize, and also becomes harder to use for clients that don't need to customize it.

8,.A facade can provide a simple default view of the subsystem that is good enough for most clients. Only clients needing more customizability will need to look beyond the facade.

9.There are many dependencies between clients and the implementation classes of an abstraction. A facade to decouple the subsystem from clients and other subsystems, thereby promoting subsystem independence and portability.

10.Abstract coupling between Subject and Observer is that it has a list of observers, each conforming to the simple interface of the abstract Observer class. The subject doesn't know the concrete class of any observer. Thus the coupling between subjects and observers is abstract and minimal.

Related Questions

Navigate

• Browse (All)
• Browse A
• Subjects

---

---

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.