Non-functional requirements relate to code standards in what way?

• A. Requirements like performance, security, reliability, and usability that influence how code is written and tested
• B. The color scheme of the UI
• C. The number of test cases
• D. The licensing terms

Answer: (A)

Non-functional requirements define quality attributes that constrain how software is built and tested. They specify how well the system must perform, stay secure, behave reliably, and be usable. Because of these attributes, coding standards are shaped to produce efficient, secure, maintainable, and accessible code, and testing strategies are designed to verify these attributes through performance, security, reliability, and usability tests. The other options don’t capture these ongoing quality constraints: the color scheme is a UI design choice, not a code-quality requirement; the number of test cases is a testing plan detail; licensing terms are legal constraints, not how code is written or tested.