In the value fulfilment blueprint, what is the difference between the functional and non-functional requirement of your product

In the value fulfillment blueprint, functional and non-functional requirements play different roles in defining your product.

Functional requirements are the fundamental actions and processes that a product must perform. They describe what the product will do and its intended functionality. For example, if you're developing a mobile app, functional requirements might include user login, data storage, data processing, and the ability to share content with other users.

On the other hand, non-functional requirements are the criteria that judge the operation of a system, rather than specific behaviors. They define how the system should work. They are often referred to as the "quality attributes" of a system. For example, performance (how fast the system responds), security (how well the system is protected against unauthorized access or damage), usability (how easy it is for the user to use the product), and reliability (how often the system fails) are all non-functional requirements.

In summary, functional requirements are about what the product should do, while non-functional requirements are about how the product should be.