Explanation:
Box 1: Non-functional
Requirements are commonly referred to as either functional or non-functional. Functional requirements describe what the solution needs to do or its behaviors, and non-functional requirements commonly describe non-behavior aspects of the solution such as performance requirements.
The following examples are of well-composed non-functional requirements:
Average screen load time for internal users that are not mobile will be less than three seconds.
External portal must be able to handle 100 concurrent users who are performing case submission.
Any credit card number that is used cannot be stored in Common Data Service environment.
Box 2: Functional
Example functional requirements
The following scenarios describe simple examples of functional requirements:
As a sales user, I need to be able to close an opportunity as lost and then capture why it was lost so that we can improve our sales tactics in the future.
As a sales manager, I need to be able to approve a discount on a quote so that I can reduce the total price and give a discount to the customer.
As a staff accountant, I want to be prevented from closing a batch that has pending items so that I do not have to reopen it later.
Box 3: Non-functional
Examples of common non-functional requirement types include:
Availability
Compliance/regulatory
* -> Data retention/residency
Performance (response time, and so on)
Privacy
Recovery time
Security
Scalability
Reference: https://docs.microsoft.com/en-us/learn/modules/work-with-requirements/3-functional-requirements
https://docs.microsoft.com/en-us/learn/modules/work-with-requirements/4-non-functional-requirements