Software organizations tend to reward programmers who (a) write lots of code and (b) fix lots of bugs. The best way to get ahead in an organization like this is to check in lots of buggy code and fix it all, rather than taking the extra time to get it right in the first place. When you try to fix this problem by penalizing programmers for creating bugs, you create a perverse incentive for them to hide their bugs or not tell the testers about new code they wrote in hopes that fewer bugs will be found. You can't win.
Anyway, that's still not impossible to solve. After the design phase, reward for every module shipped, then deduct points for every bug reported by users. If the programmer is able to hide bugs such that they never manifest in production, I say all power to him.
[Edit]
Oh ok, I think I see what you mean. Well, firstly, if a subsystem weren't integral to the app, why develop it in the first place? Secondly, you could always track the usage of the subsystem and provide additional incentives for its success. Lastly, who says subsystems have to be directly accessible to the user? If tasked to write a module that runs in the background, one can hardly make it deliberately obtuse.