Chapter 22: Systems Design, Implementation, and Operation

Question 1

conceptual design specifications

Answer 1

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

Question 2

conceptual systems design report

Answer 2

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

Question 3

scheduled report

Answer 3

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

Question 4

special-purpose analysis report

Answer 4

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

Question 5

triggered exception report

Answer 5

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

Question 6

demand report

Answer 6

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

Question 7

structured programming

Answer 7

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

Question 8

debugging

Answer 8

the process of discovering and eliminating program errors

Question 9

program maintenance

Answer 9

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

Question 10

physical systems design report

Answer 10

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

Question 11

systems implementation

Answer 11

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

Question 12

implementation plan

Answer 12

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

Question 13

walk-through

Answer 13

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

Question 14

processing test data

Answer 14

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

Question 15

acceptance test

Answer 15

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

Question 16

conversion

Answer 16

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

Question 17

direct conversion

Answer 17

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

Question 18

parallel conversion

Answer 18

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

Question 19

phase-in conversion

Answer 19

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

Question 20

pilot conversion

Answer 20

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

Question 21

postimplementation review

Answer 21

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

Question 22

postimplementation review report

Answer 22

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