In this assignment you will be tasked with building an entire custom view for the game of Draughts. You will be responsible for all drawing, touch interaction, and the ability to customise it.
The game is a two player game played on an 8x8 checkerboard. Each player starts with 12 pieces that can only move and capture diagonally on the board. The objective is to eliminate all the other player’s pieces. Pieces can only move forward up the board until they get to the other side where they are kinged. Kinged pieces can move in all four diagonal directions from there on in.
Once the general custom view is finished you will then integrate it into a UI in the later brackets.
NOTE: that you are also required to show me a working example of your brackets in labs. I will only consider marking those brackets that I’ve seen in labs. If you have only shown me the ftrst four brackets in a lab I will not consider the rest.
Submission and Penalties
You are required to submit two separate components to the Moodle
An archive containing your complete Android Studio Project. The ac- cepted archive formats are: zip, rar, 7z, tar.gz, tar.bz2, tar.xz. The use of any other archive format will incur a 10% penalty before grading.
A PDF containing documentation of your code. If you do not provide documentation your code will not be marked. Copying and pasting code into a PDF does not count as documentation.
There are also a few penalties you should be aware of
Code that fails to compile will incur a 30% penalty before grading. At this stage you have zero excuse to produce non compiling code. I should be able to open your project and be able to compile and run without having to fix syntax errors.
The use of libraries outside the SDK will incur a 20% penalty before grading. You have all you need in the standard SDK. I shouldn’t have to figure out how to install and use an external library to get your app to wor
An omission of a git repository attached to your email address that is registered for GCD will result in your application and documentation not being graded.
The standard late penalties will also apply
You are also required to submit as part of your archive a working Git repository.
When I unpack your archive there should be a .git directory as part of
This should be a fully working git
You are not permitted to upload your work to Github, Gitlab, or any other publicly visible git repository (assignment will be marked as a zero if it is)
If you need a remote git repository the only permitted one is the college provided Gitlab which can be found at gitlab.griffith.ie
There must be a minimum of seven commits in the git repository, one per completed bracket.
Very Important: Take note of the grade brackets listed below. These are meant to be completed in order. If you skip a bracket or do not complete a bracket following brackets will not be considered for mark- ing. You should be well capable of producing strong and generally robust software by now. For example if there are six brackets and you fail the third one, then the fourth, ftfth, and sixth brackets will not be marked. Documentation brackets will be treated separately from Coding brackets.
You should also be aware that I will remove marks for the presence of bugs anywhere in the code and this will incur a deduction of between 1% and 15% depending on the severity. If you have enough of these bugs it is entirely possible that you may not score very many marks overall. I want robust bug free code that also validates all user input to make sure it is sensible in nature.
Also note that the percentage listed after the bracket is the maximum mark you can obtain if you complete that many brackets without error. Everything in all brackets is mandatory.
Be aware that we take plagiarism very seriously here. Plagiarism is where you take someone else’s work and submit it as if it was your own work. There are many different ways plagiarism can happen. I will list a few here (this is not exhaustive):
Finding something similar online (full implementation or tutorial) that does the same job and submit that.
Finding something similar online (full implementation or tutorial) and transcribing (i.e. copying it out by hand)
Working together on an individual assignment and sharing code together such that all implementation look the same.
Getting a copy of someone else’s code and submitting/transcribing that
Doing any of the above and attempting to conceal it by moving function- ality around and renaming functions and variables.
Paying someone to do your assignment
I’ve had to deal with many cases of plagiarism over the last six years so I can spot it and diagnose it easily, so don’t do it. To prevent plagiarism include but not limited to the following:
Do all your code by yourself
Don’t share your code with anyone, particularly if anyone looks for a copy of your code for reference.
If you need to find information online only query about very specific prob- lems you have don’t look for a full assignment or howto.
Be aware that if you submit your assignment you accept that you understand what plagiarism is and that your assignment is not plagiarised in any way.
DescriptionIn this final assignment, the students will demonstrate their ability to apply two ma
Path finding involves finding a path from A to B. Typically we want the path to have certain properties,such as being the shortest or to avoid going t
Develop a program to emulate a purchase transaction at a retail store. Thisprogram will have two classes, a LineItem class and a Transaction class. Th
1 Project 1 Introduction - the SeaPort Project series For this set of projects for the course, we wish to simulate some of the aspects of a number of
1 Project 2 Introduction - the SeaPort Project series For this set of projects for the course, we wish to simulate some of the aspects of a number of