73 the main purpose of configuration management is to

Info iconThis preview shows pages 6–9. Sign up to view the full content.

View Full Document Right Arrow Icon
73 The main purpose of configuration management is to A. Require cost justification for any change in a software product. B. Require approval for any desired change in a software product. C. Maintain a detailed record of changes for the lifetime of a software product. D. Provide the customer with a process for requesting configuration changes. Answer: C See Chapter 5. Configuration management produces a highly detailed record, including details of each and every copy of a software product that was created. 74 Configuration management can include an approval-based check- in/check-out mechanism to ensure that
Background image of page 6

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
A. Developers won’t make unapproved changes to software. B. All changes have been tested. C. All changes have been approved. D. All changes have been verified. Answer: A See Chapter 5. A check-in/check-out mechanism in configuration management prevents the developers from making unauthorized and undocumented improvements. 75 The Software Engineering Institute Capability Maturity Model is a measure of A. Advancements in software capabilities B. The technical capabilities of software C. The maturity of an organization’s software development processes D. The ability of a software product to remain accurate, even after many years Answer: C See Chapter 4. The Software Engineering Institute Capability Maturity Model (SEI CMM) is a measure of an organization’s software development process. 76 An applet that combines functionality from external applications through their APIs is known as: A. Mashup B. Washup C. ActiveX D. Agent Answer: A See Chapter 5. A mashup is an applet that combines functionality from one or more external applications. For example, Google Maps is often used in mashups to show locations on a web site. 77 Which of the following is NOT a goal of the Software Capability Maturity Model? A. Reduced development time B. Improved development tools C. Improved software quality D. Improved planning Answer: B See Chapter 5. The SCMM has little, if anything, to do with development tools, but the other answers are some of its objectives.
Background image of page 7
78 The top-most level in the Software Capability Maturity Model has to do with A. Continuous and institutionalized process improvement B. Complete lack of processes and controls C. Fully normalized and optimized software D. Fully tested and validated software Answer: A See Chapter 5. The highest order of existence in the SCMM is a model of continuous process improvement. 79 The purpose of a Build List is A. To obtain approval at the detailed design step of the software life cycle B. To ensure that the compiler includes all necessary components during a build C. To ensure that all the necessary components are present during a build D. To record the versions of all components of each copy of a product Answer: D See Chapter 5. The Build List is a part of configuration management that records all the component versions for each build of the product. 80
Background image of page 8

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Image of page 9
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}

Page6 / 13

73 The main purpose of configuration management is to A...

This preview shows document pages 6 - 9. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online