Software-Engineering
August 28, 2024Software-Engineering
August 28, 2024Software-Engineering
|
Question 183
|
In Software Configuration Management (SCM), which of the following is a use-case supported by standard version control systems ?
(a) Managing several versions or releases of a software
(b) Filing bug reports and tracking their progress
(c) Allowing team members to work in parallel
(d) Identifying when and where a regression occurred
(a) Managing several versions or releases of a software
(b) Filing bug reports and tracking their progress
(c) Allowing team members to work in parallel
(d) Identifying when and where a regression occurred
|
Only (a), (c), and (d)
|
|
|
Only (a), (b), and (c)
|
|
|
Only (a), (b), and (d)
|
|
|
Only (b), (c), and (d)
|
Question 183 Explanation:
Software Configuration Management (SCM) is a use-case supported by standard version control systems:
1. Develop the next version of a piece of software while fixing problems with the current one.
2. Share code with other team members in a controlled way, allowing you to develop code in parallel with others and join with the current state of the codeline.
3. Identify what versions of code went into a particular component.
4. Analyze where change happened in the history of a component’s development.
1. Develop the next version of a piece of software while fixing problems with the current one.
2. Share code with other team members in a controlled way, allowing you to develop code in parallel with others and join with the current state of the codeline.
3. Identify what versions of code went into a particular component.
4. Analyze where change happened in the history of a component’s development.
Correct Answer: A
Question 183 Explanation:
Software Configuration Management (SCM) is a use-case supported by standard version control systems:
1. Develop the next version of a piece of software while fixing problems with the current one.
2. Share code with other team members in a controlled way, allowing you to develop code in parallel with others and join with the current state of the codeline.
3. Identify what versions of code went into a particular component.
4. Analyze where change happened in the history of a component’s development.
1. Develop the next version of a piece of software while fixing problems with the current one.
2. Share code with other team members in a controlled way, allowing you to develop code in parallel with others and join with the current state of the codeline.
3. Identify what versions of code went into a particular component.
4. Analyze where change happened in the history of a component’s development.