An implementation of the board game Risk to fulfil the project requirements of SOEN6441 at Concordia University, Montréal.

• Programming Language - Java
• Testing Framework - JUnit 4
• Documentation Tool - Javadoc
• Build Tool - Maven
• SCM - git

We follow a model similar to the Model View Controller (MVC) pattern. The design document can be found in the resources folder.

We follow consistent coding standards in our team.

Most standard Java conventions are used. Variables are camel cased and class names are proper singular nouns. Constants are named using capitals and underscores. White space after each declaration and definition is present. A 2-space model is followed for indentation, as defined by Google. Comments are spell-checked and maintained for clarity of code. All code is documented using Javadoc, including private instance members.

We strive for high code quality. To ensure our code stays readable, brief but descriptive names are used for variables and methods. Utility methods are separated modules to ensure reusability and maintainability. We almost always work using Pair Programming to ensure all members are aware of all the sections of the code, as well as having a consensus on the methodology of the code we write.

• SourceForge for src & rules
• Dr.Joey Paquet's - Project Document