Consider a typical house in which there are several bedrooms, a kitchen, and a laundry room? Each with a distinct function. You sleep in the bedroom, you wash clothes in the laundry room, and you cook in the kitchen. Each room encapsulates all the items needed to complete the necessary tasks.
What you have is a set of well-defined components: Each provides a single service to communicate with the other components using simple messages when something needs to be done. If you consider a kitchen, you see it is also composed of several, smaller components, including the oven, refrigerator, and microwave. Top-level objects are composed of smaller components that do the actual work. This perspective is a very natural way of looking at our world, and one with which we are all familiar. We do the same thing in object-oriented programming:
See attached file for full problem description.
Here is the reading for this work (not that you would need it )
• Explain some of the graphical user interfaces (GUIs) and communications messages that occur during the operation of a microwave
• Describe some of the advantages of having a componentized system. For example, what happens if the microwave breaks?
Interesting problem. I have attached the solution. There is a part where you will have ...
Interesting problem. I have attached the solution. There is a part where you will have to be imaginative with the graphical part of the top-level description. You can have a head start with the embedded pictures, or you can search for some more in Google images and see which one suits you for depicting a couple of high level objects and communications.