adplus-dvertising
frame-decoration

Question

Why may gap 1 arise in software maintenance?

a.

Because of differences between perceived service delivery and expected service.

b.

Because the service specification differs from the expected service as perceived by the service provider.

c.

Because the service provider has an insufficient relationship focus.

d.

Because the (internal) service designs and standards do not match the service requirements as perceived by the service provider.

Posted under Software Engineering

Answer: (c).Because the service provider has an insufficient relationship focus. Explanation:Gap 1 may arise if the service provider has an insufficient relationship focus, which means that the service provider's perception of the expected service may differ from the customer's expectation.

Engage with the Community - Add Your Comment

Confused About the Answer? Ask for Details Here.

Know the Explanation? Add it Here.

Q. Why may gap 1 arise in software maintenance?

Similar Questions

Discover Related MCQs

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?

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

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