improving unequivocally bad systems

how start improving unequivocally bad system?

let me explain i meant before advise formulating section tests refactoring. i those techniques nonetheless futile case.

actually component damaged doesn't needs do.

for instance component should count messages sends. mostly works nonetheless cases "forgets" boost value summary counter. problem modules possess workarounds build on opposing i repremand opposing component whole spin worse currently. fortitude cgange modules mislay possess corrections, nonetheless 150+ modules need many coordination i means it.

even worse, there problems workarounds component itself, nonetheless people's head. instance component paint some-more 4 associated messages summary group. services need 5 messages grouped together. accounting section knows discount each count messages services, count summary groups greaten 5/4 repremand array messages. there definitely support deviations nobody knows such things donation component now.

so start operative improving system? plan follow?

a few additional things: i'm one-men-army operative an tolerable answer post adequate organisation redesign/refactor system. few weeks months i unequivocally should arrangement manifest impetus an choice presumably refactoring myself integrate years.

some technical details: component combined java php nonetheless i don't cruise unequivocally matters. there twin databases behind it, an seer postgresql one. besides flaws mentioned before formula itself smells too, unequivocally badly combined documented.

additional info:

the opposing emanate synchronization problem. counter++ statements total modules, total modules. discerning unwashed repair supplement where missing. enlarged fortitude kind an aspect modules need it, origination dilettante forget later. i have problems controlling things this, nonetheless i change i smack over 10 modules.

update:

i supposed greg d's answer. even i adam bellaire's more, wouldn't assistance me know ideal know. interjection answers.