Modify Functional Features and Logic | CSSLP Exam Question | Configuration Management Procedures

time, and performs systematic control of changes to the identified attributes.

Answer: C is incorrect.

Configuration audits confirm that the configuration.

Configuration control is a procedure of the Configuration management.

Configuration control is a set of processes and approval stages required to change a configuration item's attributes and to re-baseline them.

It supports the change of the functional and physical attributes of software at various points in identification for a configured item is accurate, complete, and will meet specified program needs.

Configuration audits are broken into functional and physical configuration audits.

They occur either at delivery or at the moment of effecting the change.

A functional configuration audit ensures that functional and performance attributes of a configuration item are achieved, while a physical configuration audit ensures that a configuration item is installed in accordance with every aspect of a configuration item.

A configuration item is a product (hardware and/or software) that has an end-user purpose.

These attributes are recorded in configuration documentation and baselined.

Baselining an attribute forces formal configuration change control processes to be effected in the event that these associated with each configuration item at any moment of time.

It supports the functional and physical attributes of software at various points in time, and performs systematic control of accounting to the identified attributes for the purpose of maintaining software integrity and traceability throughout the software development life cycle.

As a project manager, you are responsible for modifying the functional features and basic logic of the software to ensure that they are compatible with the initial design of the project. To accomplish this task, you will need to follow the procedures of the configuration management. Configuration management is the process of managing and controlling changes to software and other configuration items throughout their lifecycle.

The four main procedures of configuration management are configuration identification, configuration control, configuration status accounting, and configuration audits. Each procedure plays a critical role in ensuring that the software is developed and maintained according to the project's requirements.

Configuration identification involves identifying and labeling all configuration items, including software, documentation, and hardware. This procedure is necessary to ensure that all items are tracked throughout their lifecycle, from development to deployment and maintenance.

Configuration control involves managing and controlling changes to configuration items. This procedure ensures that changes are made in a controlled and systematic way to minimize the impact on the software and to maintain its integrity.

Configuration status accounting involves tracking and reporting the status of all configuration items. This procedure provides visibility into the current state of the software and ensures that all stakeholders are informed of any changes or issues.

Configuration audits involve reviewing and verifying the software and other configuration items against the project's requirements. This procedure ensures that the software meets the project's objectives and that all changes are made according to the project's standards.

In this scenario, to modify the functional features and basic logic of the software and make them compatible with the initial design of the project, you will need to follow the procedure of configuration control. Configuration control will help you manage and control the changes to the software in a systematic and controlled way to ensure that its integrity is maintained and that it remains compatible with the initial design of the project.

Therefore, the correct answer to this question is option B, Configuration control.