From: Tarik Nesh-Nash (tarikn_at_microsoft.com)
Date: Wed Jan 07 2004 - 10:36:17 PST
This paper describes the structure of an operating system THE from a
high level prospective, and argues how its hierarchical structure was
important to enable good testing.
The paper is easy reading and the style was not very formal. Since I do
not have experience on these papers, I would like to know if there is a
formal standard for publications or it can be any open style.
The content was not very technical, it seems that the target audience
was broad (The author mentions that the system design field is
underestimated in his country and hence little understood).
It is interesting to see that the paper focus on the testing and
verification, though it can be discussed that the testing effort is not
very advanced. Even if the author claims that "the resulting system is
guaranteed to be flawless", the described testing methodology is not
very convincing.
The design experience was divided into three stages: conception,
construction and verification. I would be expecting more details about
the conclusions drawn on the conception phase and the process of
"reasoning art" learning. Also, the construction phase was not well
detailed, yet I would expect some important overlap between the three
phases.
This document gives a good historical reference to compare the OS field
progress in the late 40 years.
This archive was generated by hypermail 2.1.6 : Wed Jan 07 2004 - 10:39:01 PST