The Non- functional Requirements Types
The non-functional requirements are grouped into the eight non-functional requirements types as explained
Look and feel: According to this requirement the appearance of the product is important for both the user and the provider of the product.
Usability and Humanity: This explained that the product should be easy to use and there should be more importance for the product fell to make it more worth in giving the better results to the user of the product.
Performance: It tell us the product should have the right pace for the user to use as it includes everything as started from who much your product is safe to use, Is your product is fast and has accurate functions in it to provide the user a good experience in usage.
By: Sachin Chopra
Source:
Robertson, S., & Robertson, J. (2014). Mastering the Requirements Process (3rd ed.). Upper Saddle River, N.J: Addison-Wesley
Group 1 Tim Horton's 
Look and Feel Requirements:
Look and feel requirements are very important for requirements. It tells about the appearance and informed about the intended spirit, the mood, shape, or the design of the appearance of the product. Look and feel requirements are written as the product shall comply with corporate branding standard. The products should innovative, consistent, and exciting. Every design has one prototype which informed the expected look and feel of the product.
By: Kirandeep Kaur Gill
LikeLike
Performance requirements are a great way to access how a task can/will be accomplished over a period of time. The key words are “over a period of time” as this can set the metric to measure how well or how fast a requirement can be accomplished in. For Tim Hortons performance requirements are crucial since they operation in the fast-food service industry where customers demand food and service instantly. By setting these goals Tim Hortons can create metrics to accomplish tasks/goals as quick as possible.
-Mark Stabile
LikeLike
Usability and Humanity:
Usability requirements are often left out of the requirements specification on the assumption that no sane programmer would build a product that is hard to use. At the same time, the product’s usability might be one of the key factors that determine whether the intended users actually use it. Do not make the mistake of assuming the product will be usablewhat is usable to one person could be unfathomable to another.
-Haoyan Yin
LikeLike