Software Management

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

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

Explanation: It involves approving those changes that are worthwhile, and tracking which components in the system have been changed.

A. Agile method
B. Parallel compilation method
C. Large systems method
D. All of the mentioned

Explanation: In keeg with the agile methods notion of making many small changes, continuous integration involves rebuilding the mainline frequently, after small source code changes have been made.

A. Version and release identification
B. Build script generation
C. Project support
D. Change history recording

Explanation: All other options are a part of version management

A. Minimal recompilation
B. Documentation generation
C. Storage management
D. Reporting

Explanation: To reduce the storage space required by multiple versions of components that differ only slightly, version management systems usually provide storage management facilities.

A. Design & Test specification
B. Source code
C. Log information
D. All of the mentioned

Explanation: A configuration item is an approved and accepted deliverable, changes have to be made through formal procedure.

A. System building
B. Mainline
C. Software Configuration Item(SCI)
D. None of the mentioned

A. Version
B. Codeline
C. Baseline
D. None of the mentioned

A. electronic and paper documentation describing the system
B. packaging and associated publicity that have been designed for that release
C. an installation program that is used to help install the system on target hardware
D. all of the mentioned

Explanation: Release creation is the process of creating the collection of files and documentation that includes all of the components of the system release.

A. Branching
B. Merging
C. Codeline
D. Mainline

Explanation: The code may then be developed independently.