Getting requirements is not as obvious as you would think. Looking at "Concepts in Actions $3$A$"$ in chapter $3,$ Barbara Wixom points to a really frustrating project where functional requirements $($specific things the system should do$)$ were looked at$,$ but non$-$functional requirements $($the environment, speed, number of users of the system$)$ were missed. Instead of a small $$5,000$ project, it became a $$250,000$ headache that they lost $$245,000$ on$!$

Pretend that you received the following list of requirements for a sales system:

The system should $...$

be accessible to Web users.

include the company standard logo and color scheme.

restrict access to profitability information.

include actual and budgeted cost information.

provide management reports.

include sales information that is updated at least daily.

have $2-$second max response time for preset queries and $10-$minute max response time for ad hoc queries $($made up on the fly$).$

include information from all company subsidiaries.

print subsidiary reports in the primary language of the

subsidiary.

provide monthly rankings of salesperson performance.

Answer the following questions:

Which requirements are functional business requirements? Provide two additional examples that you can think of$.$

Which requirements are nonfunctional business requirements? What kind of nonfunctional requirements are they? Provide two additional examples you can think of$.$