Which statement is a software acquisition best practice for ensuring quality in development?

Which statement is a software acquisition best practice for ensuring quality in development?

• A. Track defects against quality targets
• B. Use metrics to manage
• C. Idle workers
• D. Use system based software design

Answer: (D)

Starting with system-level design is the strongest way to build quality into the software from the ground up. By outlining the overall architecture, defining components and their interfaces, and identifying the key quality attributes the system must meet (such as reliability, security, maintainability, and performance), you create a blueprint that guides every development and procurement decision. This proactive approach reduces integration risks, makes requirements traceable through the design, and helps ensure components will work together smoothly, leading to higher quality outcomes. Tracking defects against quality targets and using metrics to manage are important for monitoring and governance, but they are reactive controls that come into play after or during development. They help you measure quality and drive improvements, yet they don’t establish the design foundations that prevent defects and architectural issues in the first place. Idle workers obviously do not contribute to quality. Focusing on system-based design thus provides the most effective groundwork for delivering a high-quality software product.

Starting with system-level design is the strongest way to build quality into the software from the ground up. By outlining the overall architecture, defining components and their interfaces, and identifying the key quality attributes the system must meet (such as reliability, security, maintainability, and performance), you create a blueprint that guides every development and procurement decision. This proactive approach reduces integration risks, makes requirements traceable through the design, and helps ensure components will work together smoothly, leading to higher quality outcomes.

Tracking defects against quality targets and using metrics to manage are important for monitoring and governance, but they are reactive controls that come into play after or during development. They help you measure quality and drive improvements, yet they don’t establish the design foundations that prevent defects and architectural issues in the first place. Idle workers obviously do not contribute to quality. Focusing on system-based design thus provides the most effective groundwork for delivering a high-quality software product.