Chapter 7 reviews several techniques for testing application control if audit evidence shows that computer applications process data correctly and accurately the auditor can form the basis for reducing the amount of substantive testing that needs to be performed since that client organization could however have hundreds of financially significant applications testing application controls can prove to be a highly technical and time-consuming activity auditors therefore seek efficient and effective way to limit the application testing.
The systems development and maintenance process is common to all applications.
A properly functioning systems development process ensures that only needed applications
Are created that they are properly specified that they possess adequate control and that they are thoroughly tested before being implemented the systems maintenance process ensures that only legitimate changes are made to applications and that such changes are also tested before being implemented together these processes establish the accuracy of new applications and preserve their integrity throughout the period under review
If the auditor can verify that these processes are effectively controlled he or she can limit the extent of application testing that needs to be done if however audit evidence shows SDLC controls
To be weak and inconsistently applied application testing and substantive testing cannot be reduced in some situations it may even be necessary to expand the scope of the audit with this perspective in place let’s now examine the controls audit objectives and audit procedures related to these important processes.
Controlling new systems development
The first five controllable activities discussed next deal with the authorization develop ment and implementation of the original system the last two controllable activities pertain to system maintenance procedures.
Systems authorization activities
All systems must be properly authorized to ensure their justification and feasibility as with all material transactions authorizing the development of a new information system should be a formal step in the process typically this requires that each new system request be submitted in writing by users to systems professionals who have both the expertise and authority to evaluate and approve(or reject) the request
User specification activities
Users must be actively involved in the system development process their involvement should not be stifled because the proposed system is technically complex regardless of the technology involved the user can and should provide a detailed written description of the logical need that must be satisfied by the system the creation of a user specification document often involves the joint efforts of the user and systems professionals however it is most important that this document remain a statement of user need it should describe the user’s view of the problem not that of the systems professionals.
Technical design activities