| | |
| C | 1.1 | Explain the reasons for post-implementation reviews and audits for: |
|
|
|
| | - system development |
|
| | - system operation |
|
|
|
| P | 1.2 | Given a fully developed system, prepare a post-implementation review report including as a minimum: |
|
|
|
| | - brief description of the system including its primary purpose |
|
| | - comparison of schedules showing planned versus actual, giving reasons |
|
| | - cost comparisons showing planned versus actual, giving reasons |
|
| | - problems encountered during the project, giving potential solutions |
|
| | - special concerns which should receive attention |
|
|
|
| P | 1.3 | Perform the tasks of the review team which should include: |
|
|
|
| | - user interviews |
|
| | - DP operations personnel interviews (data entry, control, operators and librarians) |
|
| | - examination of small project requests and maintenance requests affecting the system |
|
| | - interviews of programmers who have had responsibility for maintenance/modification since the system was implemented |
|
| | - analysis of production statistics |
|
| | - volume statistics |
|
| | - review of system documentation |
|
|
|
| P | 1.4 | Develop a checklist for a review team carrying out a routine periodic review of performance. This might include: |
|
|
|
| | - review objectives of the DP organisation and specifically the system under investigation |
|
| | - examine the internal organisation of the DP resources |
|
| | - review personnel selection |
|
| | - scrutinise philosophy and processes which made the system possible |
|
| | - examine the training programme of the organisation |
|
| | - review security
|
