CHECKLIST FOR PLANNING SOFTWARE SYSTEM PRODUCTION
prepared in August 1966 by
R.W. Bemer
1. TOOLING
Is the first prototype or pilot of each hardware unit assigned (in sufficient quantity) to software production for a sufficient and continuing period of time?
Are these hardware units periodically updated and rotated to customers so that software production has up-to-date and complete equipment?
Is this hardware under the firm control of software production so as to be free of interference due to hardware test modification, confiscation for customers, etc.?
Is this hardware operated in a customer-like environment to reflect and anticipate customer needs before distribution to the field?
Is there sales representative service and field engineering service for the software systems equivalent to that for any other customer?
Is sufficient research undertaken in software production methods, such as construction languages and bootstrap methods?
Are the software production methods of other manufacturers studied if known, and sought out if unknown?
Is the manufacturer’s most powerful computer used for controlled production, distribution and maintenance of software systems for all of his machine systems?
Is there a computerized system for software field reporting?
Is there a computerized system for-software production control?
Is there a computerized system for automated software production?
Is there a computerized system for a customer roster, together with their hardware and software configurations?
Is this roster integral with the corresponding roster for manufacturing, projects and field engineering?
Does this roster contain the hardware field change level which could affect software or system performance?
Is there a software facility for file maintenance of source programs?
Is a general assembler provided which can assemble, using the tool machine, for any new machine?
Is there a tool for proving the identity of the general assembler to the specific assembler for the specific machine?
Are simulators provided for the tool machine which can simulate any new machine for which software is being constructed?
Are these simulators in a form suitable for any period of scarcity, such as early testing by customers?
Does the software production system have provision for
a) Updating the test library with additional quality assurance programs and suitable excerpts from the field reports.
b) Updating the roster.
c) Modifying itself.