adplus-dvertising
frame-decoration

Question

What is the difference between customer-driven software development and market-driven software development?

a.

Market-driven software development is based on customer needs and wants, while customer-driven software development is based on market considerations and product fit.

b.

Customer-driven software development is based on customer needs and wants, while market-driven software development is based on market considerations and product fit.

c.

Market-driven software development focuses on one specific customer, while customer-driven software development focuses on a generic market

d.

Customer-driven software development focuses on one specific customer, while market-driven software development focuses on a generic market

Posted under Software Engineering

Answer: (b).Customer-driven software development is based on customer needs and wants, while market-driven software development is based on market considerations and product fit. Explanation:The much software developed today is market-driven rather than customer-driven, meaning that requirements for a "generic" library application are created by exploring the library domain, while trade-offs between requirements are based on market considerations, product fit, and the like.

Engage with the Community - Add Your Comment

Confused About the Answer? Ask for Details Here.

Know the Explanation? Add it Here.

Q. What is the difference between customer-driven software development and market-driven software development?

Similar Questions

Discover Related MCQs

Q. What are some of the trade-offs that need to be made when using commercial off the shelf (COTS) components in a library system?

Q. What is the goal of requirements elicitation process?

Q. What are the guidelines for the contents of a requirements specification document?

Q. What are the basic techniques for modeling requirements?

Q. What is the main goal of requirements specification?

Q. What is the main difference between a requirements specification document and a project plan?

Q. What are some techniques used for specifying requirements?

Q. What are the four processes in requirements engineering according to Sommerville (2005)?

Q. What is the purpose of a requirements specification document?

Q. What is the goal of the requirements validation and verification process?

Q. What is the main purpose of the requirements negotiation process?

Q. In what stage of the requirements engineering process is design and implementation typically included?

Q. What is the main focus of the requirements engineering process?

Q. What is the role of the requirements analyst in the requirements elicitation process?

Q. What are some common techniques used for specifying requirements?

Q. What is the role of the central repository in requirements engineering?

Q. The primary goal of the requirements engineering phase is to:

Q. The part of reality that we are interested in during requirements engineering is referred to as:

Q. The model constructed during the requirements engineering phase is:

Q. The adjective 'explicit' in the phrase 'explicit conceptual model' means that the model should: