Discussion Locked

Control of End-User Computing

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

At our company, we have sophisicated users who at times will develop and roll-out end-user computing solutions (Access D/B's etc).
One concern of mine is the control of these and co-ordination of this aspect of Information Systems. We (MIS) have been bit aready by having a mission critical application software where the original source (Access .mdb file are missing) only have .mde files. Question: Is there a white-paper on the aspect of computing control.

5 replies

by diabetic

Hi Rich;

This probably won't directly answer your question (and no points are expected -- but I feel a need to share).

I think what you need to develop are a pair of custom procedures that will help you get everything documented correctly.

First: a change control policy that dictates what can be done to a server, who can add programs or applications, who must be notified when such as change is planned, the responsibilities for verifying that the planned change will work and not bring the whole thing down. etc. Depending upon the size of your enterprize, you may even want to have a test server configured where all changes have to get tested before they are implemented.

Second: you need to have an RFS (Request for Service) process where by someone wishing to use new applications, or to roll out new applications have to get the new stuff approved by a knowledgeable group of people (standing committee) and that full copies of source code are properly archived, etc. this process also makes sure that the new apps do not install any older DLLs that can mess up the computing environment.

Shoot me an e-mail at anon999888@hotmail.com and I will send you a sample of each.

Humbly submitted,
diabetic

This discussion is closed to new replies.