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.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.