Which artifacts are typically controlled by configuration management?

Which artifacts are typically controlled by configuration management?

• A. Baselines, requirements, design documents, code.
• B. Personal emails and calendars.
• C. Marketing collateral.
• D. Training materials.

Answer: (A)

Configuration management focuses on controlling the items that define the product’s identity at any point in its life cycle. The artifacts typically managed are baselines, requirements, design documents, and the code itself. Baselines provide fixed reference points for a release, while requirements specify what the system must do, design documents describe how it will be built, and the code embodies the actual implementation. Configuration management tracks revisions, maintains an audit trail, and ensures you can reproduce a specific build from a given baseline. Personal emails, calendars, marketing collateral, and training materials aren’t configuration items for product development, so they aren’t typically controlled by configuration management.

Configuration management focuses on controlling the items that define the product’s identity at any point in its life cycle. The artifacts typically managed are baselines, requirements, design documents, and the code itself. Baselines provide fixed reference points for a release, while requirements specify what the system must do, design documents describe how it will be built, and the code embodies the actual implementation. Configuration management tracks revisions, maintains an audit trail, and ensures you can reproduce a specific build from a given baseline. Personal emails, calendars, marketing collateral, and training materials aren’t configuration items for product development, so they aren’t typically controlled by configuration management.