Are nonfunctional requirements typically discussed with subject-matter experts?

Nonfunctional requirements are indeed typically discussed with subject-matter experts. These requirements describe the quality attributes of a system, such as performance, security, usability, and reliability, rather than specific behaviors or functions. Engaging subject-matter experts in conversations about nonfunctional requirements is crucial because they possess the necessary domain knowledge and insights that help define the desired attributes of the system.

For example, performance requirements might be influenced by experts who understand the load and response expectations of the application in real-world settings, while security requirements would certainly benefit from the expertise of cybersecurity professionals. By collaborating with these experts, the project team can ensure that the nonfunctional requirements are realistic, measurable, and aligned with user expectations and business goals. This collaboration fosters a comprehensive understanding of the needs that the system must meet beyond just its functional capabilities.