Question 2Which of the following are non-functional requirements:1 pointSome product requirements, like using a specific encryption protocol, are non-functional requirements.Organization requirements imposed by the company, like a specific coding style, are non-functional requirements.External requirements imposed by external organization, like using a specific development style, are non-functional requirements.All of the above.

The correct answer is "All of the above."

Here's why:

1. Some product requirements, like using a specific encryption protocol, are non-functional requirements. This is true because non-functional requirements are about how the system works, rather than what it does. An encryption protocol is about how data is secured, not what the data does.

2. Organization requirements imposed by the company, like a specific coding style, are non-functional requirements. This is also true. Coding style doesn't change what the code does, but it does affect how it's written and maintained, which are non-functional aspects.

3. External requirements imposed by external organization, like using a specific development style, are non-functional requirements. This is true for the same reasons as the previous point. The development style doesn't change what the software does, but it does affect how it's developed, which is a non-functional aspect.

So, all of these are examples of non-functional requirements.