survayy (it's not a typo)

A surveys processor

Architecture and additional information

Uncle Bob's clean architecture because it's something I've already worked with and have experienced first-hand the speed boost in development it offers in the mid to long-term.
Uncle Bob's rules for TDD (red, green, refactor) for the most part.
Split my code into two main packages: core and application. The idea behind this is to provide an easy way to separate them into two projects in the future.
Tried to keep things as extensible as possible by not tying any features to any particular implementation (only care about the interfaces).

Results from unsubmitted surveys should not be considered in the rating questions average
Think of a name/signature for SurveyGateway method getSurveyFromRawData(Object rawData) that makes more sense
Ignore pojo packages in coverage
Refactor CLISurveyGateway getter/setter methods
Separate core from application