chapter 7

Question 1

Define system life cycle. Stages: Analysis

Answer 1

Design

Question 2

What is a system analyst? IT specialist responsible for entire life cycle of new/modified system.

Question 3

Purpose of analysis stage. Identify requirements

Answer 3

collect data

Question 4

Four methods of analysis. Interviews

Answer 4

Questionnaires

Question 5

Interview advantage. Immediate feedback

Answer 5

follow-up questions

Question 6

Interview disadvantage. Time-consuming

Answer 6

expensive

Question 7

Questionnaire advantage. Quick

Answer 7

inexpensive

Question 8

Questionnaire disadvantage. Low return rate

Answer 8

inflexible questions

Question 9

Observation advantage. Reliable data

Answer 9

overall view

Question 10

Observation disadvantage. People work differently when watched.

Question 11

Document examination advantage. Reveals information other methods miss

Answer 11

see paper system operation.

Question 12

Document examination disadvantage. Time-consuming

Answer 12

expensive

Question 13

What is system specification? Document detailing configuration

Answer 13

performance

Question 14

Design stage purpose. Define system elements: software

Answer 14

interfaces

Question 15

What is file/data structure design? Defines field names

Answer 15

data types

Question 16

Characteristics of good data entry form. Clear heading

Answer 16

space for answers

Question 17

Computer form features. On-screen help

Answer 17

drop-down lists

Question 18

Verification vs. validation. Verification: checking data copied correctly. Validation: checking data meets rules.

Question 19

Two verification methods. Double entry

Answer 19

visual checking.

Question 20

Proofreading definition. Checking spelling/grammar without original document.

Question 21

Types of validation checks. Range

Answer 21

look-up

Question 22

Development: testing data types. Live

Answer 22

Normal

Question 23

Define test strategy. Guidelines explaining how testing will be carried out.

Question 24

Define test plan. Document listing all tests to be performed on the system.

Question 25

Four implementation methods. Direct changeover

Answer 25

Parallel running

Question 26

Direct changeover advantage. Immediate benefits

Answer 26

lower cost.

Question 27

Direct changeover disadvantage. Risky if new system fails

Answer 27

no fallback.

Question 28

Parallel running advantage. Gradual staff training

Answer 28

old system as backup.

Question 29

Parallel running disadvantage. Expensive (double work)

Answer 29

time-consuming.

Question 30

Pilot running advantage. Only one part affected if fails

Answer 30

cheaper training.

Question 31

Pilot running disadvantage. Slow full rollout

Answer 31

miscommunication possible.

Question 32

Phased implementation advantage. Failure only affects latest phase.

Question 33

Phased implementation disadvantage. Expensive and time-consuming per phase.

Question 34

User documentation purpose. Help users learn to use system (how to run

Answer 34

save

Question 35

Technical documentation purpose. Help programmers maintain/modify system (code

Answer 35

flowcharts

Question 36

Evaluation considerations. Compare with original task

Answer 36

identify limitations

Question 37

What is a test for input formats? Checking data entry forms and validation rules work.

Question 38

Why is a test plan created? To ensure thorough testing of all system components.

Question 39

When is parallel running preferred? When system failure would be critical; need backup.

Question 40

What is the main risk of direct changeover? Complete system failure with no backup.

Question 41

When is pilot running used? In large organizations with multiple branches/departments.

Question 42

What does user documentation include? How to run software

Answer 42

save files

Question 43

What does technical documentation include? Program code

Answer 43

flowcharts

Question 44

Why evaluate after implementation? To identify needed improvements and measure success.