Software Maintenance

What causes software changes?

I. New requirements

II. Change of environment

III Errors

IV New computers and equipment

• I,II,III

• I,II,IV

• I,III,IV

• All above

“the modification of a software product after delivery to correct faults,

to improve performance or other attributes,

or to adapt the product to a modified environment”

That is the definition of what

• Software change

• software maintenance

• software implementation

• software testing

We need maintenance for software to continue to become useful

• true

• false

"Identify and remove defect and errors"

• Preventive Maintenance

• Corrective Maintenance

• Adaptive Maintenance

• Perfective Maintenance

"Improving performance, reliability, updating documentation"

• corrective maintenance

• adaptive maintenance

• perfective maintenence

• preventive maintenance

Which are NOT the maintenance cost factors?

I. Team stability

II Contractual responsibility

III Staff skills

IV Performance and reliability

• I

• II

• III

• IV

"What part of the system most likely to be affected by change request?", This statement is which part of software maintenance prediction?

• predicting maintenability

• predicting maintenance cost

• predicting system changes

Which is NOT a prediction assumption when assessing parts of the system may cause problems and predicting cost ?

!. Change acceptance depends on the maintainability of the components affected by the change;

II.Average time required for impact analysis

III. Implementing changes degrades the system and reduces its maintainability;

IV. Maintenance costs depend on the number of changes and costs of change depend on maintainability.

• I

• II

• III

• IV

Which are process measurements that may be used to assess maintainability ?

!. Number of requests for corrective maintenance

II. Average time required for software requirements and design

III. Average time taken to implement a change request

IV. Number of outstanding change requests

• I, II, III

• I, II , IV

• I, III, IV

• All above

What process does this diagram show

• Emergency repair / urgent change request

• change identification

• system evolution

• change implementation