CHAPTER 7: SOFTWARE DEVELOPMENT
1. The impact of software defects is always trivial.
a. True
b. False
2. Software quality is the degree to which a software product meets the needs of its users.
a. True
b. False
from the very start, or do not take the time to do so.
a. True
b. False
4. When software is well–designed, programmers make no mistakes in turning design specifications into lines of code.
a. True
b. False
5. When forced to choose between adding more user features and doing more testing, most software companies
decide in favor of more testing.
a. True
b. False
6. The first release of a software product typically meets all its users’ expectations.
a. True
b. False
7. Software defects are commonly lethal and many personal injuries are related to software failures.
a. True
b. False
Chapter 7: Software Development
8. Software product litigation first occurred in 2000.
a. True
b. False
9. There is no federal product liability law.
a. True
b. False
left the seller’s possession and the alteration caused the injury.
a. True
b. False
11. Software suppliers attempt to limit their liability by specifying that although software is warranted to run on a
given machine configuration, no assurance is given as to what that software will do.
a. True
b. False
12. A successful defense against a product liability case is typically expensive in terms of legal fees.
a. True
b. False
13. In integration testing, special software programs called static analyzers are run against the new code.
a. True
b. False
14. User acceptance testing is performed by trained end users to ensure that the system operates as they expect.
a. True
b. False
Chapter 7: Software Development
15. Capability Maturity Model Integration (CMMI) is a process improvement approach that defines the
essential elements of effective processes.
a. True
b. False
16. In the context of maturity level distribution across a large sample of organizations, the percentage of organizations
at the initial maturity level is 36.
a. True
b. False
17. When developing safety-critical systems, a key assumption must be that safety will automatically result from
following an organization’s standard development methodology.
a. True
b. False
18. Risk analysis is important for safety-critical systems, but is useful for other kinds of software development as well.
a. True
b. False
19. Software developers do not typically work closely with safety and software engineers.
a. True
b. False
20. In the context of developing safety-critical systems, the safety engineer’s role is limited to producing a hazard log.
a. True
b. False
21. Software quality is defined as the degree to which a software product meets:
a. the needs of its users. b. the standards of its competitors.
c. sustainability and environmental protection needs. d. the minimum financial return standards.
Chapter 7: Software Development
22. Which of the following is true of strategies for engineering quality software?
a. High-quality software systems are tough to learn and use
because they perform slowly.
c. Developers develop high-quality software
instantaneously without a set of principles.
b. Software defects never lead to injury.
d. The first release of any software rarely meets
all its users’ expectations.
23. Which of the following is true of software testing?
a. White–box testing involves viewing the software
unit as a device that has expected input and
output behaviors but whose internal workings
are unknown.
c. Static testing involves software programs called
static analyzers which are run against new code.
b. Black-box testing treats the software unit as a device
that has expected input and output behaviors but
whose internal workings, unlike the unit in whitebox
testing, are known.
d. Integration testing involves independent testing that is
performed by trained end users to ensure that the
system operates as they expect.
24. In the context of Capability Maturity Model Integration, process is ad hoc and chaotic; organization tends
to overcommit and processes are often abandoned during times of crisis in the maturity level.
a. quantitatively managed b. managed
c. defined d. initial
25. Products, such as statements of requirements, flowcharts, and user documentation, are known as .
a. project systems b. information systems
c. objects d. deliverables
26. are defined as a set of interrelated components that include hardware, software, databases, networks,
people, and procedures that collect data, process it, and disseminate the output.
a. Management information systems b. Decision support systems
c. Business information systems d. Data information systems
Chapter 7: Software Development
27. A type of business system is the , which is used to develop accurate forecasts of customer demand,
recommend stocks and bonds for an investment portfolio.
a. upgrade management system
b. decision support system
c. executive information system
d. data information system
28. Process-control computers enable the process to be monitored for variations from operating standards and to
eliminate product defects before they affect product .
a. quality b. delivery
c. testing d. development
29. In one lawsuit in the early , a financial institution became insolvent because defects in a purchased software
application caused errors in several of its systems.
a. 1990s b. 1980s
c. 1970s d. 1960s
30. If the product fails to meet the terms of its written guarantee, the buyer or lessee can sue for .
a. breach of warranty b. comparative negligence
c. contributory negligence d. strict liability
31. means that the defendant is held responsible for injuring another person, regardless of negligence or intent.
a. Contributory negligence b. Misrepresentation
c. Strict liability d. Breach of warranty
32. When sued for , a software supplier is not held responsible for every product defect that causes customer or
third-party loss.
a. breach of warranty b. misrepresentation
c. strict liability d. negligence
33. can be oral, written, or inferred from the seller’s conduct.
a. Indemnity b. Strict liabilities
c. Warranty tolling d. Express warranties
Chapter 7: Software Development
34. Software suppliers frequently write to attempt to limit their liability in the event of nonperformance.
a. manuals b. warnings
c. warranties d. sureties
35. A is a standard, proven work process that enables those involved to make controlled and orderly progress in
developing high-quality software.
a. software guide b. software development methodology
c. software manual d. software project management
36. refers to methods within the development cycle that guarantee reliable operation of the product.
a. Software quality assurance b. Software development methodology
c. Software documentation d. Software project management
37. One approach to quality assurance is to test the code for a completed unit of software by actually entering test data
and comparing the results with the expected results in a process called .
a. dynamic testing b. user acceptance testing
c. integration testing d. static testing
38. involves viewing the software unit as a device that has expected input and output behaviors but whose
internal workings are unknown.
a. Integration testing b. Black-box testing
c. User acceptance testing d. Static testing
39. After successful unit testing, the subsystems are combined to test the entire system as a complete entity using
_____.
a. system testing b. black–box testing
c. integration testing d. static testing
40. After an organization decides to adopt , it must conduct an assessment of its software development practices to
determine where they fit in the capability model.
a. QA b. software development methodology
c. software quality management d. CMMI-DEV
Chapter 7: Software Development
41. In the context of the Capability Maturity Model Integration maturity levels, the percentage of organizations at the
managed maturity level is .
a. 5.8 b. 25.7
c. 38.9 d. 22.1
42. The safety engineer uses a logging and monitoring system to track from a project’s start to its finish.
a. standards b. objectives
c. hazards d. deliverables
43. is the probability of an undesirable event occurring times the probability that the event would go undetected
times the magnitude of the event’s consequences if it does happen.
a. Risk b. Redundancy
c. Liability d. Certainty
44. N-version programming is an approach to minimizing the impact of software errors by independently implementing
the same set of user requirements times, where N could be 2, 3, 4, or more.
a. N+1 b. N
c. N+2 d. N+3
45. A complex system used in IT is a redundant array of independent disks (RAID), which is commonly used in
for file servers.
a. high-volume data storage b. low-volume data storage
c. unpredictable-volume data storage d. irregular-volume data storage
46. is common in airplane and spacecraft control systems.
a. Structured programming b. Triple version programming
c. Object programming d. Root programming
47. In the context of development of safety critical systems, if an undesirable event has a one percent probability of
occurring, a 25 percent chance of going undetected, and a potential cost of $1,000,000, then the risk can be calculated
as .
a. $5000 b. $7000
c. $2500 d. $9500
Chapter 7: Software Development
48. Which of the following is true of the International Organization for Standardization?
a. It is an American organization
founded in 2001.
c. It issued the 9000 series of business
standards in 1987.
b. The ISO 9000:2007 provides a set of standardized requirements
for a quality management system.
d. It is a worldwide federation of national standards bodies from 161
countries.
49. The standard serves many industries and organizations as a guide to quality products, services, and
management.
a. ISO 7498-4 b. ISO 9595/DAM 1
c. ISO 9596 d. ISO 9001
50. is an important technique used to develop ISO 9001-compliant quality systems.
a. DO-178B/EUROCCAE ED–128
b. N–version programming
c. Failure mode and effects analysis (FMEA)
d. Capability Maturity Model Integration (CMMI)
51. A(n) is any error that, if not removed, could cause a software system to fail to meet its users’ needs.
52. focuses on how to define, measure, and refine the quality of the development process and the products
developed during its various stages.
54. As a result of the lack of consistent quality in software, many organizations avoid buying the release of a
major software product.
55. An airline’s online ticket-reservation system and an electronic funds transfer system that moves money among
banks, are examples of .
Chapter 7: Software Development
56. The of software, its usability, and its timely development are critical to almost everything businesses do.
57. Any defect in software can lead to decreased product quality, increased waste and costs, or even unsafe
operating conditions for employees.
59. Defendants in a(n) action may use several legal defenses, including the doctrine of supervening event, the
government contractor defense, and an expired statute of limitations.
60. A(n) assures buyers or lessees that a product meets certain standards of quality.
61. The plaintiff must have a valid contract that the supplier did not fulfill in order to win a(n) claim.
62. If an organization follows widely accepted development methods, on its part is hard to prove.
63. Black–box testing and white-box testing are two forms of .
64. treats the software unit as a device that has expected input and output behaviors but whose internal workings
are known.
65. defines five levels of software development maturity and identifies the issues that are most critical to
software quality and process improvement.
66. In the awarding of software contracts, particularly by the federal government, organizations that bid on a contract
may be required to have adopted and to be performing at a certain level.
67. A(n) is one whose failure may cause human injury or death.
Chapter 7: Software Development
68. A key element of safety-critical systems is , the provision of multiple interchangeable components to perform
a single function in order to cope with failures and errors.
69. After an organization determines all pertinent to a system, it must decide its acceptable level.
70. Poor design between systems and humans can greatly increase risk, sometimes with tragic consequences.
71. What are the standards that the warranty of merchantability requires to be met?
72. Define the five maturity levels of CMMI.
Chapter 7: Software Development
73. Discuss intentional misrepresentation.
74. Discuss the failure of safety-critical software systems through an example.
75. Define reliability.