microsoft uses frequent comprehensive prototypes in its deve

microsoft uses frequent comprehensive prototypes in its development of software. In factm in some projects there is a \'daily build\', in which a new version of products or could it be used for physical products is intergreated and compiled everyday. Is the approach only viable for software products, or could it be used for physical products as well? what might be costs and benfits of such approach for physical products?

Solution

Software products are basically virtual entities. So minor changes (e.g., fixing of bugs, small modifications etc) in the code and creating an executable versions for some projects on daily basis (called daily build) or weekly basis (called as weekly build) does not involve much costs or manpower.

But when it comes to physical entities, any changes in design or manufacturing process (including tools, dies, zigs, fixture etc) involves huge amount of costs. So any changes on daily basis is almost impossible to incur in the project. That is why utmost care is taken before the design and the manufacturing processes are decided for the final design, so that to get the final product in minimum iterations.

So the benfits in such cases would be very little which is basically monitoring the desired functioning on daily basis and any abnormality in functioning can be rectified.

But the cost involves is huge, which includes cost due to changes in design, cost in manufacturing processes, material cost, tool cost, die cost, jigs and fixture cost, cost due to changes in assembly line, also sometimes it includes cost in training human resources.