TRAINING PROJECT

Java debugging & refactor (Heme Biotech)

Debugging and fixing a Java application for medical needs prediction at Hemebiotech.

Context

Heme Biotech is a pharmaceutical company specializing in blood disorders. Alex, a chemistry researcher, had started a Java symptom-counting program — but all counters returned 0. Mission: fix the bugs, refactor to OOP standards, and document the code for the team to take over.

Bugs Fixed & Refactoring

Root bug: symptom counter always returning 0 — fixed using TreeMap
Alphabetical sort handled automatically by TreeMap's natural ordering
Full OOP refactor: ISymptomReader and ISymptomWriter interfaces
AnalyticsCounter class with getSymptoms, countSymptoms, sortSymptoms, writeSymptoms methods
Separate Main class isolating entry point from business logic
Removed stale comments, applied camelCase naming, added full Javadoc

Best Practices Applied

OOP patterns: interfaces + separate implementations
Javadoc on every public method
Git workflow: dev → main branch, atomic commits per step
Java naming conventions (camelCase) strictly followed
result.out file generated with alphabetically sorted symptoms

Defense Results

2/2

Skills validated

1 critical

Bugs fixed

Classes created

Interfaces

HemeBiotech — Java debugging project

Screenshots