Assignment 1
Due Friday by 18:00 Points 25 Submitting a file upload File types zip
Available 26 Jul at 9:00 - 7 Sep at 18:00 about 1 month
COSC2391/2401 A1 S2 2019
Criteria Ratings Pts
Submit Assignment
FP_Assignment1_sem2_2019.pdf
CoinGame.zip
The .pdf contains the written assignment specification and the .zip contains supporting source code
(interfaces) and JavaDoc documentation generated from the interface comments. To view the
javadoc simply load index.html in the doc/ folder in a web browser. The project also contains an
example console output trace (OutputTrace.pdf).
For submission you need to submit your full eclipse project. This can be done by right clicking the
project and selecting Export ... (General -> Archive File).
You are allowed multiple submissions however only the final one will be marked.
Standard RMIT Late penalty of 10% per day (of full marks i.e. 2.5/25) applies (to a maximum of 5
days after which late assignments can no longer be accepted).
!
Functional Correctness
Marking Functional Correctness
involves the marker running a test
client which runs a series of known
tests against your submissions. The
following will be tested:
Add/Remove Players; Refuse an
illegal bet; Place a valid bet; Coin
and CoinPair behaviour (including
equals()/hashCode() functionality);
Unmodifiable Collection; Spin Coins
(Delay, Result, Sequence, Callback
number and sequencing); Spin
Coins a Second Time (to test
GameEngine state handling);
applyBetResults() produces correct
outcome based on result and
BetType (table 1 in spec); After
marking you will be supplied with an
13.0 to >11.0 Pts
Exemplary
Code
successfully
passes all tests
according to the
requirements
specified in the
assignment
documentation
with correct
output, no errors,
or exceptions.
11.0 to >9.0 Pts
Developing
Code passes
majority of tests
according to the
requirements
specified in the
assignment
documentation
and where it fails
it is able to
produce partial
output and
continue
executing.
9.0 to >6.5 Pts
Pass
Code is able to
compile and run
(perhaps with
some minor
modification by
the marker) but
fails some tests,
produces
erroneous output
or functionality
that does not
match the
requirements or
throws
exceptions.
6.5 to >0 Pts
Fail
Code will not
compile or
cannot
execute to
provide any
meaningful
testing of
functionality
OR only a
small subset
of
functionality
is correctly
implemented.
13.0 pts
4.0 pts
3.5 pts
output log of the tests to help you
fix any errors that are detected
during evaluation.
Structural Adherence to
Specification
Submission makes appropriate use
of the provided classes and
interfaces. Code passes Validator.jar
checks. Compilation and execution
test with external code. (e.g. our
GEI and GEC) Output is formatted
according to spec/OutputTrace.txt
4.0 to >3.5 Pts
Exemplary
All methods in
the interfaces
have been
implemented
without
modification as
specified. All
implementation
classes are
accessed
through
provided
interfaces.
3.5 to >3.0 Pts
Developing
Most methods in
the interfaces
have been
implemented
without
modification as
specified.
Implementation
classes are mostly
accessed through
provided
interfaces. Only
minor errors,
occasional
casting/misnaming
etc.
3.0 to >2.0 Pts
Pass
Significant
changes have
been made to the
provided
interfaces/classes.
Exceptions, or
compile errors
present when
testing with
external client
code. Partial
automated testing
is still possible or
can be evaluated
manually.
2.0 to >0 Pts
Fail
Code does
not follow the
specification.
An ad-hoc
approach has
been taken
and/or no or
minimal code
has been
added to the
supplied
framework.
Encapsulation and OO Principles
Constrained variable scope,
information hiding, modularity, code
reuse.
3.5 to >3.0 Pts
Exemplary
Fields are
appropriately
encapsulated,
suitable use of OO
techniques to
remove code
duplication, no
unnecessary/global
variables.
Appropriate use of
types and visibility
3.0 to >2.5 Pts
Developing
Generally well
encapsulated
but minor
errors with
visibility, minor
code
duplication
and/or
inappropriate
use of
types/casting.
2.5 to >1.75 Pts
Pass
Clear evidence
of copy and
paste code
reuse,
unnecessary
variables, global
variables and
high visibility.
Lack of
appropriate
getters and
1.75 to >0 Pts
Fail
No obvious
encapsulation.
Code structure
appears
random or is
poorly
planned.
Total points: 25.0
3.5 pts
1.0 pts
0.0 pts
0.0 pts
modifiers. setters and
parameter
passing.
Coupling and Cohesion
Goal: High Cohesion (Classes have
a precise, clear well defined
function). Low Coupling (classes
only interact with other modules as
necessary to perform a clear
function).
3.5 to >3.0 Pts
Exemplary
The source code
is highly cohesive
and has low
coupling. Classes
and methods are
succinct and
have a clear
separation of
concerns.
Dependencies
are well managed
and only occur
where necessary
to achieve a
specific goal or
interaction.
3.0 to >2.5 Pts
Developing
Generally high
cohesion and
low coupling but
minor cases
where code
structure could
be improved by
splitting
methods/classes
and removing
unnecessary
dependencies.
2.5 to >1.75 Pts
Pass
Some effort has
been made to
increase
cohesion and
lower coupling
but there are
clear problems
with large
uncohesive
classes or
methods with
high complexity
that would
benefit from
decomposition.
1.75 to >0 Pts
Fail
There is no
obvious
structure to
the code and
modules
appear to be
randomly
grouped with
little
consideration
given to
maintainability,
reusability and
extensibility.
Source Code Quality
Importable Eclipse Project,
Appropriate class, method and
variable names, meaningful
commenting, easily
comprehensible, no warnings,
appropriate formatting
1.0 to >0.85 Pts
Exemplary
The quality
criteria have been
consistently and
fully applied in
the project
0.85 to >0.75 Pts
Developing
The quality
criteria have been
mostly applied in
the project
0.75 to >0.5 Pts
Pass
The quality
criteria have
been
inconstantly or
partially applied
in the project
0.5 to >0 Pts
Fail
The quality
criteria have
mostly not
been applied
in the project
Deductions
See comments if deduction has
been applied.
0.0 Pts
No description
0.0 Pts
No description
Late Penalty
If applicable late penalty of 10%
(2.5 marks) per day applied here.
0.0 Pts
No description
0.0 Pts
No description