Specify documentation standards. In the implementation phase the auditor plays a role in specifying system documentation since financial systems must periodically be audited they must be adequately documented the auditor should actively encourage adherence to effective documentation standards.
Verify control adequacy and compliance with sox the AIS application that emerge from the SDLC must possess adequate controls in addition compliance with SOX legislation requires management to certify the existence and effectiveness of those controls during the implementation process the internal audit function plays a key role in these verification and compliance activities.
Post-Implementation Review
One of the most important steps in the implementation stage actually takes place some months later in a post-implementation review the review is conducted by an independent team to measure the success of the system and of the process after the dust has settled although systems professionals strive to produce system that are on budget on time and meet user needs this goal is not always attained the post-implementation review of a newly installed system can provide management with insights into ways to improve the process for future systems it can also provide auditors (both internal and external) with evidence regarding the adequacy of the SDLC in general and the risks associated with a particular system the following are examples of valuable post-implementation evidence.
Systems design adequacy. The physical features of the system should be reviewed to see if they meet user needs. The reviewer should seek answers to the following types of questions
Does the output from the system possess such characteristics of information as relevance timeliness completeness accuracy and so no ?
Is the output in the format most useful and desired by the user( such as tables. Graphs ,electronic ,hard copy , and so no)?
Are the databases accurate complete and accessible?
Were data lost corrupted or duplicated by the conversion process”
Are input forms and screens properly designed and meeting user needs?
Are the users using the system properly?
Does the processing appear to be correct?
Can all program modules be accessed and executed properly or does the user ever get suck in a loop?
Is user documentation accurate complete and easy to follow ?
Does the system provide the user adequate help and tutorials?
Accuracy of time cost and benefit estimates the task of estimating time costs and benefits for a proposed system is complicated by uncertainty this is particularly true for large projects involving