V.11 Risks

The following risks have been identified at the beginning of the project (December 2010). They influenced the planning of the first three iterations significantly. Since the completion of the third iteration, the risks are mastered. This architectural overview shows the risks, including the former eventuality planning, because of their large impact on the solution.

11.1 Risk: Connecting to a Frontend

There is no knowledge about connecting an engine to an existing chess frontend. Available open source engines are programmed in C and are delivered as executable programs (*.exe). Since DokChess is developed in Java, they are of limited use as examples. Nothing is known in the project about chess communication protocols.

If it is not possible to make a working connection, the solution cannot be used with existing frontends. This not only lacks an important feature (refer V.1.1 Requirements Overview), but also makes the solution as a whole, especially as a case study, untrustworthy.

Eventuality...