# Group 53 (The Herd)

## Risk List for Assignment One

### Version 1

A1 | A2 | A3 | Risk | Risk Resolultion Progress | Created by/on | Last updated by/on
1 |  |  | Unsure of what database platform will be best to use. Research orientated development risk New Risk: JDBC - need to get drivers. | Jon will investigate Resolved: MYSQL will be used. | Jon 17Mar03 | Jon 17Mar03
2 |  |  | RMI (Remote Method Invocation)- not sure how to draw up UML (or design classes) until we can work out how RMI interacts with/calls classes. (silver bullet syndrome risk) New Risk: XML encoding - need to develop test classes. | All of us will study RMI and Jon will write a small piece of code to demonstrate it's use. Resolved: Not using RMI - uning XML encoding of serrialised objects. Jon Still to write code. | Paul 17Mar03 | Paul 17Mar03
3 |  |  | Feature Creep - We keep adding cool stuff to the game | Andrew will tell Jon to shut up everytime he says "But it would be cool" | Jon 23Mar03 | Jon 23Mar03
4 |  |  | Not sure if all SRS is done correctly (for example - not sure what classic mistakes to match these risks up with). | Jon will review our SRS against the checklist. Resolved | Andrew 18Mar03 | Andrew 18Mar03
5 |  |  | Security - even though this is just for entertainment, ideally we should be certain that no client can conprimise the system integrity. Ideally cheating (accidental or mallicious) should be prevented, and the server should be secure. | Paul will do some reasearch on security using Java. | Danny 5Mar03 | Danny 5Mar03