Acquisitions that involve a significant amount of software development are notorious for their problems. Missed schedules and cost overruns plague the acquisition process. When systems are finally delivered, they are often unreliable and do not meet all their requirements.

The software acquisition process should have all of the necessary milestones and accountabilities to ensure that the work is done in both a timely and correct fashion.

After the plan is prepared and approved, a Request for Proposals $($RFP$)$ is developed and circulated. The RFP is a sent to all logical vendor sources to provide a solution, for a price quoted, that addresses the problem specified in the requirements $($usually by a certain deadline$).$

Tasks:

Develop and submit a well$-$written, graduate$-$level paper NOT LESS THAN four $(4)$ pages that addresses the following questions:

What is an RFQ$?($your response here should go beyond providing a simple, textbook definition!$)$

What is an RFP$?($your response here should go beyond providing a simple, textbook definition!$)$

What is the difference between an RFQ and RFP$?($compare and contrast these two documents, which means providing a response that is more than a simple, one or two$-$line statement$)$

When, under what circumstances, would you recommend using an RFP$?$ Why?

When, under what circumstances, would you recommend using an RFQ$?$ Why?