Your comment "so the chip assembly is repeated over and over as pieces are completed or updated" reminds me of my boss's mantra -- "build it early and build it often." We've been doing it that way for almost 20 years.
Considering the tight schedules a chip development usually faces, I think most chip designs follow what you described as Just In Time chip development. Why? Simply because there is never time to develop blocks first and the chip later, and nobody wants surprises at the end -- surprises mean delays.
The final chip assembly and verification processes should be the MOST predictable part of the schedule, because the team has done this several times during the course of the development, and the final iteration that leads to tapeout is just one more turn of the crank.
NASA's Orion Flight Software Production Systems Manager Darrel G. Raines joins Planet Analog Editor Steve Taranovich and Embedded.com Editor Max Maxfield to talk about embedded flight software used in Orion Spacecraft, part of NASA's Mars mission. Live radio show and live chat. Get your questions ready.
Brought to you by