Software Project Management (SPM) MCQs | Page - 1

 projects need to be managed because professional software engineering is always subject to organizational budget and schedule constraints.

 risk management involves anticipating risks that might affect the project schedule or the quality of the software being developed, and then taking action to avoid these risks.

 testing is a part of project, thus it can’t be categorized as risk.

 a proven methodical life cycle is necessary to repeatedly implement and manage projects successfully.

 the probability of the risk might be assessed as very low (<10%), low (10–25%), moderate (25–50%), high (50–

 estimation involves working out how much effort is required to complete each activity and, from this, calculating the total cost of activities.

 the quality plan should set out the desired software qualities and describe how these are to be assessed.

 configuration management policies and processes define how to record and process proposed system changes, how to decide what system components to change, how to manage different versions of the system and its components, and how to distribute changes to customers.

 the value of the quality attribute must be related, in some way, to the value of the attribute than can be measured.

 software design explains all of the statements as its definition.