Non-functional requirements describe (check ALL that apply):System Design Constraints.Quality related constraints like security, performance, and usabilityIntended output or result of the system, such as, computing the shortest path between two points in a graph.

Non-functional requirements describe:

1. System Design Constraints: These are the limitations or restrictions on the system design. For example, the system may need to be compatible with certain hardware or software, or it may need to be able to handle a certain amount of data or users.

2. Quality related constraints like security, performance, and usability: These are the requirements that relate to how well the system performs and how easy it is to use. For example, the system may need to be secure from hackers, it may need to perform tasks quickly, or it may need to be easy for users to navigate and understand.

The intended output or result of the system, such as computing the shortest path between two points in a graph, is not a non-functional requirement. This is a functional requirement, as it describes what the system is supposed to do. Non-functional requirements, on the other hand, describe how the system should behave or what qualities it should have.