Answer:
The cost of change typically increases linearly as a project progresses in a conventional software process.
Explanation:
This means that as more changes are made later in the project timeline, the cost associated with those changes tends to increase proportionally.
The cost of change in a conventional software process increases exponentially as the project progresses. This rise in cost is due to factors like communication overhead and the complexity of later-stage modifications, consistent with Brooks' Law and the nature of exponential growth as opposed to linear growth.
The cost of change increases exponentially as a project progresses in a conventional software process. When changes are made late in the development cycle, the complexity and costs associated with making those changes are much higher than if the same changes were made earlier in the process. This phenomenon can be partly explained by Brooks' Law, which states that adding manpower to a late software project makes it later, due to the increase in communication overhead among team members. Similarly, the cost implications of change can be seen in the context of economies of scale and network externalities, where the addition of more users to a system can significantly alter the value and costs associated with that system.
In terms of software development processes, introducing changes to a project already in an advanced stage can lead to a cascade of modifications that require rework and additional testing. This results in costs that rise more steeply than just a straight line - which would represent linear growth. Moreover, with the fast pace of technological advancement, such as that forecasted by Moore's Law, the cost of not adapting quickly can also be high, potentially leading to loss of market share or the need for more radical and costly overhauls later.
