Chapter 22: Systems Design, Implementation, and Operation Flashcards Preview

Accounting Information Systems > Chapter 22: Systems Design, Implementation, and Operation > Flashcards

Flashcards in Chapter 22: Systems Design, Implementation, and Operation Deck (22)
Loading flashcards...
1

conceptual design specifications

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

2

conceptual systems design report

summarizes conceptual design activities, guides physical design activities, communicates how all information needs will be met, and helps the steering committee assess feasibility

3

scheduled report

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

4

special-purpose analysis report

report with no pre-specified content, format, or pre-specified schedule; usually prepared in response to a management request

5

triggered exception report

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

6

demand report

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

7

structured programming

a modular approach to programming in which each module performs a specific function and is coordinated by a control module

8

debugging

the process of discovering and eliminating program errors

9

program maintenance

updating a computer program due to changed user needs, fixing bugs, legal or regulatory changes, or to make use of new technology

10

physical systems design report

summarizes what was accomplished in physical design; used to determine whether or not to proceed to the implementation phase

11

systems implementation

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

12

implementation plan

a written plan showing how the new system will be implemented; specifies when the project should be complete and the IS operational, including a completion timetable, cost estimates, task milestones, and who is responsible for each activity

13

walk-through

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

14

processing test data

processing valid and erroneous transactions to determine if a program operates as designed and that valid transactions are handled properly and errors are detected and dealt with appropriately

15

acceptance test

test of a new system using real transactions to determine if user-developed acceptance criteria are met

16

conversion

the process of changing from an old computer system or format to a new one

17

direct conversion

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

18

parallel conversion

changing from an old system to a new one by operating both systems simultaneously until the organization is confident the new system is functioning correctly

19

phase-in conversion

changing from an old to a new system by gradually replacing elements of the old with the new until the old system has been entirely replaced

20

pilot conversion

changing from an old to a new system by implementing a system in one location, using it until all problems are resolved, and then implementing it in the rest of the organization

21

postimplementation review

review made after a new system has been operating for a brief period to ensure that the new system is meeting its planned objectives, identify the adequacy of system standards, and review system controls

22

postimplementation review report

a report that analyzes a newly delivered system to determine if the system achieved its intended purpose and was completed within budget