Modules in a service program - How many is too many?

I started a different thread as the topic has changed somewhat.

Based on the last two posts to the procedure name vs. production support thread 
and seeing this theme run through the prior posts I'm going to go for the gusto 
and try to get the approval to combine multiple procedure into a module and, if 
I understand correctly, multiple modules into a service program.

The question I have now is where to draw the line on how to do the general 
design.  First some background.  Our applications can be separated into 
different areas; payments, collections, funding, etc.  Should I have a single 
service program for each application area or would there be more than one per 
area?  I presume one for everything is not a good idea.

Even though most of the suggestions from the other thread advocated multiple 
procedures in a single module I wasn't picking up much on multiple modules in a 
service program (probably my thick skull) but that seems to make sense.

Thoughts?

Rick


Privileged and Confidential.  This e-mail, and any attachments there to, is 
intended only for use by the addressee(s) named herein and may contain legally 
privileged or confidential information.  If you have received this e-mail in 
error, please notify me immediately by a return e-mail and delete this e-mail.  
You are hereby notified that any dissemination, distribution or copying of this 
e-mail and/or any attachments thereto, is strictly prohibited.