
Java & OOP
Inheritance, interfaces and the design questions behind them.

OOP coursework is marked on design as much as output. A program that works but models the problem as one giant class scores below a cleaner one that does the same thing, because the assignment is testing whether you can decompose. We write to the design brief and keep the UML in step with the code.
What you get
- Class design with a reason for each relationship
- Inheritance versus composition, decided deliberately
- Exception handling that is not an empty catch block
- UML that matches the code you submit
- JUnit tests where the brief asks for them
Related reading


APA 7th Edition
The details that cost marks: capitals, italics, ampersands and DOIs.
Read more →
Discussion Chapter
Where your results stop being numbers and become findings.
Read more →