ch24

Direct conversion

changing from an old to a new system by terminating the old when the new is introduced

Conceptual design specifications

requirement specifications for systems output, data storage, input, processing procedures, and operations

Scheduled report

report prepared on a regular basis, with a pre-specified content and format

Acceptance test

using real transactions to determine if user-developed acceptance criteria are met

Postimplementation review

review of new systems after operating for a brief period to ensure it meets planned objectives and review system controls.

Processing test data

processing valid and erroneous transactions to see if a program operates as designed and errors are detected and corrected

Pilot conversion

implementing a new system in one location, resolving its problems, and then implementing it in the rest of the org

Program maintenance

updating a computer program due to changed user needs, fixing bugs, or legal or regulatory changes

Structured programming

modular programming approach; each module performs specific functions and is coordinated by a control module

Postimplementation review report

report that analyzes a newly added system to determine if it achieved its intended purpose

Demand report

report with a pre-specified content and format, prepared only on requests

Parallel conversion

changing from an old to a new system by operating both simultaneously until confident that the new system functions correctly

Walk-throughs

step-by-step reviews of program logic to find incorrect logic, errors, omissions, or other problems

Physical systems design report

summarizes what was accomplished in physical design; used to determine whether to proceed to implementation

Phase-in conversion

gradually replacing elements in an old system with new elements until the old system is replaced

Triggered exception report

report with pre-specified content and format, prepared in response to abnormal conditions

Systems implementation

process of installing hardware and software and getting the IS up and running

Special purpose analysis report

report with no pre-specified content, format, or pre-specified schedule; usually prepared at management's request

Implementation plan

written plan showing how the new system will be implemented and when the project is complete and the IS operational

Debugging

process of discovering and eliminating program errors.