Info iconThis preview shows page 1. Sign up to view the full content.

View Full Document Right Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: projects • understood by all individuals involved in a project and quality assurance activities • applied throughout all phases of a project KD Reference: _______________________________ ___________________________________________ Whether standard approach to quality assurance prescribes the types of quality assurance activities (and specific reviews, audits, inspections, etc.) to be performed to achieve the objectives of the overall quality plan? KD Reference: _______________________________ ___________________________________________ Whether quality assurance planning prescribes the scope and timing of quality assurance activities? KD Reference: _______________________________ ___________________________________________ Whether quality assurance reviews evaluate general adherence to the IT standards, policies and procedures? KD Reference: _______________________________ ___________________________________________ Whether senior management has defined and implemented IT standards, policies and procedures, including a formal system development life cycle methodology purchased, developed in-house or combination of the two? KD Reference: _______________________________ _ IT Audit Manual Volume III 22 IT Audit Manual No. Item 114 Whether system development life cycle methodology: • governs the process of developing, acquiring, implementing and maintaining computerised information systems and related technology • supports and encourages development/modification efforts that comply with the organisation's and IT long- and shortrange plans • requires a structured development or modification • process with contains checkpoints at key decision points and requires authorisation to proceed with the project at each checkpoint • is complete and current • is capable of being tailored/scaled to accommodate all types of development that is occurring within the organisation • is applicable for both in-house and purchased software creation and maintenance • has documented provisions for technological change • has built in a general framework regarding the acquisition and maintenance of the technology infrastructure • has steps to be followed (such as acquiring; programming, documenting and testing; parameter setting; maintaining and applying fixes) should be governed by, and in line with, the acquisition and maintenance framework for the technology infrastructure • calls for provisions outlining third-party implementer acceptance criteria, handl...
View Full Document

{[ snackBarMessage ]}

Ask a homework question - tutors are online