Database Reference
In-Depth Information
holding meetings with your end users and developing a prioritized list of
changes and additions that they want you to make. Occasionally, a change
might come in from a person who is not on the end-user committee. To
handle these requests, system personnel usually make use of a standard
change-request form. This form contains information such as desired
change, reason for change, screen shots of the existing screen that needs to
be changed (if applicable), and more, depending on the organization. Such
changes usually have to authorized by the end user's management before
it is sent to the computer department.
Once the change request comes to the computer department, if it's sim-
ple and there's some spare time, the modification is scheduled immedi-
ately. Usually, however, it is added to a prioritized list of things to do. Once
it reaches the top of the list, the same SDLC steps used during develop-
ment are used during maintenance. In other words, you need to determine
whether the modification is feasible, determine its cost, develop a specifi-
cation, etc.
Training
Once the system is installed, the end users will require some training.
There are various ways to achieve this, which can range from in-house
training to CAI (computer-assisted instruction).
Once the end users are trained, they'll need some support on a day-to-
day basis. First, as already discussed, they'll need a manual so they can
look up answers to questions. Some systems do not use paper manuals.
Instead, everything is embedded in a help file. If the manuals are insuffi-
cient, then the company might want to do what most companies are doing
and fund and staff a help desk. Sometimes people in end-user departments
rely on a person within their department who has become an expert at
using the system. This person is usually referred to as the
resident expert
.
SUMMARY
In this chapter, we reviewed Oracle's developmental tool suites. We then
focused on a broad array of systems-development issues and methodolo-
gies. Just keep in mind that a tool without a robust process is like a car
without an engine.
Search WWH ::
Custom Search