< Prev Next >
100
NATO SOFTWARE ENGINEERING CONFERENCE 1968
9. Working Papers
5) Hardware configuration, operational dates of units
6) Channel assignments, other determinations of logical options
7) Field change orders affecting software and whether installed or not
8) Software options for:
a. Required units
b. Characteristics of their storage
c. Characteristics of their usage
d. Maximum store allotted for processing and usage
e. Hardware restrictions affecting software operation, such as reserved elements or lockouts
f. Delivery form of software unit (symbolic, relocatable, absolute, FORTRAN, etc.)
g. Special software supplementing or replacing standard units, by whom supplied, data descriptions and linkages
9) Number of last system delivered. Updating pattern and requested frequency (6 month maximum interval for archivage limitation):
a. Every system
b. Every nth system
c. Upon specific request
d. First new system after elapsed time interval
e. Only on change to specified software units
f. Combinations of these
10) Requirements for backup system on another machine
11) Special commitments by sales or programming personnel
12) List of customer’s field reports by number?
6. FABRICATION
Is software fabricated for utility in the international market?
Is there an active standards unit in the software production group policing compliance with national end international standards available?
Are there internal local standards for production consistency?
Does programmer terminology conform to the standard IFIP/ICC vocabulary?

Are sufficient personnel provided to participate in advanced standards making work?
Is all system planning done with standard flowchart templates, where applicable?
Are logic equations an allowable alternative to flowcharting?
Are good records kept in any stage of development?
Are systems kept on tape or disc periodically copied on cards or tape for recovery?