Wednesday, October 24, 2007

3rd Presentation: Bridge Pattern

The last presentation of CSI3303.
6 of us had presented our last design pattern. In the presentation , I had briefly introduce what is bridge pattern and how it is useful to us?

Bridge pattern is a design pattern used in software engineering .The purpose is to divide a complex component into two separate but related inheritance hierarchies. It able to make it easier to change either aspect of the component.

For example , if a user wanted to develop a ToDoList for the Personal Information Manage, a system should be flexible, able to modify and ability to choose.Thus to support this software, it is better to separe the ToDoList representation from its underlying implementation.

Benefits of this approach
Benefits of this approach is apparent when developer add capabilities to the basic behavior.
To add characters or numbering in subclass List.
To support features like grouping items sequentially : extend ListImpl.

In this presentation , one of our classmates had talk about the proxy design pattern. In proxy design pattern , it may be useful if the user have a remote object in a far away area and wants to have access to it. The proxy pattern creates a object locally which represent the remote object . Any communication with the remote object can now talk directly with the local object.There are several type of proxy deisng patterns. They are: virtual proxy, remote proxy, protective proxy and smart proxy.

I had also learn a brief idea on how the JUnit testing works as will as other 3 design patterns. Mr Mok will show us more hands on example and how to run a JUnit testing in the next coming lesson.

No comments: