Software Maintenance includes

Related MCQs

• Match the following : A- Maintenance control: B- Maintenance prediction: C- Maintenance process: 1-Cost of planning and scheduling hardware preventive maintenance, and software maintenance and upgrades, managing the hardware and software baselines, and providing response for hardware corrective maintenance. 2- Predicting the number of change requires a system understanding and the relationship between the system and external environment. 3- It is triggered by a set of change requests from system users, management or customers.
• Match the following : A- Maintenance control: B-Maintenance measures: C-Maintenance personnel : 1-Cost of planning and scheduling hardware preventive main- tenance, and software maintenance and upgrades, managing the hardware and software baselines, and providing response for hardware corrective maintenance. 2- Measures that address how easily a system can be repaired or changed. 3-Number of personnel needed to maintain all aspects of a computer system, including the support personnel and facilities needed to support that activity.
• ---------- it includes the steps of maintenance phase of software.
• What type of software testing is generally used in Software Maintenance?
• This set of Basic Software Engineering Questions and Answers focuses on “Function Oriented Software Design”. 1. Choose the option that does not define Function Oriented Software Design.
• Software maintenance is
• How does a software project manager need to act to minimize the risk of software failure?
• If in a software system, the operation is degraded if results are not produced according to the specified timing require- ments then the software system is referred as
• If in a software system, the operation is incorrect if results are not produced accor- ding to the specified timing requirements then the software system is referred as
• Match the following : A-Control metrics : B- Process metrics: C- Control: D-Correctness: 1- They are associated with software process. 2- They are associated with software products. 3- Protective measure that reduces system vulnerability. 4- Extent to which a system or component is free from faults in its specification, design, and implementation