1. Look at your own Chat Client/Server or another group's Chat client/server design and describe good and bad design characteristics using the criteria in Chapter 9.
Try to find a few examples of cohesion and coupling. Describe what type of cohesion and coupling is present. For coupling, can you think of a way to reduce it?
In my idea , I think , it quit good but have a few bad . In bad . My group don't use
1. Common coupling . (I notice pattern of constructor).
2.Control coupling. : Because I see our code , have link method in some condition (if ) and that method can be group in same class for reducing .
3. I don't have some hook or some method . Another people may be can not use like reusability .
In good .
1. I see own code . It has encapsulate attribute . But it has not grouping that attribute .
2. I see my program using like Dynaming load . Means that use some method in that time . It does not use all own program since strat program .
2. What architecture design pattern is exhibited by AKADNS ?
• I thinks , It likes Broker architecture pattern .
• Because when it type www.google.com it will be www.google.co.th . I think , it will find the near Web Server and use it .
3. For your board game design, what architecture design patterns are present?
If you can't find any architecture design patterns in your board game, then describe at least one architecture design patterns in OCSF.
In my idea , I should The Foctory pattern . Because I can use other class and can pass object by use interface .
Surarit Chaisuntharanon 46540530