adplus-dvertising
frame-decoration

Question

What are the characteristics that indicate system degradation?

a.

Code over seven years old, missing or incomplete design specifications, and hard-coded parameters that are subject to change

b.

Difficulty in keeping maintenance personnel, frequent system failures, and overly-complex program structure and logic flow

c.

Very large modules or subroutines, code written for previous generation hardware, and running in emulation mode

d.

All of the above

Answer: (d).All of the above Explanation:The characteristics that indicate system degradation are code over seven years old, missing or incomplete design specifications, hard-coded parameters that are subject to change, difficulty in keeping maintenance personnel, frequent system failures, overly-complex program structure and logic flow, very large modules or subroutines, code written for previous generation hardware, and running in emulation mode.

Engage with the Community - Add Your Comment

Confused About the Answer? Ask for Details Here.

Know the Explanation? Add it Here.

Q. What are the characteristics that indicate system degradation?

Similar Questions

Discover Related MCQs

Q. Which type of metrics can be used to guide decisions about when to start a major overhaul of components or complete systems?

Q. What is the scope of software quality assurance?

Q. What can be done with the observed trends from metrics used in software quality assurance during maintenance?

Q. What is the relationship between software quality assurance during development and maintenance?

Q. What quality factors affect maintenance effort and cost?

Q. What is the role of metrics in software quality assurance during maintenance?

Q. What is the purpose of software quality assurance during maintenance?

Q. Which scheme requires the most planning and oversight?

Q. What is an advantage of the variable staff and fixed schedule scheme?

Q. In the fixed staff and variable schedule scheme, what is fixed in advance?

Q. What are the three common ways to decide on the contents and timing of the next release?

Q. What is the purpose of bundling change requests into releases?

Q. Why should the quick-fix model be avoided?

Q. In the quick-fix model of software maintenance, what is the typical order of updating documentation?

Q. What is the essence of the iterative-enhancement model of software maintenance?

Q. What is the suggested process for controlling changes during maintenance according to IEEE Standard 1219?

Q. Who makes the decision to implement a change request in the software maintenance process?

Q. What are the four maintenance categories for change requests?

Q. What is the IEEE Standard 1219?

Q. Why is configuration control important during software maintenance?