D**C
发帖数: 6754 | 1 设计一个 client/server的chess game
你们有啥想法,主要是偏OO设计 | c*********e
发帖数: 16335 | 2 mac里的围棋不错，windows里面咋不整一个？
【在 D**C 的大作中提到】
: 设计一个 client/server的chess game
: 你们有啥想法,主要是偏OO设计
| D**C
发帖数: 6754 | 3 文不对题啊
【在 c*********e 的大作中提到】
: mac里的围棋不错，windows里面咋不整一个？
| s******e
发帖数: 493 | 4 Trying to start with a simple and commonly used use case for the scenario.
Do not try to cover too much for the first round. You can always add more
when it is needed.
Once you have a clear picture on the requirements/use case, you need to
focus on either system design or OOD depending on the position you apply for.
For an architect position, I think you should focus on system design and
mention that each tier itself need to be designed using ood. In your case, I
think it would be common that client uses ria, and server needs to handle
some internet protocol. The other questions jump out of my mind are what is
the communication topology between clients (piont-point, or server based
with push), what ria technology you want to choose, what kind of clients you
want to support (web, desktop, or mobile), etc.
for a developer position, you might need to define the components, classes
and their relationships based on your use case for each tier of client and
server. To do that, you might still need to do some kind of system design,
for example, dividing the responsibilities between client and server. Trying
to make your class/component cohesive and loosely coupled. At many times,
designing with event will be more impressive rather than with a mediator
pattern. Finally, using UML to convoy your thoughts. Most likely class and
component diagram should be sufficient. |
|
