To minimize the cost of a software project, quality management techniques should be applied:

A.
as close to their writing (i.e., point of origination) as possible.

B.
primarily at project start-up to ensure that the project is established in accordance with organizational
governance standards.

C.
continuously throughout the project with an emphasis on finding and fixing defects primarily during
testing to maximize the defect detection rate.

D.
mainly at project close-down to capture lessons learned that can be applied to future projects.

Explanation:
While it is important to properly establish a software development project, quality management
should be effectively practiced throughout the project. The major source of unexpected costs on
most software projects is rework. The general rule is thatthe earlier in the development life cycle
that a defect occurs, and the longer it takes to find and fix that defect, the more effort will be needed
to correct it. A well-written quality management plan is a good start, but it must also be actively
applied. Simply relying on testing to identify defects is a relatively costly and less effective way of
achieving software quality. For example, an error in requirements discovered in the testing phase
can result in scrapping significant amounts of work. Capturing lessons learned will be too late for
the current project. Additionally, applying quality management techniques throughout a project is
likely to yield its own insights into the causes of quality problems and assist in staff development.