View this PageEdit this PageAttachments to this PageHistory of this PageHomeRecent ChangesSearch the SwikiHelp Guide
Hotspots: Admin Pages | Turn-in Site |
Current Links: Cases Final Project Summer 2007

Discussion 2 - Joung-Goo Lee

Part 1 - How does choice of language affect the use of design patterns?

High level language reduces errors and makes users easy by showing them essential interface only and object oriented language reduces maintaining fee by making the bond weak among the objects. For those reasons, object oriented language changed the design pattern to more understandable and available for class design. For example, we have to call repair professional to change the monitor if the lines, which we can find when we remove the cover of a cable, are connected from CPU to monitor. However, we can change the monitor easily because it is a line that is connected by a module cable. Therefore, using object oriented language makes “flexible” design patterns possible other than machine language or assembly language.

Part 2 - Describe an Interesting Pattern.

I will describe Abstract Factory Design Pattern. Abstract Factory Design Pattern is a kind of Creational Pattern that helps to create a class, which has same or similar interface form. For example, when we define a class “sea” and create its inheritances as “Pacific Ocean”, “Atlantic Ocean”, and “Indian Ocean”, we call the class that helps those inheritances as “Abstract Factory”.
Here is another example. In case of making a racing car, there are many objects divided like V-8 (engine type), Carbon fiber (body type), and Wet condition (tire type). When we embody those above, the Abstract Factory Pattern is very useful because it coordinates interface, so we do not need to care of the parts in programming. What we need to is do programming with interface. If we do not use this pattern, we would make hard coding that over issues “if statement” If we do not use this pattern.

Link to this Page