Software change control-control Cost Overflow _ software Testing

In the original, 51Testing Software Test Network (http://www.51testing.com) ~ Software life cycle, software repair cost pyramid, the more down the cost of modification. The requirements phase found that the cost of change is the smallest, the other from small to large in turn is the design phase, coding phase, the system testing phase to modify the cost of the code. After the proposed project, must increase the demand confirmation link, the demand will certainly change, but we want to manage and control it, let it within a controllable range. 　　For example, Heilongjiang should be in the prototype, finished drawing the flowchart with the user to confirm, so as to reduce our cost exceeded risk. <b "=" "style=" LINE-HEIGHT:18.2PX; Word-wrap:break-word; margin:0px Auto; padding:0px; " 　　> Examples: For example, demand 1 and Demand 2 were developed at the outset, their respective cost is 5 people/day, one-time development is 10 people/day. Since demand 21 did not start, the project team only developed demand 1, after entering the testing phase, found that demand 2 also to develop, at this time, the cost of 2 in accordance with the software engineering theory doubled 5-20 times, the assumption is 5*5=25, then the total cost may be 30 people/days.