This document discusses how to understand non-functional requirements. It defines that functional requirements describe what a system should do, while non-functional requirements describe how it should be. It then lists and describes common non-functional requirements for systems including usability, performance, security, scalability, and others. It also discusses where requirements can come from such as business, infrastructure, domains, or externally/internally. Finally, it proposes an exercise to practice understanding non-functional requirements by having business owners present cases to an outsourcing company team.