f) updated and corrected materials as produced
g) actual user programs for interchange?
Does this group maintain the standard software library, including systems from other software components?
Are updatings distributed in loose-leaf form, and remaining stock updated simultaneously?
Are all updates adequately supported by cover letters containing instructions and notification of obsolescence, with periodic summaries of available material on each system?
Does the library group utilize a computer for this service, for mailing lists, customer interest and software profiles, controlling and monitoring distribution?
Is a customer able to incorporate his own software units and special requirements without interference or malfunction as each system update is made?
Is the customer’s software system modified to become the new system rather than replace his entire system?
12. FIELD REPORTING AND MAINTENANCE
Is there an official, supported system for field reporting on
a) Software malfunction
b) Software mismatch to documentation
c) Inferior software performance
d) Requests for change to software design
e) Nonconformity to standards?
Is this reporting procedure enforced by written instructions to
a) Software Production
b) Sales and A.E. personnel
c) our customers?
Is turnaround service provided in the shortest time by means of high-speed communications systems?
Are field reports processed by formal procedures so the A.E. or customer can know the status at any time?
Are current lists of outstanding field reports furnished to A.E’s so they may protect the customer intelligently against these dangers?
Do all field reports carry identification of software units used and actual level of field changes installed in hardware?
Is the customer supplied with manufacturer’s recommended good practices in diagnostic methods, operations and use of processors?
Is the user clearly instructed that it is his responsibility to develop the simplest and smallest program which demonstrates the malfunction?