The following lists:

• NFR on forecasted demand are incorrect: Due to the fact that demand volumes change with time and after the NFRs were initially established; or perhaps the process of converting the request to technical transactions was incorrect; or demand was reduced due to budget restrictions.
• NFR definitions are not comprehensive: Limited definition for the response times attribute have been met. Other attributes also define the performance of a service and hence its quality. These include the stability and consistency of the service. These all need to be modeled when defining the NFRs.
• NFRs can't be measured: The NFRs are modeled in the design stage. Lack of tracking and monitoring will lead to NFRs being unenforceable.
• There are no limitations on the infrastructure: This is equivalent to handing infinite infrastructure to either your internal delivery team or operations team.