Q3. One of the most common mistakes by new SAs is confusing functional and non-functional requirements. Visit the Amazon.com site. Give an example of a functional business requirement and an example of a non-functional business requirement. Why is it important to make the distinction?

A:Functional and non-functional requirements can be distinguished by simplifying their meaning. In basic terms functional requirements is what is being done within or by the system. At Amazon.com sales suggestions are being made to customers as they browse or review a specific product. This is a functional requirement and is explained by what is being done. These same sales suggestions are arranged along the side and bottom of the web page. Also, the sales suggestions are based off the users browsing history for similar products or products needed in addition, as accessories to previously viewed items. This is how the suggestions are made and is a non-functional requirement. This distinction is import to SAs because it allows them to understand what the intent and goals of a system is versus how to create and implement it.