Standard Development Life Cycle
Standard Procedures
 |
| |
 |
| |
 |
| |
 |
| |
 |
| |
 |
| |
 |
| |
 |
| |
 |
| |
 |
Implementation Phase
In this phase your ready to “Go Live”. You need to have all your turnover documents ready.
There should be time built into the schedule for your Production Control folks to implement all
the programs and files. Let them give you an estimate of how long this will take and plan
accordingly.
Training is part of the Implementation phase but this is usually done before go live. It can’t be
too much earlier than the implementation for all the bugs need to be worked out first in the
Testing Phase.
Memos should go out the department heads with notification of the implementation.
As part of the turnover you need to provide documentation. Included in the documentation
should be the backup and recovery procedures.
Set up security according to responsibility of the users of the new system. Assign a security
profile to the responsible parties. Backups for individuals may be needed to cover anyone off
site at the time of need.
Generally user authority is given to the level of responsibility. Software may or may not have
field level security or application level security but user’s responsibilities will dictate how that
security will be set.
There will be times a special user profile will be needed. One to be used by the application
support team. It should only be available on an emergency basis. Set up some kind of system
to have that profile assigned only after the problem has been officially reported. Logging of
the problem and solution should be recorded. Not only for the history but as a requirement of
the auditors.
Scheduling of Batch Jobs - Once again like the production turnover documents, account for the
time needed of Production Control. Turn in the documentation of the jobs needed to run in
batch mode. Separate updating jobs from reporting jobs. After the Update jobs run, backup the
results for recovery purposes.
These jobs may need a special calendar to determine when to run particular jobs. So also keep
this in mind.
Update and validate all the control tables used with the new system. Execute the onetime
programs to load the migration data for your new system.
After all is implemented, back up all the data, run all your test scripts to be sure the
implementation was successful. After all goes well, restore to the backup.
There is continuing support that will be needed for a couple of months. Making sure all daily,
weekly, and monthly schedules run successfully.
You may think this was the last phase in the Standard Development Life Cycle but there is one
more. The Post Implementation Review.
Benefits of the Implementation Phase.
There should be time built into the schedule for your Production Control folks to implement all
the programs and files. Let them give you an estimate of how long this will take and plan
accordingly.
Training is part of the Implementation phase but this is usually done before go live. It can’t be
too much earlier than the implementation for all the bugs need to be worked out first in the
Testing Phase.
Memos should go out the department heads with notification of the implementation.
As part of the turnover you need to provide documentation. Included in the documentation
should be the backup and recovery procedures.
Set up security according to responsibility of the users of the new system. Assign a security
profile to the responsible parties. Backups for individuals may be needed to cover anyone off
site at the time of need.
Generally user authority is given to the level of responsibility. Software may or may not have
field level security or application level security but user’s responsibilities will dictate how that
security will be set.
There will be times a special user profile will be needed. One to be used by the application
support team. It should only be available on an emergency basis. Set up some kind of system
to have that profile assigned only after the problem has been officially reported. Logging of
the problem and solution should be recorded. Not only for the history but as a requirement of
the auditors.
Scheduling of Batch Jobs - Once again like the production turnover documents, account for the
time needed of Production Control. Turn in the documentation of the jobs needed to run in
batch mode. Separate updating jobs from reporting jobs. After the Update jobs run, backup the
results for recovery purposes.
These jobs may need a special calendar to determine when to run particular jobs. So also keep
this in mind.
Update and validate all the control tables used with the new system. Execute the onetime
programs to load the migration data for your new system.
After all is implemented, back up all the data, run all your test scripts to be sure the
implementation was successful. After all goes well, restore to the backup.
There is continuing support that will be needed for a couple of months. Making sure all daily,
weekly, and monthly schedules run successfully.
You may think this was the last phase in the Standard Development Life Cycle but there is one
more. The Post Implementation Review.
Benefits of the Implementation Phase.
- Production Ready
- All communication has been done
- All Training is complete
