adplus-dvertising
frame-decoration

Question

Why does the value of software maintenance lie in activities that result in benefits for the customers?

a.

Because software maintenance results in a product being delivered to the customer.

b.

Because software maintenance results in a service being delivered to the customer.

c.

Because software development provides benefits to the customer.

d.

None of the above.

Posted under Software Engineering

Answer: (b).Because software maintenance results in a service being delivered to the customer. Explanation:Software maintenance has more service-like aspects than software development, because the value of software maintenance lies in activities that result in benefits for the customers, such as corrected faults and new features.

Engage with the Community - Add Your Comment

Confused About the Answer? Ask for Details Here.

Know the Explanation? Add it Here.

Q. Why does the value of software maintenance lie in activities that result in benefits for the customers?

Similar Questions

Discover Related MCQs

Q. What is the gap model often used for in service marketing?

Q. Why may gap 1 arise in software maintenance?

Q. What is a Service Level Agreement (SLA) used for in software maintenance?

Q. What is the cause of gap 2 in software maintenance?

Q. What is the gap model used by service marketeers for?

Q. Which gap is caused when the expected service as perceived by the service provider differs from the service as expected by the customer?

Q. What is a Service Level Agreement (SLA)?

Q. What is the cause of gap 3?

Q. What is the purpose of event management in software maintenance organizations?

Q. What is the purpose of a service level agreement in software maintenance organizations?

Q. Why do software maintenance organizations need to manage their product as a service?

Q. What is configuration control in software development?

Q. Why is configuration control important during software maintenance?

Q. What is the IEEE Standard 1219?

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

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

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

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

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

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