< Prev Next >
NATO SOFTWARE ENGINEERING CONFERENCE 1968
97
9. Working Papers
Does it specifically include material on the following:
a) International, national, industry and company standards.
b) Design for offline vs. online operation.
c) Design for closed vs. open shop usage.
d) Flexibility for various customer job mixes.
e) Alternate software with different performance but same functional characteristics.
f) Diagnostics under the executive system.
g) Modelling for design decisions (and simulation).
h) Initialization, bootstrap and restart procedures.
i) Optimizing human operating characteristics.
j) Special diagnostic aids for users.
k) Making the executive system forgiving and helpful in case of hardware faults.
l) Providing for special, nonstandard hardware.
m) Accounting and measuring procedures.
n) Modular construction.
o) Alternative modes of system operation, with a provision to indicate those selected.
p) User priorities, special accounting and custom software units supplied by the user.
q) Machine room operational procedures.
4. SCHEDULING AND COSTING
Do plant accounting procedures provide all necessary information on costs by project, rather than by cost center?
If not, does software production incorporate this in its own production control system?
Is the gathered data processed, not merely accumulated?
Is there a software production control system to fabricate to predicted schedules for predicted costs?
Are costs of previous system construction utilized in predicting new costs?

Are all sales commitments for software, and software delivery clauses in contracts, concurred in by software production for incorporation in the production control system?
Are there responsible software project managers who utilize the mechanized production control system to ensure that all elements are available on scheduled delivery dates?
Are there production documents for each phase of production of each software unit, representing a scheduling commitment upon the part of the unit manager?
Do these then yield gross schedules of expected completion which are published internally and incorporated in the production control system?
Are these expected schedules then modified by maximum slippage factors to produce schedules which can be incorporated into contracts without specific approval each time, particularly for non-delivery and non-performance penalty provisions?
Is it guaranteed that all contracts with schedules prior to these dates are subject to approval by software management?