Project Feedback
and Evaluation
Dependable Distributed
Middleware Systems
18-749, Spring 2006
Team #: 1
Application:
Su-Del-Ku -- A
real-time, fault-tolerant, high performance game where two or more sudoku
players can pit their intelligence against each other
Middleware + Platform:
JBosss, MySQL, Linux
Team Members: Christopher
Nelson <crnelson@cs.cmu.edu>, Saul Jaspan <saul.jaspan@gmail.com>,
Lucia de Lascurain <ldelascu@andrew.cmu.edu>, Jose Luis Rios Trevino
<jriostre@andrew.cmu.edu>, Yudi Nagata <ynagata@andrew.cmu.edu>
2/11/2006:
Feedback on project proposal
- Good division of
project responsibilities
- Interesting baseline
application (this has not been done before)
- Where are you considering
using asynchronous messages (since you mention that you might need them)?
- You’ve talked
about a server crash not affecting the continuation of the game. What
about the start-up of a new game or the addition of a client to the
game?
- Under the real-time
requirements, you have two separate requirements – client receives
reply in 200ms and game resumes within 2 seconds. Does this mean that
the 200ms applies only in the fault-free case? Also, does the 200ms
apply to ALL clients connected to the game?
- Does a client map
onto a player? You mention the term “player” under the performance
requirements
- You have a lot of
functionality listed in the baseline application features – you might
want to break those up into mandatory and optional features, just to
ensure that enough of the application is implemented and that you don’t
run out of time
Feedback on project
interfaces and end-to-end use case
Final check-off list
Baseline:
Failover:
Exception-handling:
Recovery:
Latency:
Performance:
Test-cases:
Additional features:
Overall comments
Marks