<< Chapter 9: Ten Pounds in a Five Pound Sack The hypothesis: Amid a wash of paper, a small number of documents become critical pivots around which every project’s management revolves. These are the manager’s chief personal tools Documents for a Computer Product (Hardware) Objectives defines the need to be met and the goals, the [...]
<< Chapter 8: Calling the Shot Programming Space as Cost The system designer puts part of his total hardware resource into resident-program memory when he thinks that it will do more for the user in that form than as adders, disks, etc. No one can criticize a programming system for size per se and at [...]
Chapter 7: Why Did the Towers of Babel Fall? How does one estimate? Recall that back in Chapter 2 we developed the following ratio: 1/3 planning 1/6 coding 1/4 component test & early systems test 1/4 system test, all components in hand It would be a mistake to estimate the coding first and then develop [...]
<< Chapter 6: Passing the Word For those unfamiliar with the story of the Tower of Babel, read about it here: http://en.wikipedia.org/wiki/Tower_of_Babel A Management Audit of the Tower of Babel First of all, did the project have the following: A clear mission? Yes, even though it was impossible to do Manpower? Yup Materials? Clay and [...]
<< Chapter 5 – The Second-System Effect Written Specifications – The Manual The manual is the external specification of the product, and it is the chief product of the architect The manual must not only describe everything the user does see, including interfaces; it must also refrain from describing what the user does not see. [...]