HELP!

This is not strictly an Informix issue, but it does address quality software. I need some ammunition regarding software distribution to multiple (2400) sites. If you know of articles or books relating to the process of controlling software at multiple sites please point me in the right direction. Most books talk about the software process from analysis and design through testing and implementation. But none that I have seen talk about software distribution to multiple sites. Here's what I am getting at. I have a system that is comprise of many individual modules (i.e. a compete accounting package, ordering system, labor management... ) most are interrelate in some way. We have a system of releases (modeled basically from what you would think). We also allow software to be distributed outside of the release system (for emergency fixes or O/S patches ect) we call these 'release independent'. I am getting to the point where every project manager believes his/her project is so important that it can't wait for the scheduled distribution of a particular release, so it ~must~ go out as 'release independence'. I don't want to get into any more detail over the net, but I think you can see where I'm leading too. I already have multiple releases (an unavoidable evil) but I now have "release independent" software creeping into the process. Any opinions anyone might have would also help. Thank You. PS - O.O. is a solution but O.O. must start in the analysis and design phase, not in the implementation phase. We are mainly in maintenance mode, and our software was designed with releases in mind.