Multiple Choice
Ans: d
Response: see Introduction
Difficulty: easy
Ans: e
Response: see Introduction
Difficulty: easy
Ans: e
Response: see Introduction
Difficulty: medium
Ans: a
Response: see Introduction
Difficulty: easy
Ans: d
Response: see Introduction
Difficulty: hard
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
Ans: b
Response: see Introduction
Difficulty: hard
Ans: b
Response: see Managing the Programming Process
Difficulty: medium
Ans: b
Response: see Managing the Programming Process
Difficulty: medium
Ans: e
Response: see Managing the Programming Process
Difficulty: hard
d) Scope creep
e) None of the above
Ans: a
Response: see Managing the Programming Process
Difficulty: medium
Ans: b
Response: see Managing the Programming Process
Difficulty: hard
Ans: a
Response: see Managing the Programming Process
Difficulty: hard
Ans: c
Response: see Managing the Schedule
Difficulty: medium
Ans: c
Response: see Managing the Schedule
Difficulty: hard
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
Ans: b
Response: see Testing (and footnote about Admiral Grace Hopper)
Difficulty: medium
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
Ans: a
Response: see Test planning
Difficulty: medium
Ans: b
Response: see Test Planning
Difficulty: medium
Ans: c
Chapter 12 MC page 7
Ans: c
Response: see Test Planning
Difficulty: hard
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
Ans: b
Chapter 12 MC page 8
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
Ans: c
Response: see Unit Tests
Difficulty: medium
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
Ans: b
Response: see Integration Tests
Difficulty: hard
Ans: a
Response: see Integration Tests
Difficulty: medium
Ans: d
Response: see System Tests
Difficulty: medium
Ans: a
Response: see System Tests
Difficulty: medium
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
Ans: b
Response: see Acceptance Tests
Ans: d
Response: see Acceptance tests
Difficulty: easy
Ans: c
Chapter 12 MC page 11
Ans: a
Response: see Acceptance Testing
Difficulty: medium
Ans: e
Response: see Acceptance testing
Difficulty: hard
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
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
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
Ans: e
Response: see Developing Documentation
Difficulty: easy
Ans: d
Response: see Types of Documentation (answer d is system documentation)
Difficulty: hard
Ans: a
Response: see Types of documentation
Difficulty: medium
d) Systems documentation
e) Acceptance documentation
Ans: b
Response: see Types of documentation
Difficulty: hard
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
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
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
Ans: True
Response: see Introduction
Difficulty: easy
Ans: False
Response: see Introduction
Difficulty: medium
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
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
Ans: True
Response: see Introduction
Difficulty: medium
Ans: False
Response: see Managing the Programming Process
Difficulty: easy
Ans: False
Response: see Managing the Programming Process
Difficulty: medium
Ans: True
Response: see Managing the Programming Process
Difficulty: medium
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
Ans: True
Response: see Managing the Programming Process
Difficulty: easy
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
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
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
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
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
Ans: False
Response: see Testing
Difficulty: medium
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
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
Ans: True
Response: see Testing
Difficulty: medium
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
Ans: True
Response: see Testing
Difficulty: easy
Ans: False
Response: see Testing (they are in acceptance testing)
Difficulty: medium
Ans: True
Response: see Testing
Difficulty: easy
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
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
Ans: False
Response: see Developing Documentation
Difficulty: easy
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
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.
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.
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.
118. What are some classical implementation mistakes and how can you
avoid them?
And if nothing else, this also needs to be a learning experience for the
team so that projects stay on track in the future.
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.