Software Management

A. A single software configuration management team for the whole organization
B. A separate configuration management team for each project
C. Software Configuration Management distributed among the project members
D. All of the mentioned

A. 40-20-40
B. 50-20-30
C. 30-40-30
D. 50-30-20

Explanation: A recommended distribution of effort across the software process is 40% (analysis and design), 20% (coding), and 40% (testing)‏.

A. Baselines
B. Source code
C. Data model
D. None of the mentioned

Explanation: A baseline is analogous to the kitchen doors in the restaurant. Before a software configuration item becomes a baseline, change may be made quickly and informally.

A. Change control
B. Version control
C. SCIs
D. None of the mentioned

Explanation: Configuration management allows a user to specify alternative configurations of the software system through the selection of appropriate versions.

A. System building
B. Release management
C. Change management
D. Version management

A. Configuration item identification
B. Risk management
C. Release management
D. Branch management

Explanation: Risk management is an entirely different domain.

A. Software configuration audit
B. Software configuration management
C. Baseline
D. None of the mentioned

A. Tracking of change proposals
B. Storing versions of system components
C. Tracking the releases of system versions to customers
D. None of the mentioned

Explanation: All the options are tracked

A. ISO 9000
B. CMM
C. CMMI
D. All of the mentioned

Explanation: It is defined in all the mentioned options.

A. Codeline
B. Configuration control
C. Version
D. Workspace

Explanation: In configuration control changes are managed and all versions of components are identified and stored for the lifetime.