As an IS auditor, which documents should you verify for Systems Development Methodology? State briefly.

In most companies Systems Development is badly handled and proper documentation is not maintained. The code is developed in great hurry and control aspects are given the go by. The accuracy of the processing and the legal compliance are left as open questions. The IS auditor should verify whether following documents exist or not: System Scope Document. Functional Requirement Specifications. Software Requirement Specifications or Request for Proposal. Design Description or Functional Specification Document. Customization Register. Software code. Test Plan. Unit test results. Integration test results. Acceptance test results. The documentation should be properly cross-indexed. The effect of a change made in the system should be well understood. It should not happen that, due to ignorance of the entirety of the business process and its ramifications, a change made in one area affects other areas, that too after a lapse of time. Every time a change is made, a thorough testing should be done and documented. The IS Auditor should get necessary evidence and comment on the lack of proper adherence to procedure.