Is there a computerized system for manipulating the data on each software unit, such as
a) total size
b) maximum residency
c) set membership
d) the other units which may call it
e) the other units which it may call
f) the interfaces with these surrounding units, together with the entry and exit points
in order to determine
a) that the hardware configuration is not exceeded
b) that enough hardware exists to run the software
c) a mechanical diagram of the entire system for completeness and consistency for quality control, diagnostic and maintenance purposes?
Does the production control system recognize and allow for the relative invisibility of software?
Given a specific software unit of a minimum size feasible for individual control, do the responsible supervisors estimate total elapsed time and costs for man and machine hours as a function of their resources? Is internal competitive bidding allowable for cost reduction?
Is the data for each stage (functional specifications, flowcharts, implicit quality test, coding, checkout in vacuo, checkout in processor, checkout in system, documentation, explicit quality test, release) of development of that software unit given by the supervisor on a signed document?
Are labor distribution reports developed from the timecards of programmers participating on each unit?
Does the individual programmer periodically give an estimate of the percentage of completion of each unit, for correlation to labor distribution and schedules, and perhaps PERT charts?
Are full records kept on original estimates, revised estimates and actual completion dates for
a) Recalibration of supervision
b) Improvement of future estimates
c) Deriving production standards
d) Possible rebalance of staff or redesign
e) Notification to marketing in case of slippage?
Are these viewed as official company records, so that detected falsifiers are subject to discharge?
Does effort expended on unapproved or bootleg projects put the controlling supervisor subject to discharge?
Is the production control keyed to a roster containing the list of official software units supplied without charge, keyed to the documentation units, and for each customer the
1) User’s name, address and representative
2) Branch office name, address and representative
3) Contact pattern between user, branch and programming
4) Machine type, serial, installation date, on-rent date