With "bug speaks a certain thing to prerequisite"
the star person of the micro wear

Now when as for the star person concerning the selection criteria of OS, "product life cycle becomes short from with this embedded type product, to the time - the market shouts, how it can merchandise the intended product quickly, the importance than something. It should seriously consider short-term development than efficiency. And, it speaks with the selection of OS "that development period is influenced largely.

The same person lists the cause development period of the product having increased. Complicates the program longer by the fact that complicated application has increased, says that there are times when thing and the project management where time is required for debugging become difficult. Furthermore, you say that development not overtaking the industry standard standard due to the various middleware and the appearance etc. of protocol, technician insufficiency and the like has become problem.

These problems are cleared, or or in order from first to try not to occur, the same person have assumed that the selection of OS is important.

The star person listed process model and the thread model as one taxonomic method when OS is selected.

Process model furthermore, OS-9 and Windows CE (V3.x), real-time Operating System and UNIX and Linux, Windows 95/98/Me of Lynx and the like, WindowsNT/2000 and Windows CE (V2.x) and the like divides into non real-time Operating System.

On the one hand, there is iTRON and VxWorks and pSOS etc. which are real-time Operating System in the thread model.

The same person exists, with process model application such as kernel and process becoming independent, while programming we assume that local variable becomes the basis. The thread model being something where the kernel and the driver and task etc. operate with one big object, says that global variable becomes the basis.

Because of this, when with process model, error occurs when program execution certain one, only the process which has become error knocks down, but, you say that with the thread model the possibility the whole system knocking down is high.

The star person, being small-sized, when high speed we would like to construct the system, OS of the thread model is good, but, the product which does scalable development and being large-scale, we have assumed that it should adopt the process model which can construct the complex system.

The same person introduced also the example which developed the same functional program making use of OS which differs. In case of OS of the A corporation, we have assumed that at the B corporation with same 19 it became also total 1386 line, vis-a-vis being total 335 line with A4 paper 5.
As for development technique with RAD

In addition, the same person assume that RAD (Rapid Application Development) it is desirable to actualize, in regard to the development technique which divides into the hardware and the software.

Until recently with opening departure, the test of the software and in order to debug, it did not wait for the fact that the hardware is completed and the ? did not become, you say that wasteful time occurred. Furthermore, when obstacle occurs, the time which is carved whether cause software side or hardware side catches.

On the one hand, you say that with RAD development technique, it places the software in the "reference board", separates from the hardware and tests the software. Because of this, having designed and while developing the hardware, when the test and the bug taking of the software is possible, the hardware is completed, it can move to the last test simultaneously. Because it can develop the software and the hardware with simultaneous advance, you say that progress circumstance of project can be improved substantially.

In order to actualize RAD, various API are defined to detail, we have assumed that thing and the software which thing and the driver and the application which the system design of loose coupling does are separated completely it is required that it is designed in such a way that it can reuse as the part and the like.
As for bug you think certain ones,

In addition as for the same person, idea of the whole project, it designates that it is not bug as prerequisite as for "the Fault avoidance" empty and bug you think the thing which occurs, it should convert to "Fault tolerance" also you speak. When the program becomes long, in addition to the fact that time bets on debugging, it is difficult, to lose bug completely, you say that the coordinating point of bug evasion exists statistically. The same person, at the point in time when the program exceeds 16000 lines, error density (the number of errors per 1000 lines) exceeds 0.5, calls this the coordinating point of bug evasion. In other words, as for the program which exceeds 16000 lines, assuming that it converted lastly, completely without bug as for doing it is difficult reason.