Chapter 12 MC page 1

Chapter 12 Moving into Implementation

Multiple Choice

1. The fourth phase of the SDLC is the _________ phase

a) Planning
b) Analysis
c) Design
d) Implementation
e) Training

Ans: d
Response: see Introduction
Difficulty: easy

2. Carlos is working on testing and documentation for a new systems project.

What phase of the SDLC is he in?
a) Planning
b) Analysis
c) Interviewing
d) Design
e) Implementation

Ans: e
Response: see Introduction
Difficulty: easy

3. During the implementation phase of the SDLC:

a) Analysts will write programs
b) Programmers will develop user interfaces
c) Project managers will convert logical ERDs into physical DFDs
d) Champions will do the data management design
e) None of the above

Ans: e
Response: see Introduction
Difficulty: medium

4. One of the mistakes of system development is:

a) Thinking that programming is the focal point of systems development
b) Doing a good, thorough job on the analysis phase
c) Building a full and complete set of requirements
d) Creating a user-friendly user interface
e) Adding value to the business

Ans: a
Response: see Introduction
Difficulty: easy

5. Which is NOT an activity of the implementation phase of the SDLC?

Chapter 12 MC page 2

a) Developing the system software

b) Testing the system software
c) Installing the new system
d) Creating the data storage design
e) Selection of the most suitable conversion approach

Ans: d
Response: see Introduction
Difficulty: hard

6. The largest single component of any systems development project in terms of

both time and cost could be:
a) Conducting JAD sessions
b) Gamma testing
c) Developing the user interface
d) Writing programs
e) Having meetings

Ans: d
Response: see Introduction
Difficulty: medium

7. Which is generally the best understood component of the SDLC and may offer
the fewest problems?
a) Developing the database design
b) Developing the systems software
c) Writing onscreen documentation
d) Changing the data into third normal form
e) Doing interviews

Ans: b
Response: see Introduction
Difficulty: medium

8. One of the best books on managing projects (and was written in 1975) is:
a) The Magic Mountain by Thomas Mann
b) Working Overtime by Thomas Watson
c) The Mythical Man-Month by Frederick P. Brooks Jr.
d) The Musical Project by Alan Dennis
e) Windows: The Microsoft Story by Bill Gates

Ans: c
Response: see Managing the Programming Process
Difficulty: hard

9. Normally, analysts will be working on _________ while the programmers are

writing code.
a) Developing specifications for the enhancements to the system that were not
able to included in this version
b) Creating various kinds of tests
Chapter 12 MC page 3

c) Putting together the system prototype

d) Filing materials into a system binder
e) Trick question the analysts will be working hand-in-hand with programmers
on writing the code

Ans: b
Response: see Introduction
Difficulty: hard

10.According to the textbook, which of the following is not a cause of project

failure?
a) Flaws in analysis
b) Flaws in aesthetics
c) Flaws in user interface design
d) Flaws in database design
e) Flaws in developing correct system specifications

Ans: b
Response: see Managing the Programming Process
Difficulty: medium

11.Bridget is managing a systems development project. The programmers have

gotten farther and farther behind in the schedule. One thing she should NOT
do is:
a) Use a code generator that comes with high-end CASE tools
b) Add more programmers to the development team
c) Keep communication channels open
d) Hold weekly meetings
e) Keep close tabs on the process so it doesnt slip farther

Ans: b
Response: see Managing the Programming Process
Difficulty: medium

12.Which is NOT a method of coordinating activities on a development project?

a) Have a weekly project meeting
b) Create and follow standards
c) Keep the programming effort well organized
d) Separate work into three areas: development; testing; production
e) Furnish programmers with coffee, soda and treats to keep morale up

Ans: e
Response: see Managing the Programming Process
Difficulty: hard

13.The process of coordinating a program as it changes through construction

(like keeping files and programs in different places) is called:
a) Change control
b) Separation of duties
c) Judicial control
Chapter 12 MC page 4

d) Scope creep
e) None of the above

Ans: a
Response: see Managing the Programming Process
Difficulty: medium

14. If a program does not pass a test:

a) The analyst will verify that the use-cases were correctly formulated
b) The program is sent back to the development team
c) The project manager will verify that the test was or was not appropriate for
the code being tested
d) The project will be scratched
e) More programming staff will be added to the project
f) The testing methods and test data will be changed

Ans: b
Response: see Managing the Programming Process
Difficulty: hard

15.Frequently, code management systems are used that:

a) Require that modules be checked-in and checked-out from a development
library
b) Verify that the code is in System Standard Form (SSF)
c) Show that physical ERDs have been correctly implemented by the logic
d) Build the code from CASE specifications
e) All of the above

Ans: a
Response: see Managing the Programming Process
Difficulty: hard

16.If a program module is taking longer to develop than expected, the

recommended action is:
a) Put more programmers on the staff
b) Force the developers to work weekends to catch up
c) Move the expected completion date back
d) Incorporate scope creep into the requirements
e) Change the development environment into an object-oriented language

Ans: c
Response: see Managing the Schedule
Difficulty: medium

17.The most common cause of schedule problems during application

development is:
a) Weather related (like hurricanes, tornados, wildfires)
b) Hardware and server incompatibilities
c) Scope creep problems
Chapter 12 MC page 5

d) Switching to different development tools (such as a new version of your

programming language)
e) None of the above

Ans: c
Response: see Managing the Schedule
Difficulty: hard

18.The authors describe writing programs as:

a) A fun, creative activity
b) A tedious process
c) A very mathematical and logical process
d) An excellent learning process for end-users
e) Answers B and C

Ans: a
Response: see Testing
Difficulty: medium

19.A major credit card company has an hour of system downtime on the Friday
after Thanksgiving (generally one of the biggest shopping days of the year).
Which might be a good estimate of the amount of income lost from this
outage?
a) Under $50,000
b) From $50,000 to $99,999
c) From $100,000 to $249,999
d) From $250,000 to $500,000
e) Over $500,000

Ans: e
Response: see Figure 12-1
Difficulty: medium

20. The term bug in software came from:

a) An English translation of the word for defect in German
b) The story of a moth getting caught inside an early computer
c) The acronym BUG for binary unknown glitch
d) No one knows the reason
e) None of the above

Ans: b
Response: see Testing (and footnote about Admiral Grace Hopper)
Difficulty: medium

21.A program is not considered finished until:

a) It has been used successfully for six months
b) The cost of developing the program breaks-even with the benefits of the
program
c) The ROI is positive
d) It has passed its testing
Chapter 12 MC page 6

e) It dies and is replaced by a newer version

Ans: d
Response: see Testing
Difficulty: medium

22.Test plans:
a) Are generally developed by the programmers informally
b) Generally only cover main processing and not the various sub-processes
c) Often have 20 to 30 pages
d) Can be massive with over 200 pages of very explicit plans and directions
e) Can generally be written in three pages or less

Ans: c
Response: see Test Planning

23.On test plans:

a) Each individual test has a specific objective and describes a set of very
specific test cases to examine
b) Each user must contribute to the specific goals of the test plan
c) Each member of the project team, plus all developers (programmers) must
identify one specific application that they will test
d) Only the master project manager tests, and only after all coding has been
completed in what is called the Omega test
e) The use of multiple choice options has been shown to effectively assess to a
99.9% accuracy rate

Ans: a
Response: see Test planning
Difficulty: medium

24.The test objective is taken directly from:

a) The results of the JAD session
b) The program specification
c) The use-cases
d) The project sponsor
e) The questions raised in a focus-group application

Ans: b
Response: see Test Planning
Difficulty: medium

25.The authors suggest that:

a) All testing must include live production data
b) All testing must include both alphabetic and numeric data
c) It is impossible to test every possible combination of input and situation
d) Testing rarely pays for itself
e) Testing should only be used for complex programs and situations

Ans: c
Chapter 12 MC page 7

Response: see Test Planning

Difficulty: medium

26.Especially with interactive forms, testing should:

a) Include batch data processing
b) Omit data validation
c) Include certain combinations of commands or menu choices
d) Only be done by real users with real data on the job
e) None of the above

Ans: c
Response: see Test Planning
Difficulty: hard

27.When testing individual modules, it sometimes happens that some modules

are not finished when testing starts, so the programmer usually writes _______
for the unfinished modules to enable the modules around them to be tested.
a) By-passes
b) Temporary Modules
c) Placeholder Modules
d) Stub Modules
e) End Modules

Ans: d
Response: see Test Planning
Difficulty: medium

28.Bob is starting testing on a complex system that has several modules that
are not finished yet. He has asked the programming staff to create stubs for
the unfinished modules. Which of the following would probably be a good
example of a hardcoded value to be displayed by a stub module?
a) here
b) in uncoded module
c) in the screen output module for exception processing module CRM-
Exception-Processing
d) testing
e) stub module

Ans: c
Response: see Test Planning
Difficulty: easy

29.Which of the following is NOT a general test stage?

a) Unit tests
b) Module tests
c) Integration tests
d) System tests
e) Acceptance tests

Ans: b
Chapter 12 MC page 8

Response: see Test planning

Difficulty: medium

30.Generally, most errors (defects) are found in which two testing periods?
a) Unit testing and integration testing
b) Integration testing and system testing
c) System testing and acceptance testing
d) Unit testing and acceptance testing
e) Alpha testing and beta testing

Ans: b
Response: see Test Planning
Difficulty: medium

31.Unit tests focus on:

a) All modules (all units)
b) Users and their acceptance of how a specific unit works
c) A program or a program module
d) Interact screen forms
e) How the overall system functions

Ans: c
Response: see Unit Tests
Difficulty: medium

32.There are two approaches to unit testing:

a) Alpha and beta
b) Yin and Yang
c) Numerical and alphabetical
d) Valid and invalid
e) Black-box and white-box

Ans: e
Response: see Unit tests
Difficulty: easy

33.Black-box testing:
a) Is reserved for special circumstances in which the tester wants to review the
actual program code
b) Is reserved for NASA space missions
c) Is reserved for very complex systems
d) Is only used by highly skilled testers
e) None of the above

Ans: e
Response: see Unit tests
Difficulty: medium

34.Integration testing:
a) Is to verify that batch processing and online processing both work together
Chapter 12 MC page 9

b) Assesses if a set of modules or programs that are to work together, do so

c) Is a cross between black-box and white-box testing
d) Verifies that client side applications and server side applications do work
together
e) Rarely turns up errors or defects

Ans: b
Response: see Integration Tests
Difficulty: hard

35.Which of the following is NOT an approach to integration testing?

a) Use-case testing
b) User interface testing
c) Use scenario testing
d) Data flow testing
e) System interface testing

Ans: a
Response: see Integration Tests
Difficulty: medium

36.System tests are usually conducted by:

a) Programmers (developers)
b) Project managers
c) Users
d) Systems analysts
e) Project sponsors or project champions

Ans: d
Response: see System Tests
Difficulty: medium

37.As compared to integration testing, system testing:

a) Is much broader in scope
b) Uses production data (rather than test data)
c) Is done by hand-picked end-users (rather than systems analysts)
d) Involves both black-box and red-box testing
e) Makes more extensive use of stubs

Ans: a
Response: see System Tests
Difficulty: medium

38.Integration testing focuses on ___________; while system tests focus on

_______________.
a) Modules working together; meeting business requirements
b) Black-box tests; white-box tests
c) End-users acceptance; project sponsor acceptance
d) DFDs; ERDs
e) Beta tests; alpha tests
Chapter 12 MC page 10

Ans: a
Response: see System Tests
Difficulty: medium

39.Which of the following is probably something that system testing WILL NOT
verify?
a) Systems documentation
b) Ability to perform under heavy load
c) Conformance to Sarbanes-Oxley requirements
d) How well the system meets business requirements
e) The systems usability

Ans: c
Response: see System Tests
Difficulty: medium

40.Acceptance tests are done primarily by:

a) Programmers
b) Users
c) Developers
d) Systems Analysts
e) Project Managers

Ans: b
Response: see Acceptance Tests

41.Paul is a user in the marketing department. He has been selected to help

test a new customer relationship management system. He will probably
perform his testing in which test phase?
a) Unit tests
b) Integration tests
c) Systems tests
d) Acceptance tests
e) Evaluation tests

Ans: d
Response: see Acceptance tests
Difficulty: easy

42.The goal of acceptance testing is:

a) That modules and units work together with each other
b) That the databases are properly organized for both efficiency in storage and
access
c) To confirm that the system is complete and meets the business needs
d) That both black-box and white-box tests have been approved by upper
management
e) To verify that the use-cases, ERDs and DFDs have been properly converted

Ans: c
Chapter 12 MC page 11

Response: see Acceptance Testing

Difficulty: medium

43.Acceptance testing is generally done in two stages:

a) Alpha tests and beta tests
b) Black-box tests and white-box tests
c) Integration tests and systems tests
d) Unit tests and module tests
e) Inductive tests and deductive tests

Ans: a
Response: see Acceptance Testing
Difficulty: medium

44.Because users perceptions of the new system will be significantly influenced

by the experiences in the acceptance tests, analysts should strive for:
a) Colorful screens, carefully laid out following ASCI screen standards
b) Extensive unit and stub testing
c) Complete code walk-throughs with users, programmers, project managers
and project sponsors
d) Fast access to databases and in data retrieval
e) Rigorous and successful system testing

Ans: e
Response: see Acceptance testing
Difficulty: hard

45.As a suggestion to positive acceptance testing, analysts should:

a) Provide incentives to acceptance testing users, such as iPods and iPhones
b) Carefully listen to (and respond quickly and appropriately to) user feedback
c) Intentionally place errors in the code for users to find so they feel valuable
to the team effort
d) Provide program listings with the code to users so they can conduct
appropriate white-box testing
e) All of the above

Ans: b
Response: see Acceptance testing
Difficulty: easy

46.The main difference between alpha testing and beta testing is:
a) In alpha testing, only department managers do testing; in beta testing all end
users do testing
b) In alpha testing, only black-box testing occurs; in beta testing, both black-and
white-box testing occurs
c) In alpha testing, end-users test; in beta testing hand-selected customers join
in on the testing
d) In alpha testing, users test with made-up data; in beta testing users use real
data and carefully monitor the system
Chapter 12 MC page 12

e) In alpha testing, the project team with select end-users test using randomly
generated data; in beta testing, all end-users test with realistic (but made-up)
data

Ans: d
Response: see Acceptance Tests

47.The two fundamental documentation types are:

a) System documentation and integration documentation
b) Screen documentation and batch documentation
c) User documentation and online documentation
d) System documentation and user documentation
e) Acceptance documentation and integration documentation

Ans: d
Response: see Developing Documentation
Difficulty: medium

48.Vrinda is creating user manuals, training manuals, and online help system.
She is probably working on:
a) User documentation
b) System documentation
c) Her dissertation
d) Her masters thesis
e) Acceptance documentation

Ans: a
Response: see Developing Documentation
Difficulty: easy

49.The authors suggest that:

a) Leaving user documentation to the end of a systems project is a good
strategy
b) Good quality documentation takes about 10 hours per screen for online
documentation
c) That documentation can be completed after the system is implemented so
the task is not a part of the critical path of the SDLC
d) Developing good documentation takes longer than many people expect
e) Paper documentation is harder to use since most users are not familiar with it

Ans: d
Response: see Developing Documentation
Difficulty: hard

50.The authors suggest a good time to start the documentation process is:
a) Once the interface design and program specifications are complete
b) Once the system test is complete
c) Once the alpha acceptance test is complete
d) Once the beta acceptance test is complete
Chapter 12 MC page 13

e) Once the logical ERDs and DFDs have been translated into physical ERDs and
DFDs

Ans: a
Response: see Developing Documentation
Difficulty: medium

51.Which of the following is NOT a key strength of online documentation?

a) Searching for information is often simpler (provided a good search index is
provided)
b) The same information can be presented several times in different formats
c) Online documentation allows the user to interact in ways that would be
impossible with paper documentation
d) Online documentation generally is significantly cheaper to produce than
paper documentation
e) It can be bound and printed for reading away from the computer

Ans: e
Response: see Developing Documentation
Difficulty: easy

52.Which of the following is NOT a common type of user documentation?

a) Help systems
b) Reference documents
c) Procedure manuals
d) ERD, DFD, Use-cases and code documents
e) Tutorials

Ans: d
Response: see Types of Documentation (answer d is system documentation)
Difficulty: hard

53.This type of documentation is designed to be used when the user needs to

learn how to perform a specific function (such as updating a field or adding a
new record):
a) Reference documentation
b) Procedures manuals
c) Tutorials
d) Systems documentation
e) Final documentation

Ans: a
Response: see Types of documentation
Difficulty: medium

54.This type of documentation describe how to perform business tasks (such as

printing a monthly report or taking a customers order):
a) Reference documentation
b) Procedures manual
c) Tutorials
Chapter 12 MC page 14

d) Systems documentation
e) Acceptance documentation

Ans: b
Response: see Types of documentation
Difficulty: hard

55.This type of documentation teaches people how to use major components of

the system (like an introduction to the basic operations of the system):
a) Help system
b) Procedures manual
c) Tutorials
d) Systems documentation
e) Acceptance documentation

Ans: c
Response: see Types of documentation
Difficulty: easy

56.Which of the following is NOT a general type of navigation control for help
topics?
a) Table of contents
b) Index
c) Inverted pointer
d) Text search
e) Intelligence agents

Ans: c
Response: see Designing Documentation Structure
Difficulty: medium

57.This particular type of documentation control lists the information in a logical

form, as though the users were to read the reference documentation from
start to finish:
a) Index
b) Text search
c) Content sensitive help
d) Intelligence agents
e) Table of contents

Ans: e
Response: see Designing Documentation Structure
Difficulty: medium

58.When creating the index, which of these will probably NOT be a place to find
terms to include in the index:
a) The set of commands in the user interface (like open file, modify, etc.)
b) The set of user interface design standards (like aesthetics, layout,
consistency, etc.)
Chapter 12 MC page 15

c) The set of major concepts in the system (like in the Tune Source example of
artist, tune, music genre, etc.)
d) The set of business tasks (like ordering, returns, adjustments, etc.)
e) The set of synonyms for other sets (like quit, stop, end for exit or erase
for delete)

Ans: b
Response: see Identifying Navigation Terms
Difficulty: medium

59. An example of a fairly recent enhancement to online help functionality that

uses intelligent agents might be:
a) Table of contents
b) Search function
c) Context sensitive help
d) Index
e) None of the above

Ans: c
Response: See Designing Documentation Structure
Difficulty: very hard

60. The development of all parts of the new system (including programming,
testing, system documentation and user documentation) is generally called:
a) Planning
b) SDLC
c) Waterfall
d) Construction
e) Installation

Ans: d
Response: see Introduction
Difficulty: easy

61.Mya is a programmer on the new inventory tracking system. She looks in the
development library for a module that she needs to modify and changes a
couple of lines in that module. BUT at the same time Steve was also
working on that module - getting it from the library before Mya did and
putting it back in the library after Mya made her changes and saved it. One
common solution to this problem might be:
a) To hold weekly meetings so Mya and Steve could discuss this
b) To have all developers (including Mya and Steve) e-mail all other developers
as they make changes to a module
c) Have a program log / check-out system which would show that the module
was already checked out (in this case to Steve) and that modifications can
not be made until he checks it back in
d) Have all developers call the Project Manager with any and all changes
e) Have a white board in the development area, where a programmer can write
down the modules he/she is working on and ask all developers to check the
white board before making changes
Chapter 12 MC page 16

Ans: c
Response: see Coordinating Activities (c is better than e in terms of a viable
process)
Difficulty: medium

TRUE/FALSE

Chapter 12 True / False questions

62.The final phase of the Systems Development Life Cycle (SDLC) is

Implementation.

Ans: True
Response: see Introduction
Difficulty: easy

63.During the implementation phase of the Systems Development Life Cycle

(SDLC), systems analysts spend their time writing programs and coding
applications.

Ans: False
Response: see Introduction
Difficulty: medium

64.During the implementation phase of the Systems Development Life Cycle

(SDLC), systems analysts will probably be designing tests, working on
documentation, selecting a conversion strategy and implementing the new
system.

Ans: True
Response: see Introduction
Difficulty: easy

65.Even if there were flaws in the analysis and design phases, those can easily
be overcome in the implementation phase.

Ans: False
Response: see Introduction
Difficulty: easy

66.The authors suggest a book on managing programming projects called The

Mythical Mountain written by Roberta Roth.

Ans: False
Response: see Managing the Programming Process
Difficulty: medium

67.If the system being analyzed, designed and developed requires programming
(as compared to a package or outsourcing), developing the software may be
Chapter 12 MC page 17

the single largest component of any systems development activity in terms of

both time and money.

Ans: True
Response: see Introduction
Difficulty: medium

68.During project planning, the project manager identified the programming

tasks and assigned them to systems analysts for programming.

Ans: False
Response: see Managing the Programming Process
Difficulty: easy

69.During program design and again here in the actual programming

coordination, we find that it is best to have modules that overlap and have
high coupling and low cohesion.

Ans: False
Response: see Managing the Programming Process
Difficulty: medium

70.Generally when assigning programming development tasks, the project

manager will analyze skill levels and capabilities of programming staff and
also analyze the modules for complexity and try to match complex modules
to more experienced and skilled programming developers.

Ans: True
Response: see Managing the Programming Process
Difficulty: medium

71.If a mismatch exists between available programming skills and the

programming staff, the best method to solve this is to put more programmers
on the project so that it comes in on time, and within budget!!!!

Ans: False
Response: see Managing the Programming Process
Difficulty: medium

72.An ironic fact of systems development is that the more programmers that are
involved in the development of the system, the longer the project will take.

Ans: True
Response: see Managing the Programming Process
Difficulty: medium

73.Sometimes a project manager can help inexperienced programmers acquire

additional skills through training or through working with more skilled
programmers who serve as mentors.
Chapter 12 MC page 18

Ans: True
Response: see Managing the Programming Process
Difficulty: easy

74. A fairly common approach to keeping development activities coordinated is

to have weekly project meetings.

Ans: True
Response: see Coordinating Activities
Difficulty: easy
75.Over the years (as shown by Fredrick Brooks book The Mythical Man
Month), research has shown that creating and following standards has
actually led to late projects, so the experts advise keeping standards to a
minimum and allowing flexibility as that will give additional employee
satisfaction and faster development.

Ans: False
Response: see Coordinating Activities
Difficulty: easy

76.Many project teams have three areas in which programmers can work: a
development area (or development server); a testing area; and a production
area.

Ans: True
Response: see Coordinating Activities
Difficulty: easy

77.Change control in application development is a formal process for changing

written documentation into online documentation, and frequently uses
specialized cyber documentation agents to create menus, screens and
online user documentation.

Ans: False
Response: see Coordinating Activities
Difficulty: hard

78.If a program module is taking longer to develop than expected, generally the
most appropriate approach is to move the expected completion date back by
the same amount of time that the module will be late.

Ans: True
Response: see Managing the Schedule
Difficulty: easy

79.Adding new requirements to a project after the system design has been
finalized is called requirements creep.
Chapter 12 MC page 19

Ans: False
Response: see Managing the Schedule (scope creep)
Difficulty: medium

80.Charles has been assigned to developing modules CRM_input_web;

CRM_input_validation; CRM_database_retrieval; and CRM_database_update.
He is two weeks behind and is only on the second module. This is definitely a
serious issue and Charles should be reprimanded or even fired for
incompetence.

Ans: False
Response: see Managing the Schedule (comment we dont know enough. Maybe
Charles had a medical emergency and has been in the hospital for those two weeks;
or had a scheduled vacation; or had to do emergency support and maintenance on
modules that have failed in production.)
Difficulty: hard

81.One of the keys to successful project management is to monitor minor

slippages in the schedule.

Ans: True
Response: see Managing the Schedule
Difficulty: easy

82.When creating a project plan, project analysts normally figure out the critical
path.

Ans: True
Response: see Managing the Schedule
Difficulty: medium

83.The critical path is the fine line between the alpha test and the beta test as
you change from test data to real production data.

Ans: False
Response: see Managing the Schedule
Difficulty: medium

84.Frequently a project manager will create a risk assessment that tracks

potential risks along with an evaluation of their likelihood and potential
impact.

Ans: True
Response: see Managing the Schedule
Difficulty: easy

85.Nancy, a project manager, has identified some potential risks with a form
creating package that is being used for the first time. The developer who is
using this form creating package is new to that package, although she has
been with the company for several years and has been recognized for
Chapter 12 MC page 20

outstanding development skills. Nancy should rate this as a high risk and
immediately drop the forms creation package from this project.

Ans: False
Response: see Managing the Schedule (you do need to try some new things and
an experienced, outstanding developer should be able to adapt to using a new
package)
Difficulty: hard

86.By the time the design phase is started, all time estimates should be within
5% of the actual completion time.

Ans: False
Response: see Managing the Schedule
Difficulty: medium

87.Testing is considered as a prized activity on a development project, and

developers (programmers), analysts, and project managers frequently
request being assigned to develop documentation.

Ans: False
Response: see Testing
Difficulty: medium

88.Thorough testing is the hallmark of professional software developers.

Ans: True
Response: see Testing
Difficulty: easy

89.Most professional organizations devote more time and money to testing (and
revision and retesting) that to the original application development
(programming) effort.

Ans: True
Response: see Testing
Difficulty: easy

90.Software bugs are estimated to cost the US economy $12.4 million dollars a
year.

Ans: False
Response: see Testing
Difficulty: hard

91.With some software systems, a day of down-time caused by a software bug

can cost more than several programmers annual salaries.

Ans: True
Chapter 12 MC page 21

Response: see Testing (the text was an hour of downtime can be more than one
years salary, so a day of downtime could be more than several programmers).
Difficulty: hard

92.Testing and programming are tightly coupled.

Ans: True
Response: see Testing
Difficulty: medium

93.Black-box testing is used for normal unit testing

Ans: True
Response: see Testing
Difficulty: easy

94.White-box testing is used when the complexity is high and you want to trace
each path through the programming applications.

Ans: True
Response: see Testing
Difficulty: easy

95. Yuri is a project manager and is creating a test plan. He will want to
complete system testing prior to starting integration testing.

Ans: False
Response: see Testing
Difficulty: easy

96.The normal order for testing is: unit testing, then integration testing, then
system testing, and finally acceptance testing

Ans; True
Response: see Testing
Difficulty: easy

97.Alpha tests come before Beta tests.

Ans: True
Response: see Testing
Difficulty: easy

98. Alpha and beta tests are part of systems testing.

Ans: False
Response: see Testing (they are in acceptance testing)
Difficulty: medium

99. Beta tests make use of real data.

Chapter 12 MC page 22

Ans: True
Response: see Testing
Difficulty: easy

100. Sometimes companies use customers in beta tests.

Ans: True
Response: see Testing
Difficulty: easy

101. Stub testing (if used) occurs in Unit Testing when all of the modules
may not have been fully coded.

Ans: True
Response: see Testing
Difficulty: easy

102. The main difference between integration testing and system testing is
that integration testing looks to see if modules work together without errors;
but system testing is more focused on meeting business requirements.

Ans: True
Response: see System Tests
Difficulty: medium

103. Analysts should not worry about the users perceptions of the new
system during acceptance testing.

Ans: False
Response: see Acceptance tests
Difficulty: medium

104. The two basic types of documentation are: portfolio documentation

and assessment documentation.

Ans: False
Response: see Developing Documentation
Difficulty: medium

105. System documentation takes all the processes, notes, diagrams from
systems analysis and systems design and puts it in a project binder for future
reference.

Ans: True
Response: see Developing Documentation
Difficulty: medium

106. User documentation includes such things as logical ERDs, logical DFDs,
use-cases, physical ERDs, physical DFDs and screen mockups.
Chapter 12 MC page 23

Ans: False
Response: see Developing Documentation
Difficulty: medium

107. User documentation must be developed at the end of the project, after
all programming, testing and approvals have occurred. To do it any earlier
may risk not including changes in the system.

Ans: False
Response: see Developing Documentation
Difficulty: hard

108. Good-quality paper documentation usually takes about 8 hours per

page (double-spaced).

Ans: False
Response: see Developing Documentation
Difficulty: easy

109. Online documentation will probably be the dominant form of user

documentation in the near future.

Ans: True
Response: see Developing Documentation
Difficulty: easy

110. Tutorials teach people how to use major components of the system.

Ans: True
Response: see Types of Documentation
Difficulty: easy

111. When developing navigational controls for online documentation, you

should consider tables of contents, indices, text searches, intelligent agents
(like context sensitive help), and web-like links between systems.

Ans: True
Response: see Types of Documentation
Difficulty: medium

ESSAYS:

112. Stephanie is an analyst for a major credit card company. They are
working on an updated authorizations system that will be in place for the
major holiday shopping season in late November and December. As the
systems beta test, they are planning on trying it out for credit card
customers and businesses in Montana during the second week of June. Is this
a good test plan? Why or why not?
Chapter 12 MC page 24

Ans: From figure 12-1, the estimate for an hour of system downtime for credit card
authorizations downtime is about $2,600,000 (and that data is from April 2000 so
it might be higher now). Testing under realistic situations can be valuable. It is
highly unlikely that the volume of customers in Montana during the
second week of June would be comparable to the volume of all users
during the very busy Christmas shopping season. The company would want
the updated authorizations system to perform under heavy loads, so while this
might be an early beta test, it would not subject the system to the same realistic
loads.

Response: see Testing (and in particular System Tests)

Difficulty: hard

113. Michael is working on online documentation. He has about ten

menu items; twenty items in the index; and wants to have about ten
tutorial pages. How much time should he allocate to developing the
documentation for these items (menus, index and tutorials)?

Ans: From the Developing Documentation materials, we have for good-quality

documentation, this usually takes about [] 2 hours per screen for online
documentation. This would translate into about 80 hours of work (10 + 20 +
10 (=40) * 2 for a total of 80 hours).

Response: see Developing Documentation

Difficulty: medium

114. Christine is a senior user in the online order fulfillment area. Where
would she get involved in the testing process for an updated online order
system?

Ans: Christine would probably been involved in interviews and possibly with use-
cases in the analysis phase. In the testing phase, she might be involved in alpha
testing, but would most likely be involved in beta testing. She should verify that
the business value has been met and that the applications do exactly as
the business requirements specified. She should give any feedback
quickly and directly to the project team so that any modifications can be
made quickly.

Response: see Acceptance tests

Difficulty: medium

115. Myles is a systems analyst on a new project that involves significant

programming. What is Myles doing while the programming is going on?

Ans: Myles should be working on testing and documentation. The main

project manager for this project should be assigning development (programming)
tasks and monitoring so that the project doesnt slip from its expected completion.
As soon as some of the modules are completed, Myles can start testing (possibly
with stub modules); then move into integration, system and acceptance testing.
Likewise, he can be completing documentation tasks.
Chapter 12 MC page 25

Response: see Testing and Developing documentation

Difficulty: medium

116. Bruce is a senior project manager. What activities should he be doing

in the programming / development phase?

Ans: Bruce should be overseeing and coordinating programming activities.

He probably is hosting weekly project meetings, making sure that modules are
progressing as planned. He is also working with other systems analysts to make
sure that the testing plan has been developed and testing is going on; and that
documentation is started. He also wants to make sure that scope creep is not
occurring (or dealing with it), and that the project is on time. If the project does
start to slip, he needs to be on top of the issue and find solutions to get it back on
track or to extend the project time schedule if it cannot be placed back on track.

Response: Managing the Programming Process and the entire chapter

Difficulty: medium

117. The project is very complex and defects (errors / bugs) have been
found during the unit testing and integration test. Finally the project is in the
system testing phase. If you are the project manager, can you relax now?

Ans: NO!!!! Errors / bugs / defect can still show up in the systems testing
and acceptance test phases. And if they do show up, you need to be able to
get them fixed quickly. With a complex system, it may not be until beta testing
when the users get the system that some defects are found.

Response: see Testing

Difficulty: medium

118. What are some classical implementation mistakes and how can you
avoid them?

Ans: (See Practical tip 12-1):

1) Research oriented development using new technologies can delay your
process. It might be good to learn new processes and techniques, but it will
probably slow you down.
2) Using low-cost personnel good people do cost more than others and
probably are worth it!!!
3) Watch code controls make sure that check-out processes are in place and
are enforced. Use a source library.
4) Managing the testing process make sure that testing is thoroughly,
systematically and competently done.
5)
Response: see Practical Tip 12-1
Difficulty: hard

119. Jing is a project manager developing a critical project that MUST be

completed by December 31st. Due to some unforeseen issues early
Chapter 12 MC page 26

on, the project is now two weeks behind and it is mid-November.

What can / should Jing do to get the project finished by December 31 st?
Ans: There are lots of things that Jing can do some of which are generally not
advised. Adding additional programming staff will probably lengthen the
time. If the programming is the bottleneck, it might be good to decompose
complex programs into smaller modules that can be delegated to different
programmers for completion. To watch the time, test plans should be ready as
soon as modules are; users should be prepared to do testing as soon as possible.
Documentation can be done concurrently. If the deadline is an absolute, Jing needs
to make sure that everybody, and everything is kept updated and on target. It
might mean that some of the staff gets only an abbreviated Thanksgiving break or
some people (maybe testing) work during the Christmas to New Years break week.
If any slack could occur, Jing should be exploring all avenues (can the deadline be
extended to January 15th? How fixed is the end date?) to see how best to manage
the project in the time left in the planned schedule.

And if nothing else, this also needs to be a learning experience for the
team so that projects stay on track in the future.

Response: see entire chapter

Difficulty: hard

120. What is the difference between usability testing and performance

testing?

Ans: Usability testing is generally more important for the user-interface,

while performance testing makes sure the desired response time is met.
Some processes that can help might be formal usability testing (see chapter 9) and
ensuring database response time is within expected parameters as detailed in the
original requirements specifications (see chapter 11).

Response: see testing and also review chapters 9 and 11

Difficulty: medium

121. Identify three types of user documentation. Contrast when

each form of documentation should be used.

Ans: There are three types of user documentation: reference documents or

help systems, procedure manuals, and tutorials.

Reference documents or help systems are designed to be used when the

user needs to learn how to perform a specific function, such as updating a
field or adding a new record. Since users may have already attempted to
perform the function prior to reading the reference documentation, it must be
particularly clear and brief.

Procedure manuals describe how to perform a business task such as

printing a monthly report or taking a customer order. Each item in the
procedure manual typically guides the user through a task that requires several
Chapter 12 MC page 27

functions. Procedure manual entries are normally much longer than reference
document entries.

Tutorials teach people how to use major components of the system, such as the
operating system or the accounts receivable system. Tutorial entries are much
longer than procedure manual entries. Tutorials are typically designed to be read in
sequence whereas reference documents and procedure manuals are designed to be
read individually.

Response: See Developing Documentation

Difficulty: hard