| PLEX86 | ||
Was FORTRAN buggy 4341Was FORTRAN buggy 4342 The ECO-FCO (Engineering Change Order-Field Change Order) process was easy. The new parts or modifications... Well,.. In the case of the IBM 360 mod 30, the unifying 360 architecture definition existed. But the architecture was only implemented for that model via emulation on a different micro engine. i.e. no mod 30, 360 hardware, ever existed as such. In the: architecture, implementation, realization, description model of computers, 360 architecture of the mod 30 was implemented via emulation on the ??? micro engine, and the realization was (some family of electronic transistor building blocks technology). In the case of the 1401 emulator on the IBM 360 mod 40 and the 7090 emulator on the IBM 360 mod 50 the computers being emulated did exist as separate independant hardware products. None of these three that I mentioned were preproduction development simulations of a future devices to be implemented and realized in another form. Anyway the development emulators are not meant to be static enbreasties. They are software realizations of the proposed device and as one purpose are used to explore and verify it. Then when a hardware realization of the device is being built they interact with that process to verify its accuracy and if needed to feed back to the device definition stage. Theoretical eg.: The device definition proposes behavior X, The development emulation vets X as logically consistant. But X is physically impossible to accomplish with existing technology. Therefore this result is fed back to the definition stage and the definition gets changed to some alternate Y, which gets vetted by the emulator and turned over to the engineers with the soldering irons. -- Rostyk Rostyk
|
||||
Alt Folklore Computers from Newsgroups The #1 Usenet Provider on the Internet
|
||||